Your teams are working hard. Why is delivery still so difficult?
Helping engineering leaders reduce dependencies, improve team effectiveness and create better conditions for delivery.
You've invested in talented people, established teams and engineering practices, yet delivering change still feels harder than it should.
I help engineering leaders understand what's holding delivery back and make informed changes to team boundaries, responsibilities, interactions and the technology that supports them.
When capable teams struggle to deliver
The problems aren't always obvious when you look at individual teams. People may be working effectively within their own responsibilities, yet the way work moves across the organisation creates delays, frustration and unnecessary effort.
You might recognise some of these situations:
Even simple changes involve multiple teams. Work passes through handovers, queues and approvals before it can reach users.
Teams are constantly coordinating rather than delivering. Dependencies and competing priorities make it difficult to plan work or make progress independently.
Responsibilities and decision-making are unclear. Work falls between teams, decisions are repeatedly escalated, or several groups believe they're responsible for the same thing.
Your architecture makes change difficult. Shared systems, tightly coupled components or fragile integrations mean changes in one area can have unexpected consequences elsewhere.
Platform and specialist teams are becoming bottlenecks. Other teams depend on a small number of specialists for routine changes, support or decisions.
You're considering a reorganisation but aren't sure it will help. Existing boundaries may no longer reflect how work is delivered, but it's difficult to know what an alternative should look like.
These symptoms are often connected. Changing team structures alone may achieve little if technical dependencies, unclear responsibilities and existing ways of working remain unchanged. Understanding those relationships is essential to making improvements that last.
Creating better conditions for delivery
I work alongside engineering leaders and teams to understand the current delivery system, identify the constraints that matter and explore practical improvements.
Rather than prescribing a particular team structure or operating model, we'll examine how people, responsibilities, technical systems and work fit together.
Depending on your context, our work may focus on four connected areas.
Understand how work really gets done
Explore how work moves from user needs through the teams and systems involved in delivering it.
Make dependencies, handovers, decision points and recurring delays visible, creating a shared understanding of what’s helping or hindering delivery.
Clarify responsibilities and team interactions
Identify where stewardship is unclear, responsibilities overlap or teams depend on one another unnecessarily.
Explore team boundaries and interaction patterns that enable clearer decisions, effective collaboration and greater independence where it matters.
Address architectural and organisational constraints
Examine how shared systems, platform capabilities, technical coupling and organisational arrangements affect delivery.
Identify opportunities to reduce friction and improve team effectiveness without assuming a major restructure or architectural rewrite is required.
Explore, test and evolve better arrangements
Develop and evaluate potential changes with leaders and teams, testing their implications against real delivery scenarios.
Support the introduction of agreed improvements and learn from their effects rather than treating a new organisational chart as the final outcome.
The objective isn't simply to reorganise teams. It's to create an environment where teams can work more effectively, make decisions and deliver with fewer unnecessary constraints.
Start with understanding, not restructuring
We can begin with a focused engagement to understand what's constraining delivery, explore alternative arrangements and establish a practical direction for improvement.
1. Build a shared understanding
We'll work with leaders, engineers and relevant stakeholders to examine how work is delivered, how responsibilities are distributed and where dependencies or delays occur.
What you'll gain: A shared view of the current delivery system, the constraints having the greatest impact and the opportunities worth exploring.
2. Explore and evaluate improvements
We'll develop potential changes to team boundaries, stewardship, interactions or technical arrangements, examining their trade-offs against real delivery scenarios.
What you'll gain: Practical options for improvement, greater clarity about where responsibilities and decisions should sit, and an evidence-informed basis for choosing what to change.
3. Make changes and learn from the results
We'll support the introduction of agreed changes, clarify how teams will work together and establish meaningful ways to assess their effects.
What you'll gain: Clearer working arrangements, actionable next steps and evidence to guide further improvements as your organisation evolves.
The outcome: A shared understanding of what's constraining delivery, informed decisions about how teams and technology should work together, and practical changes that improve the conditions for effective delivery.
Sociotechnical architecture grounded in real-world experience
I've spent more than 20 years working across software engineering, technical leadership, architecture and organisational change.
My work brings together an understanding of software systems with the human and organisational factors that determine how effectively teams can deliver.
I'm a Team Topologies Valued Practitioner, creator of User Needs Mapping and author of User Needs Mapping: Aligning Teams Around What Matters.
I use approaches such as User Needs Mapping and the Team Topologies pattern language to help people develop a shared understanding of their organisation and make informed decisions about team boundaries, interactions and the capabilities they support.
At Blue Lagoon Iceland, growing the engineering function hadn't resolved the handovers, competing priorities and fragmented responsibilities affecting delivery.
Working with people across technology, product and the wider business, we explored existing workflows, user needs and capabilities to help develop more effective team arrangements.
From delivery constraints to more effective teams
Let's improve how your teams deliver
If your teams are busy but delivery remains difficult, let's explore what's happening.
You don't need to have decided whether the answer is restructuring teams, changing your architecture or introducing new ways of working.
We'll discuss the challenges you're facing, what you're trying to improve and whether there's a useful way I can help you move forward.