Co-design that works: building programs with people, not just for them.

Co‑design is one of those buzz words that is popping up everywhere. In agriculture, government, community programs, and funding conversations - and mostly with good intent.

But sometimes when organisations say co‑design, what is really meant is consultation or feedback, not genuine co-design. Sometimes people are brought in once most of the decisions have already been made and asked to then help make the program land, rather than shaping it from the outset.

That can still be useful and has its place, as long as we are really clear about the intent, but it is not the same as designing with people from the start.

In agriculture, timing, trust, risk, relationships, seasonal pressure, market pressure all shapes whether a program gains traction or not. A program can be technically sound and still miss the mark if it does not fit the people and businesses it is meant to support.

Growers know things that do not always sit in reports. They know the practical pinch points: labour, weather, costs, fatigue, timing, family businesses, and the constant judgement call between what would be ideal and what is actually possible.

Industry organisations understand adoption and capability. Researchers bring evidence and a scientific lens. Government brings policy and accountability and broader public interest. All of that is important, but usually none of it is enough by itself.

This is where we need to spend more time and focus. The people closest to the work can usually see the friction first. They know what will be adopted, what will be ignored, what will build confidence and what will fall over. If we listen early enough, we can design around reality instead of trying to patch it up later.

The word co‑design is misleading when a project is already largely framed, with set timelines and outputs written into a plan. If people are invited to contribute at this stage, it is not co-design.

Genuine co‑design means bringing people in while there is still room to move. It means asking better questions earlier. What do people need? What are they worried about? What would make this useful? What would make it too hard? And then comes the part that can be challenging: being willing to change direction when the input tells you to.

It also does not stop once the program is launched, and this is where we sometimes also miss the mark. We do the engagement, write up the findings, design the program, and then call the rest delivery. True co‑design keeps the right people close enough to keep shaping the work as things change - in a practical way, with the people who understand the work having a voice through the life of the program.

Building strong relationships and trust is an important part of this. We can talk about systems, innovation, productivity and transformation, but trust is what lets people take a risk, try something different and stay in the conversation.

Good co‑design builds trust because people can see their knowledge being taken seriously over time, not just captured at the start. They may not get everything they want - usually they will not – as good co-design considers different perspectives and viewpoints. But people involved should be able to see what was heard, what changed, what did not, and why.

When trust is built, people are more prepared to challenge and contribute.

Useful beats polished

I have seen plenty of programs that look reasonable on paper, with clean timelines, clear reporting and good intent, but then when it comes to implementation it doesn’t have the impact that it hoped.

It doesn’t mean the idea was bad, it often just means that the original design sat too far away from implementation. The seasonal timing did not fit, the tool was clunky or overly complex, or the message wasn’t shaped in a way that landed with the people it was tailored for.

Co‑design helps test those assumptions before they become expensive problems. The result may be less polished at first, but useful over polished is almost always better.

A good facilitator can help guide the co-design process by giving people enough structure to think clearly, and enough space to say what needs to be said. They notice who is quiet, who is taking up too much room, where the tension is, and what the group is circling but not quite naming.

Sometimes the most useful thing a facilitator does is help a group stay with the discomfort and messiness in the design phase long enough to find the better answer.

There is a temptation to make co‑design look more complicated than it needs to be. Clear communication along with utilising practical facilitation tools and structures allows people to know why they are there, what is being asked of them, where the boundaries are, and how their contribution could shape what happens next.

Clarity creates confidence, and confidence creates momentum. If people feel confused or left out, it is hard to regain that confidence.

In essence, people support what they help create, which is what co-design is all about. Shared ownership does not mean everyone agrees, and often it means the opposite at the start. Different priorities and viewpoints come into the room, and it can get messy, but that messy stage helps everyone to unpack what is really important and is where the useful alignment starts.

When the people that matter have some ownership of the work, and a genuine way to keep shaping it as conditions change, the program is stronger. People understand it, can see themselves in it, and are more prepared to make it work.

In practice, it comes back to a few key things. Engage before the important decisions are locked in. Listen for needs, fears, motivations and constraints, not just comments or the loudest voices. Be clear about purpose. If people do not understand why the work matters, the process will fall over.

Use facilitation that is structured but not controlling. Use tools people can actually participate in. Translate between policy, practice, research and community expectations, because those worlds do not always speak the same language.

And document decisions clearly, because people deserve to know what happened to what they offered.

If we design with people, not just for them, we build programs that are more practical, more trusted and more likely to last. In agriculture, where relationships are pivotal to successful outcomes, that is not just good engagement, it is good strategy.