Capability, not consulting

The best outcome of a consulting engagement is one where the client never needs you again. That should be the starting point, not an accident.

28 May 2026 ยท 4 min read

Abstract illustration of capability transfer from external to internal teams

There is a version of consulting where you walk into an organisation, do clever work for six months, hand over a slide pack, and leave. The client is impressed. The slides sit in a shared drive. Nothing changes. You get called back eighteen months later to do it again.

I have done that version. I am not proud of it.

The version I am trying to build now looks different. It starts with the same discovery, the same benchmarking, the same current-state mapping. But the point of the engagement is not to produce a recommendation. The point is to leave behind a team that can do the next one without me.

What this looks like in practice

I have been embedded inside the University of Wollongong's Operational Excellence Programme for the better part of a year. The work covers academic consideration, reasonable adjustments, recruitment, onboarding, and complaints redesign. Five separate process streams, each with its own stakeholders, its own politics, its own history of failed attempts.

The instinct in traditional consulting is to own the methodology. You bring your framework, run the workshops, write the future-state maps, present the roadmap, and hand it over. The client gets a deliverable. You get a reference. Everyone is happy, briefly.

What we did instead was build the capability inside the team. The five-section working pack (current state, pain points categorised by process, people, policy, and system; external benchmarks; improvement opportunities; future-state map with implementation roadmap) is not a proprietary tool. It is a repeatable method that the internal team now runs on its own.

The programme manager, Beth, runs the methodology across new streams without calling me first. The stakeholder engagement approach, the three-tier opportunity framework (quick wins, medium-term, long-term transformational), the way we sequence executive sign-off: all of it has been absorbed into how the team works. Not because I wrote a training manual, but because they did the work alongside me and internalised the pattern.

Why this matters now

Australian universities are about to get much more careful about consulting spend. The sector is under real financial pressure. Federal funding is tightening. Student numbers are volatile. International revenue, the thing that subsidised a decade of institutional ambition, is no longer a certainty.

In that environment, a university that spends six figures on a consulting engagement wants to know it is buying something that lasts. Not a report. Not a set of recommendations that require another engagement to implement. They want to know that the investment builds something permanent inside the institution.

This is not a new idea. Plenty of firms talk about "capability transfer" in their proposals. The difference is whether you design the engagement around it from day one, or bolt it on at the end as a two-page "transition plan" appendix.

Designing around it means accepting some uncomfortable trade-offs. It means spending time teaching methods that you could execute faster yourself. It means letting the internal team run workshops that you would have run more efficiently. It means building their confidence with stakeholders instead of being the external authority in the room.

It also means being honest about scope. Not every engagement suits this model. Sometimes an organisation genuinely needs an external pair of hands for a fixed period, and the right move is to do the work and leave cleanly. But when the problem is structural (when the organisation will face this kind of challenge again, in a different stream, with different stakeholders), the only durable answer is internal capability.

The obvious tension

I am a consultant arguing that organisations should need fewer consultants. The irony is not lost on me.

But I think this is the only version of the work that holds up under scrutiny. If a university pays for a six-month engagement and the only lasting artefact is a PDF, that is not a good outcome. If the same university pays for a six-month engagement and three of its internal staff can now run a process redesign from discovery through to implementation, that is a different proposition entirely.

It might mean fewer repeat engagements for me. It might mean a smaller book of active clients at any given time. But it also means the clients I do work with are genuinely better off when I leave, and that is the only referral that compounds.

The best consulting engagement is the one after which the client never calls you back. Not because the relationship broke down, but because they do not need to. If that is the starting point, the whole design of the work changes.

And if the sector is about to scrutinise every dollar spent on external advice (it is), then the consultants who survive will be the ones who can honestly say: the thing I built inside your organisation is still working, two years later, without me.

That should be the test. It is the one I am trying to hold myself to.


Get the next one.

A short essay, irregular schedule. No spam, no upsell.