Rebuild your org around services
Restructure how your organisation is built, funded and run — around the outcomes it delivers, not the functions it inherited.
The idea
Your organisation already delivers hundreds of services. It just isn't built to deliver any of them well.
Return from parental leave. Move team. Resolve a grievance. Real things people need, each one currently spread across three teams and an intranet. Nobody designed them badly. Nobody designed them at all.
A service is a commitment, not a diagram: one name people recognise, one owner, one team, one measure. Which makes this structural — teams, budgets and decision rights all move.
Underneath sits the part that makes AI compound: the patterns. The same steps repeat across every service — verify, decide, progress, answer. Capture one well — as a documented pattern, a built and automated one, or eventually a team that owns it — and every service using it gets better. Improve it once and every service improves that day.
How I help
Map demand, not structure.
What people are actually trying to do, in their words.
Score and sequence it.
Ranked on value and feasibility. A published queue, not a wish list.
Find the patterns.
The steps that repeat across services — verify, decide, progress, answer. How many services need each one is the business case.
Design the way in.
However people actually reach a service — a form, a chat, a search bar — that's a design decision too, not an accident of whichever system was already there.
Redesign the structure.
Teams, funding, decision rights and governance drawn around outcomes — with shared capability given the right home: a library, a built pattern, or, where it's earned, a team of its own.
Build the capability to keep going.
So conversion continues without me.
What you get
- A service catalogue
Every outcome your organisation delivers, named the way people ask for it.
- A prioritised conversion backlog
Scored on value and feasibility, published so everyone knows what is coming and when.
- A pattern library
The repeatable steps underneath your services — verify, decide, progress, answer — with the reuse numbers that justify investing in them.
- Patterns built to the right level
Documented for some, automated for others, owned by a dedicated team where the reuse earns it. The form follows the maturity, not the other way round.
- An operating model that matches
Teams, funding, ownership, decision rights and governance redrawn around outcomes.
- Internal capability to convert
The roles, rhythm and skills to keep going without buying the ability back in.
Why it matters
Big-bang restructures bet everything on one design being right. One service at a time, you're never more than weeks from evidence — and each conversion makes the next one cheaper.