Codifying Delivery Practice - Internal Capability
Sector: Internal
Role: Principal Software Engineer
Focus: Engineering strategy and delivery enablement
As the organisation shifted from large, multi-year projects to smaller, faster-paced work, teams no longer had the luxury of bedding in.
Delivery still worked - but inconsistently.
What “good” looked like lived in people’s heads. Onboarding dragged. Practices varied.
We needed to codify what worked - fast - without killing autonomy.
The Challenge
- Delivery practices evolved through habit, not design
- Onboarding relied on memory and individual handover
- Pace, quality, and process varied across teams and timeframes
- Attempts to “align” often turned into theatre - or got ignored
The ask: Can we codify delivery - in a way that enables autonomy, clarity, and fast starts?
My Role
As Principal Engineer, I authored or co-authored three core strategy artefacts:
- Facilitating High-Performing Teams - a research-backed guide to sustainable team culture
- Ways of Working Guide - a practical playbook for team setup and agile delivery
- Engineering Strategy - a unifying model for architecture, capability, and delivery maturity
Each was built from the ground up - based on 20+ years of embedded experience, not frameworks.
And I didn’t just write them - I socialised the thinking across the org through regular, low-friction channels: twice-weekly MSTeams posts that surfaced themes, patterns, and practical prompts.
Because most people don’t read the document - but they will use what travels.
Key Contributions
- Codified culture and delivery into clear, practical guidance
- Aligned tooling, team norms, and architectural direction
- Reduced onboarding drag and delivery ambiguity
- Built foundations for repeatable enablement, internal review, and healthy autonomy
Strategic Value
- Turned tacit knowledge into shared clarity
- Enabled consistency without command-and-control
- Created principles that scaled with teams - and stuck under pressure