Start With the System, Not the Output
Co-design is often treated as a method; a workshop; a phase in a project plan. It’s more useful to think of it as a practice framework. A framework that helps teams navigate complex systems rather than rush toward solutions. Because the real work isn’t in generating ideas. It’s understanding the system those ideas need to live in.
That means looking beyond users to focus on stakeholders in the full sense of the word: communities, organizations, policymakers, and frontline staff. Each brings a different view of the system and a different stake in how it needs to change.
Applied to Pivot’s healthcare-focused work, that means hospital officials might bring policy insight. Patients bring lived experience. Businesses bring operational expertise. Healthcare systems bring research. Each perspective reveals something different about the system being examined.
And each brings something else we don’t always want to name, much less face.
Power.
Everybody has power. Not just formal authority. But influence, expertise, relationships and critically, the ability to move things forward or quietly stall them. Ignoring power doesn’t make it go away. It just shows up later, usually when timelines tighten, and decisions become more substantive.
Good co-design surfaces those dynamics early. It makes them part of the conversation. Not to resolve them completely – because that rarely happens – but to understand the terrain and dynamic.