Service goals
User journeys, indicators, objectives and error budgets.
DevOps & platform
Site reliability engineering consulting
Turn reliability goals into measurable service behaviour, useful alerts and tested recovery work. Make delivery and operations calmer, more repeatable and easier for the owning team to change.
01 / Scope
Work on the system, not around it.
The engagement starts with the architecture and working constraints already in place. We agree the risky paths, make the changes visible and leave ownership with the team running the system.
Observability
Signals that explain impact, cause and recent change.
Response
On-call ownership, runbooks, escalation and incident learning.
Resilience
Capacity, dependency failure, backup and recovery tests.
02 / Method
Make delivery and operations calmer, more repeatable and easier for the owning team to change.
Scope and access are agreed before the work begins. Decisions, changes and residual risk remain visible throughout the engagement.
Trace the current path
Start with evidence, owners and the constraints that shape the safe solution.
Build one working pattern
Prioritise by practical impact and implement with the people who operate the system.
Extend it with the team
Test the changed path, document the decision and hand over a backlog that still makes sense.
03 / What remains
- 01Service level indicators and objectives
- 02Alert and dashboard changes
- 03Incident and on-call runbooks
- 04Reliability improvement backlog
Related work
Continue with the adjacent problem.
04 / Talk to Gritt
What is happening in the system?
Send the cloud, workload or deadline. An engineer will reply and tell you whether this is the right scope.
email