Practice
Technology Leadership
Scale the decisions, not the meetings.
Structure and architecture mirror each other whether or not anyone designed that. When delivery slows, the fix is usually in team boundaries, decision rights and platform ownership rather than in another process.
The problem
The organisation grew and the decision-making structure did not. Everything still routes through the people it routed through when the team was a third of the size.
Handoffs everywhere
Teams wait on each other in ways nobody designed, because the boundaries were drawn for an org chart rather than for flow.
Centralised judgement
A small number of people are in every decision, which makes them the constraint and makes their absence a risk.
Platform as a side project
Internal tooling exists but has no product owner, so it accumulates features nobody asked for and skips the ones everybody needs.
Senior capacity is spent on coordination, and the leadership layer the organisation needs never gets built because nobody has time to build it.
The model behind it
Team Topology and Conway's Law
Your architecture will mirror your team structure whether you design it to or not. Conway's Law is not a warning — it is a design tool. If you want loosely coupled services, you need loosely coupled teams.
- Stream-aligned
- Own customer outcomes end to end
- Platform
- Provide self-service capabilities that remove cognitive load
- Enabling
- Unblock adoption of new practices and technologies
- Complicated-subsystem
- Manage components that require specialised knowledge
Fix the team structure and the architecture often fixes itself. Ignore it and no amount of architectural documentation will compensate.
Try this week, without booking anything
- Draw your current team structure. Does this map produce the architecture you want?
- Run a Conway's Law audit — compare the org chart to the system architecture diagram.
The programme
The Leadership Programme
A leadership model that distributes decisions without losing coherence — team boundaries, decision rights, and a platform with an owner.
- Who it is for
- CTOs, VPs of Engineering, heads of platform, and the senior engineers being asked to lead without the title.
- How it runs
- Modules run half-day to two days. Facilitated sessions work on your own teams and org chart; the intensives carry follow-up coaching.
- Catalogue
- 10 modules across 4 tracks, plus 5 facilitated sessions
Not sure where to start? The core arc is Leadership Fundamentals → Organisation & Team Design → Delivery Systems. Everything else stays available — take a single module or sequence a track.
- Conway's Law & Team Boundaries1-day workshopYour architecture mirrors your communication structure whether you designed it that way or not — which makes team boundaries an architectural decision.
- Decision Rights & Delegation1-day workshopDecisions made at the wrong altitude are the commonest source of both bottleneck and drift — which makes delegation a design problem, not a trust problem.
- Cognitive Load & Team Interfaces1-day workshopA team can only hold so much — and the interaction modes between teams are what decide whether that limit is respected or quietly exceeded.
- Delivery Metrics That Mean Something1-day workshopHow to replace delivery dashboards that measure activity with signals that tell you which dimension is actually holding delivery back — and what to fix first.
- Fitness Functions Instead of Review Boards1-day workshopBatch review cannot govern continuous change. How to encode architectural invariants as automated checks — and what still belongs to the board.
- Execution Stability & Structured Refactoring1-day workshopDelivery slows because structural entropy accumulates unmeasured. Classify refactoring into dicing, slicing and peeling to restore predictability.
- Paying Down Debt Through Feature Work1-day workshopDebt accumulates faster than refactoring projects can remove it. Fund architecture improvement through the product roadmap instead of competing with it.
- Platform as a Product1-day workshopAn internal platform with no product owner builds what nobody asked for and skips what everybody needs — adoption, not completeness, is the only measure that counts.
- Developer Experience as a Control System1-day workshopDevEx is not a perk — it is the set of operating conditions that governs how fast and how safely change moves through your delivery system.
Facilitated sessions
Worked on your material, not a case study
The modules are worked through; the sessions are worked on your own structure. Team topology, delivery, platform and distributed leadership all run against your org chart rather than a case study. Fractional leadership is the delivery mode when the work needs someone inside the organisation rather than in front of it.
The thinking behind it
Read before you book
How it went somewhere else
Building Architecture Governance Without Slowing Down
How a HealthTech startup embedded architecture governance into a fast-moving product team — achieving compliance without losing velocity.
- Client
- Pre-Seed HealthTech (12 employees)
- Industry
- Healthcare
- Duration
- 12 weeks (fractional engagement)
Free 30-minute diagnostic
Where is the coordination going?
Bring your team structure and one delivery that took longer than it should have. Thirty minutes is usually enough to see which boundary caused it.
Not the right one?