The problem
Services in the For Purpose and Local Government sectors are often designed from the inside out — shaped by funding guidelines, program logic templates and organisational structure, then presented to the community as a finished product. When uptake is poor, the diagnosis is usually “awareness”, and the remedy is more promotion. The harder truth is often that the service was never designed around the people it exists for.
What the evidence says
Successive Australian reviews and royal commissions — across disability, aged care and mental health — have reached the same conclusion from different directions: services designed without genuine input from the people who use them consistently underperform on access, trust and outcomes. Government funders have responded, and co-design is now an explicit expectation in many Commonwealth and Victorian program guidelines rather than a nice-to-have.
The options
There is a spectrum. Consultation asks the community to react to a near-final design. Engagement involves them earlier, but the organisation still holds the pen. Co-design shares the pen: people with lived experience help define the problem, shape the model and test it before launch. Each step up costs more time; each also removes risk that is far more expensive to discover after launch.
What works
The organisations that do this well treat community input as evidence, not endorsement. They document what they heard, show how the design changed in response, and carry that evidence chain into their funding submissions and evaluations. That chain does double duty: it produces a better service, and it produces a more fundable one, because assessors can see the model is anchored in demonstrated need rather than assumption.
Word Weaver designs programs and services with that evidence chain built in — from needs analysis and co-design through to program logic, operating model and evaluation framework. If your next service design starts with a template rather than the community, start the other way around.
