Co-Creation is Not a Workshop

Most people describe co-creation as sticky notes and voting dots. That's not co-creation. That's a meeting.

Co-creation is a worldview. It's a fundamental belief about where good solutions come from.

The Worldview

Here's what I believe after 26 years of building products:

The best solutions emerge when the people closest to the problem are part of creating the solution.

Not consulted. Not interviewed. Not asked for feedback on a finished design. Part of creating.

This sounds obvious. It's not how most organizations work.

The Usual Pattern

Most product development follows this pattern:

1. Someone (often far from users) decides what to build
2. Designers make it look nice
3. Developers build it
4. Someone remembers to ask users what they think
5. Users are confused
6. Everyone wonders what went wrong

I've watched this pattern destroy millions in investment. One company I worked with spent two years on this cycle before discovering their customers didn't want what they'd built.

The Alternative

Co-creation inverts this:

1. Gather the people who understand the problem deeply
2. Create conditions for them to surface what they know
3. Build something together
4. Test it with real users
5. Iterate based on evidence

The magic happens in step 2: "create conditions for them to surface what they know."

Why This Works

Your organization is full of hidden knowledge.

The customer service rep who hears the same complaint every day. The sales person who knows exactly which features close deals. The operations manager who sees where the system breaks. The user who's been waiting years for someone to ask the right question.

Most of this knowledge never reaches the people making product decisions.

Co-creation breaks those silos. It creates space for insights to surface. It treats everyone as an expert in their domain—because they are.

What It Looks Like

When I facilitate co-creation sessions, I don't present for 30 minutes then ask for feedback. I start with participation from minute one.

Not because I'm impatient. Because the energy shifts the moment people stop being an audience and start being contributors.

We might map a journey together. Identify pain points as a group. Ideate solutions that combine expertise from across the room. Build rough prototypes that embody collective intelligence.

The output isn't a report. It's shared understanding and aligned direction.

The Real Challenge

The hard part isn't the methods. It's the mindset shift.

You have to believe that the engineer knows something the PM doesn't. That the customer service rep sees things the designer can't. That users themselves hold answers nobody else can access.

If you don't believe this, you'll run workshops that look like co-creation but aren't. You'll present your ideas and ask for validation. You'll hear what confirms what you already thought.

If you do believe it, everything changes. You start listening differently. You create space for surprise. You design sessions where anyone can shift the direction.

A Concrete Example

I was working with an engineering software company that had spent two years building the wrong thing. When we finally brought users into a co-creation session, one of them arrived with slides.

Not slides they'd been asked to prepare. Slides they'd made years ago, trying to show the company what they actually needed. UI mockups. Documentation. "If you built this, it would save us a week per month."

This user had been waiting years for someone to create space for their knowledge to be heard.

That's what co-creation does. It creates space.

Start Small

You don't need a transformation initiative. Start with one session where:

• Everyone speaks in the first five minutes
• The agenda responds to what emerges
• The output is shaped by collective intelligence, not one person's vision
• Hierarchy fades into expertise

See what happens when you treat everyone as a contributor.

You might be surprised what your organization already knows.