05 · Leadership and Organisational Development
Delivery processes across distributed teams
Distributed engineering organisation.
Situation
An engineering organisation with teams at several locations had no consistent delivery process. Every team tracked work differently. Sprint commitments were made and missed without anyone being able to say why.
Leadership had no reliable view of what was in progress, what was blocked and what actually got finished. The result: unpredictable output, a leadership team unable to plan, and a delivery culture in which, tacitly, nobody believed commitments were binding any more.
Approach
I introduced agile working models that matched how the organisation actually worked — not what the textbook says.
Kanban created visibility across all teams, so that work and blockers were visible to everyone who needed to see them. Sprint structures with explicit commitments were added, as were retrospectives that led to real process changes rather than documents nobody reads.
I stayed through the first complete delivery cycle — to see whether the model holds under pressure, not only when things are calm.
Result
Delivery visibility improved organisation-wide. Work in progress, priorities and bottlenecks became more transparent and created a better basis for planning and leadership decisions. Teams gained clearer working structures, less ad-hoc re-prioritisation and a better ability to align commitments across distributed locations.
Feedback
“He applies methods deliberately and effectively, shares his knowledge openly and addresses conflict constructively. He combines focus with honest reflection and is someone the team can rely on.”