There is a challenge that often gets put to consultancy: does it offer real value, or does it create dependency in public services? It’s a question that matters because government departments are under pressure to deliver faster, reduce risk and make better use of public money, but they also need services that can be sustained long after a supplier has left.
So really, the question is not whether outside expertise has a role in public service delivery; it’s whether that expertise is used in a way that strengthens the organisation, rather than becoming its organisational memory. Before moving into consulting, I worked in the Civil Service, so I know what good looks like, and what bad looks like too. I’ve been there to pick up the pieces when capability and knowledge haven’t been left behind.
Strategic partnership needs to mean more than bringing in people to deliver outputs. It should create the conditions for better decisions, lower delivery risk and stronger organisational capability. It should help teams understand the evidence behind a recommendation, the trade-offs being made and the practical steps needed to carry work forward. Good delivery still matters, but organisations responsible for complex services need partners who leave behind stronger capability, better decision-making and the confidence to manage future change independently.
To be clear, the goal is not to eliminate external expertise. Public organisations will always need access to specialist skills and experience that it would not be practical or proportionate to maintain permanently in-house. The challenge is making sure that external expertise complements internal capability rather than substituting for it. That is what I think strategic partnership should mean: bringing in expertise where it adds value, while strengthening the organisation’s ability to make decisions and deliver effectively for itself.
The best strategic partnerships provide more than additional capacity. They give teams access to specialist expertise, proven approaches and perspectives drawn from work across different services and sectors. User-Centred Design and Business Analysis are particularly valuable because they strengthen how evidence is gathered, tested and used. Supported by disciplines such as Service Design and Business Architecture, they help organisations understand complex problems, reduce risk and make better decisions.
One of the biggest misconceptions about knowledge transfer is that it happens at the end. People often think of chunky handovers and detailed repositories of work. Granted, those things are important, but they are not enough on their own. Knowledge transfer works best when it is embedded throughout delivery: in shadowing, show-and-tells, decision logs, design crits and the everyday conversations that help people understand not only what was done, but why.
This is particularly important where product management capability is still developing, or where people are moving into product roles from other parts of an organisation. Effective capability-building begins with understanding both individual and organisational needs. This can include assessing product management maturity against the government DDaT framework, creating individual development plans and identifying the needs of the wider product community.
Case study: For one UK central government department, our product managers co-created a Community of Practice that established a shared language, clearer goals and greater confidence in multidisciplinary teams. Continued support helped the forum become part of the organisation’s own capability, rather than remaining dependent on a supplier.
Case study: For a separate UK central government department, knowledge transfer was built into delivery KPIs across more than 110 statements of work, with 100% of those KPIs met through measured capability uplift, mentoring outcomes and increased client ownership. That matters because it moves knowledge transfer away from a good intention and into accountable delivery. It becomes something teams plan for, revisit and evidence throughout the work.
Good exit also has to be designed from the start. In one of these central government engagements, a planned handover enabled an incoming supplier to understand, operate and continue improving the service. More importantly, the handover shows what it means to treat delivery as a long-term responsibility. It is not enough for a service to work while the original team is around it. Future teams need to understand it, operate it and continue improving it.
There is also a risk reduction argument here. Building capability while delivering helps teams make better decisions earlier, before problems become expensive or difficult to unwind. Supporting this with strong partnership governance gives delivery teams a route to surface risks early, escalate them at the right level and draw on the right specialist support.
Predictable access to specialist capability can also reduce the operational risk created by lengthy recruitment lead times or sudden changes in demand. This matters particularly in large, complex central government services, where stability, accessibility and security are critical. Across the examples described here, services supporting hundreds of thousands of users depend on clear documentation, shared understanding and repeatable ways of working. In environments like these, sustainable delivery cannot depend on one supplier holding all the knowledge. It depends on shared understanding, clear documentation and repeatable ways of working.
This is what a useful partnership looks like to me. You bring in expertise where it is needed, but you don’t keep that expertise contained within the consultancy. You work alongside teams, solve problems together and leave behind things people can actually use, from playbooks and standards to research evidence, service documentation and decision logs. It also means recognising the knowledge that already exists within client teams and helping structure it so it can be shared, reused and built on.
Better partnerships come from better capability. When teams understand the evidence, the risks and the reasoning behind delivery decisions, they are better placed to prioritise. That is where strategic partnership becomes more than delivery support. It becomes a way of strengthening the organisation itself.
If consultancy is going to justify its place in public service delivery, this is the standard it should be held to. Not whether it can produce impressive outputs in isolation, but whether it helps organisations make better decisions, reduce risk and keep improving after the engagement ends. The strongest test of a strategic partnership is whether it leaves the organisation better equipped to deliver, adapt and improve for the people who rely on its services.
A strategic partner should leave an organisation more capable than they found it. Two disciplines play a particularly important role in achieving that: Business Analysis strengthens the evidence and reasoning behind difficult decisions, while User-Centred Design ensures those decisions respond to the needs and behaviours of the people using the service. The next two articles explore how each discipline reduces delivery risk and helps organisations make better decisions.