Before we start — the one thing to hold onto
Most organisations think they have a leadership problem. They don't. They have a decision rights problem. I've sat in rooms with engineering managers who were held accountable for outcomes they had no authority to influence. And directors who couldn't make a decision without three levels of approval.
Leadership isn't about having all the answers. It's about making sure the right people have the authority to decide — and the accountability to own those decisions.
That one idea changes everything. It turns bottlenecks into clarity.
Keep it in mind.
Purpose
The goal of this workshop is concrete: build leadership capabilities for distributed, AI-augmented organizations with clear decision rights and effective team management for the future of work.
I've seen teams scale by adding managers — and then watch decision-making slow to a crawl. Not because the managers were bad — because nobody decided who should decide what. This workshop fixes that.
You'll leave with a decision rights matrix, distributed leadership playbook, and OKR implementation framework.
Who Should Attend
This workshop is designed for the people who lead teams — and the people who lead the people who lead teams.
- Engineering Managers, Tech Leads, Directors
- CTO, VP Engineering, C-level Technology Leaders
- Product Managers, Engineering Leaders
Typical team size: 8-15 participants
Format: In-person or virtual (hybrid available)
Try it yourself — The decision bottleneck audit
Before the workshop, think about the last decision that got stuck. Who needed to approve it? Who actually understood the problem? Who was accountable for the outcome?
If those three people weren't the same person, that's exactly why this workshop exists.
What You'll Achieve
By the end of this workshop, you will have:
- Decision rights frameworks for autonomous organisations and AI agents
- Distributed technology leadership practices for remote/hybrid teams
- Engineering culture for AI augmentation, change management, and upskilling
- Fractional leadership engagement models (CTO for AI, VP Engineering)
- Cross-functional AI product leadership alignment
- OKR/V2MOM implementation with AI objectives
- Career ladders, role clarity, and accountability structures
- Team topology and interaction modes design
These aren't management theory. They're operating models you can deploy in your next quarter.
Typical Outcomes
Immediate outcomes (within 1 week):
- Decision rights matrix drafted and reviewed
- Leadership principles and behaviours defined
- Role clarity survey conducted with teams
Short-term outcomes (within 1 month):
- Decision rights framework rolled out to teams
- Team topology redesigned for product-alignment or enabling teams
- OKR process established with AI objectives included
- Engineering career framework updated
Long-term outcomes (3-6 months):
- Faster decision-making with clear accountability
- Reduced bottlenecks and escalations
- Higher team engagement and satisfaction
- Successful fractional leadership integration (if applicable)
Workshop Structure
Day 1:
- Morning (3 hours): Organisational design, decision rights, and team topology
- Afternoon (3 hours): Distributed leadership practices and AI agent accountability
Day 2:
- Morning (3 hours): OKR/V2MOM setting, career frameworks, and performance metrics
- Afternoon (3 hours): Change management, upskilling, and implementation roadmap
Total duration: 2 days
Adjustable: Can be modularised into half-day sessions on specific topics
Try it yourself — The escalation map
Look at your last five escalations. What decision was stuck? Who should have been able to make it? Why couldn't they?
Most teams I work with find their escalations aren't about complexity — they're about unclear authority.
Prerequisites & Preparation
Before the workshop:
- Organisational chart and team structure
- Current decision-making bottlenecks documented
- Engineering effectiveness survey results (if available)
- List of AI agents or automation currently in use or planned
- Existing performance and goal-setting frameworks (OKRs, KPIs, V2MOM)
Recommended team composition:
- 1-2 CTO or VP Engineering
- 3-5 Engineering Managers or Directors
- 1-2 Tech Leads or Principals
- 1 HR Business Partner or Talent Lead
- 1 Product Leader or Product Manager
- Optional: Fractional leader candidacy discussion
How to know if this landed
You'll know this has landed when someone stops escalating a decision and starts asking "who owns this?" They can explain the decision rights matrix in their own words. They understand why team topology matters and how to design it. They treat OKRs as alignment tools, not performance weapons.
What changes when the mental model clicks
I've run this session with leadership teams ranging from startups with flat structures to enterprises with seven management layers. The gap at the start is usually not about intent — everyone wants clarity — it's about not having a framework for deciding who decides.
What changes after this workshop:
Teams stop treating decision rights as implicit and start treating them as explicit. The decision rights matrix exercise tends to be the moment things click — people realise they've been holding managers accountable for decisions they had no authority over.
The team topology design tends to immediately change how people think about structure. They start asking "how should these teams interact?" instead of "who reports to whom?" Their decisions get faster. Their escalations drop. They stop blaming "slow management" when the real problem was that nobody clarified authority.
Book a Workshop
Ready to give your leadership team the decision rights framework they need?
or
2-day leadership workshop includes organisational design, decision rights framework, team topology mapping, OKR implementation, career framework design, and change management planning.