The Difference Between Consultation and Genuine Co-Design
Consultation and co-design are often spoken about as though they are interchangeable.
They are not.
Both can be valuable. Both can create opportunities for people to contribute. Both can improve decisions.
But they give people very different levels of influence over what is ultimately created.
Consultation asks people what they think.
Co-design asks people to help shape what happens next.
That difference matters.
Consultation has a place
Consultation is not inherently a bad process.
There are times when an organisation needs to gather feedback, test an idea, understand different perspectives or hear from people who may be affected by a decision.
Done well, consultation can provide valuable information.
The problem arises when a process is described as collaborative while the most important decisions have already been made.
If the direction is fixed, the solution has already been designed and people are simply being asked to comment on it, that is consultation.
It may be useful consultation.
But it is not co-design.
Being clear about that distinction creates more honest relationships from the beginning.
Co-design begins earlier
Genuine co-design starts before the answer is known.
It creates space for the people closest to an issue to influence how the problem is understood, what priorities matter and what potential solutions might look like.
That means the conversation is not simply:
What do you think of what we have developed?
It becomes:
What are we trying to solve?
What are we missing?
What matters most to the people affected?
What knowledge needs to shape this work?
What might a better outcome look like?
Those questions change the nature of participation.
People are no longer being invited into somebody else’s solution.
They are helping shape the work itself.
Participation does not automatically mean influence
Organisations can involve many people and still make very little space for genuine influence.
There might be workshops.
Surveys.
Reference groups.
Community meetings.
Advisory committees.
Stakeholder interviews.
All of those activities can look highly participatory.
But the number of people involved does not tell us how much influence they had.
A better question is:
What was able to change because people participated?
Could their input change the direction?
Could it alter priorities?
Could it challenge assumptions?
Could it influence the final design?
If nothing meaningful was open to change, then participation was limited regardless of how extensive the engagement process appeared.
Start by being clear about what is negotiable
One of the simplest ways to build trust in a process is to be clear about what people can and cannot influence.
Sometimes there are genuine constraints.
There may be legislation.
Budget limitations.
Timeframes.
Contractual requirements.
Safety considerations.
Government policy.
Existing organisational commitments.
Co-design does not mean pretending those constraints do not exist.
It means putting them on the table.
If something cannot change, say so.
If something can change, create genuine space for people to shape it.
People are far more likely to trust a process when they understand its boundaries than when they discover later that their contribution could never have influenced the outcome.
Listening is more than collecting feedback
Listening is often talked about as though it simply means providing an opportunity for someone to speak.
But genuine listening requires an organisation to do something with what it hears.
That does not mean every suggestion must be adopted.
Different perspectives can conflict.
Resources are finite.
Decisions still need to be made.
But people should be able to see how their contribution travelled through the process.
What did we hear?
What did it change?
What could not be changed?
Why?
What happens next?
Closing that loop is one of the most important parts of respectful engagement.
Without it, people can be asked to contribute repeatedly without ever knowing whether their time, knowledge or experience made any difference.
The people closest to a system often see what others cannot
There is knowledge that exists in reports, research, policy and organisational data.
And then there is knowledge that comes from experiencing a system.
Both matter.
People who use a service understand where it becomes difficult to navigate.
Frontline workers often know where processes break down.
Communities understand context that may never appear in formal documentation.
Families see consequences that organisational reporting may not capture.
Leaders see constraints across the broader system.
Good co-design creates a way for these different forms of knowledge to meet.
It does not assume one person holds the complete answer.
That is often where better solutions begin.
Co-design requires organisations to share some control
This can be the uncomfortable part.
Genuine co-design requires a willingness to enter a process without controlling every outcome in advance.
For organisations used to established decision-making structures, that can feel unfamiliar.
There is often a strong instinct to arrive with answers.
It can feel more efficient.
It can feel safer.
But complex problems rarely belong to one person, one team or one organisation.
If we already knew exactly how to solve them, many of them would not remain complex.
Co-design creates another way of working.
It asks organisations to bring their expertise while recognising that other people bring expertise too.
The work becomes less about handing over control completely and more about understanding where responsibility, knowledge and decision-making should sit.
Relationships are part of the process
Good co-design cannot be reduced to a workshop methodology.
The quality of the relationship matters.
Trust matters.
Continuity matters.
The way disagreement is handled matters.
Whether people feel safe enough to say something difficult matters.
Whether an organisation returns after the workshop matters.
Because co-design is not simply about creating a moment of participation.
It is about building enough trust for people to contribute honestly to something that matters.
That takes time.
And sometimes it requires organisations to work at the pace of the relationship rather than the pace of the project plan.
Be clear about who makes the final decision
Co-design does not remove leadership or governance responsibility.
Someone will still need to make decisions.
Boards remain accountable.
Executives remain responsible.
Funding bodies may hold certain authorities.
What changes is the quality of the information and perspectives informing those decisions.
Strong co-design makes those pathways clearer rather than less clear.
People should understand:
Who is involved?
Who has decision-making authority?
How will recommendations be considered?
How will disagreements be resolved?
How will the final decision be communicated?
Transparency around decision-making protects the integrity of the process.
Design together. Then keep listening.
The work does not end when something has been designed.
Implementation will reveal things the design process could not predict.
A policy may make sense on paper and create unexpected barriers in practice.
A service might work well for one group and poorly for another.
A process may be technically correct but difficult for people to use.
That means co-design needs a feedback loop.
Design.
Implement.
Listen.
Learn.
Adjust.
Measure.
Then listen again.
The aim is not to create a perfect solution the first time.
It is to create a way of working that can respond as new information becomes available.
Better participation should lead to better decisions
Co-design is not valuable simply because more people were included.
Its value lies in what that inclusion makes possible.
Better understanding.
Different questions.
Fewer assumptions.
More relevant solutions.
Greater ownership.
Stronger relationships.
And decisions informed by the people who understand the issue from different parts of the system.
Sometimes consultation is exactly what is required.
At other times, the complexity of the issue demands something deeper.
The important thing is being honest about which process we are creating.
Because asking people to participate carries responsibility.
If we invite people into the room, we should be clear about why they are there, what they can influence and what will happen with what they share.
That is where participation begins to become partnership.
And where co-design can begin to create real change.
