Infrastructure & Operations | 8 min read
Service continuity is an infrastructure design decision
Why continuity should be treated as part of infrastructure design rather than as a support or governance clean-up exercise.
Open route pieceStart hereReader routes
Choose a route in, based on what you need.
Not a flat archive. A set of pathways through infrastructure, governance, architecture, delivery and leadership judgement, so you can start with the lens that matters most.
Hiring leadsTechnical peersGovernance readers
Reader route
Understand the environment
A first pass through how dependable estates are really held together: continuity, visibility, documentation and what happens after change.
Readers who want the operating context before the frameworks.
Delivery & Improvement | 8 min read
Asset visibility is an operational control, not an admin task
Why asset visibility is a leadership and control issue before it is a tooling issue.
Open route pieceDelivery & Improvement | 7 min read
Documentation fails when it stops describing the live service
Why documentation becomes a service-ownership and control-evidence problem once it stops describing the live service truthfully.
Open route pieceLeadership & Judgement | 6 min read
Post-implementation reviews are where you find out what the project really was
Why post-implementation review should be treated as a service-truth and leadership-learning tool rather than project paperwork.
Open route piece