The process that I followed is not unique but does come with experience. It can be quickly summarised into:
Discover → Diagnose → Frame → Mobilise → Enable → Stabilise & Learn
Phase 1: Discover
Step 1: Rapid Landscape Scan
Actions:
Build an immediate, imperfect view of the environment
Avoid waiting for complete artefacts
Inputs & Prompts:
Conversations
Existing boards/tools (if any)
Observations
Outputs:
Initial mental model of work and pressure points
Success Measures:
You can describe ‘what’s happening’ without needing validation from reports
Step 2: Structured Leadership Conversations
Actions:
Meet 1:1 with managers and delivery leads
Use consistent questioning
Inputs & Prompts:
Now / Next / Later
Why it matters
Timeframes
Dependencies
Risks
Needs from leadership
Outputs:
Pattern recognition across teams
Success Measures:
Repeated themes and inconsistencies become visible
Phase 2: Diagnose
Step 3: Identify Weak Signals
Actions:
Look for:
‘Everyone knows’ issues
Cross-team dependencies
Time-bound risks
Low ownership areas
Outputs:
Candidate risks
Success Measures:
You can articulate the issue clearly and confidently
Step 4: Validate and Deepen Understanding
Actions:
Test assumptions
Confirm scope and impact
Identify affected systems, teams, and processes
Outputs:
Defined problem statement
Success Measures:
The issue moves from vague → specific
Phase 3: Frame
Step 5: Translate to Business Risk
Actions:
Reframe into:
Continuity risk
Customer impact
Financial exposure
Strategic misalignment
Outputs:
Executive-ready narrative
Success Measures:
Non-technical stakeholders immediately understand urgency
Step 6: Secure Sponsorship
Actions:
Present:
Risk
Timeline
Options
Consequences
Outputs:
Priority endorsement
Decision rights
Organisational backing
Success Measures:
Work is officially recognised and supported
Phase 4: Mobilise
Step 7: Decompose into Workstreams
Actions:
Break problem into outcome-based streams
Outputs:
Clear work packages
Success Measures:
Work can be parallelised and assigned
Step 8: Reduce Scope Where Possible
Actions:
Identify:
Workarounds
Alternatives
Redundant effort
Outputs:
Reduced or simplified scope
Success Measures:
Less work required without compromising outcomes
Step 9: Assign Ownership
Actions:
Allocate a clear owner per stream
Outputs:
Named accountability
Success Measures:
No workstream is “floating”
Step 10: Establish Visibility
Actions:
Create shared view (e.g. Now/Next/Later, program board)
Outputs:
Transparent priorities and progress
Success Measures:
Anyone can understand what matters quickly
Phase 5: Enable
Step 11: Tailor Delivery Approach
Actions:
Match method to work type:
Agile
Operational
Project-based
Hybrid
Outputs:
Fit-for-purpose delivery model
Success Measures:
Teams are not constrained by mismatched process
Step 12: Coach Leaders
Actions:
Support delivery leads in:
Planning
Decision-making
Team enablement
Escalation
Outputs:
Improved leadership capability
Success Measures:
Leaders adapt their style to suit the situation
Step 13: Enable Team Ownership
Actions:
Shift from:
Task assignment → Problem ownership
Encourage:
Self-organisation
Collaboration
Initiative
Outputs:
Increased engagement and speed
Success Measures:
Teams step forward without prompting
Step 14: Monitor Flow
Actions:
Track:
Wait states
Bottlenecks
Handoffs
Lag time
Outputs:
Realistic delivery insights
Success Measures:
Risks are identified early, not after delay
Phase 6 — Stabilise & Learn
Step 15: Adapt Scope
Actions:
Shift to MVP where required
Reprioritise based on constraints
Outputs:
Achievable delivery plan
Success Measures:
Outcomes delivered despite disruption
Step 16: Embed Learning
Actions:
Capture:
Leadership shifts
Team behaviours
Delivery improvements
Outputs:
Reusable capability
Success Measures:
Organisation performs better next time