Stabilising systems that have become fragile
Sometimes the problem isn't a missing system but one that's quietly failing: an application nobody fully understands any more, a developer or supplier who has moved on, deployments everyone is nervous about, or cloud infrastructure that has grown expensive and unreliable. I start by working out what's actually there and what state it's in, then stabilise it, document it and make it safe to change. From there, the business can decide whether to improve it, hand it on, or plan a replacement, based on facts rather than fear.
- Inherited or orphaned applications with little or no documentation
- Fragile deployments and environments nobody wants to touch
- Cloud setups that are costly, insecure or hard to reason about
- Performance problems, outages and recurring failures
- Getting a stalled or troubled project back on track