How I lead delivery
Six moves I use to turn complexity into execution.
The same six moves, whether I'm running a programme as a project manager or a team as a Scrum Master. Each one is backed by something I've actually built or run.
The six moves
- Requirements gathered in detail at intake
- 21 stakeholders aligned across two programmes
- Delivery delays down 33% on a before-and-after comparison
- 1
Clarify
What problem are we actually solving?Turn ambiguity into a clear problem, scope and outcome. Requirements are gathered in detail at intake, including through an AI agent I built in Microsoft Copilot Studio.
- 2
Structure
What needs to be defined?Build the plan, milestones, governance and delivery model. Standard estimation benchmarks for every project type; plans, milestones and Gantt-based timelines; backlogs refined and estimated with product owners.
- 3
Align
Who needs to agree?Create alignment across stakeholders, teams and decision-makers. Ownership made explicit through RACI and service expectations through SLAs; alignment workshops and conflict resolution across 21 stakeholders in two cross-divisional programmes.
- 4
Execute
How do we move the work?Manage delivery, dependencies, risks, priorities and change. Scrum for distributed teams across Sweden and India; Kanban flow with WIP limits and cycle time; RAID logs, dependency tracking and impediment removal across concurrent workstreams; leadership reporting through Jira and Power BI dashboards.
- 5
Improve
What is slowing us down?Use data, feedback and retrospectives to improve the system. Structured retrospectives on high-stakes projects that turn feedback into actions. Across the process changes I introduced, delivery delays fell 33% on a before-and-after comparison.
- 6
Scale
How do we make improvement repeatable?Turn what works into repeatable operating standards. Plain-language SOPs; PM onboarding walkthroughs; vendor onboarding; an AI-assisted SOP and estimation framework adopted beyond my own role.
Operating principles, not slogans.
Clarity before activity
Don't start by tracking tasks. Start by understanding the outcome.
Structure without bureaucracy
Governance should make delivery clearer, not slower.
Visibility before escalation
Good reporting surfaces problems early.
People, process and technology
Sustainable delivery improvements need all three.
Improvement becomes the system
Don't solve the same problem twice.
AI should remove friction
Use AI where it improves speed, clarity and consistency, not simply because it's available.
From vision to execution. From execution to business value.
Complex delivery needs structure. Let's talk.