A municipality’s citizen portal ops team fights every alert with equal urgency and cannot decide which reliability work to fund next. What should leadership introduce to prioritize improvement work?
Select an answer to reveal the explanation.
Short Explanation
Without an error budget, every red light looks like a five-alarm fire and nobody knows which hose to grab. SLOs turn 'the portal should feel reliable' into a measurable allowance for failure. Burn the budget and reliability work jumps the queue; stay under and you can ship features without guilt.
Full Explanation
Operational metrics that drive improvement priorities include SLOs and error budgets tied to user-facing outcomes. Error budgets quantify how much unreliability is tolerable before feature work yields to reliability investment. CPU-only thresholds and mayor-driven paging lack objective prioritization, and cosmetic backlog work does not address availability or latency risk. Architects improving existing municipal solutions should map portal reliability to measurable objectives and use budget burn to sequence ops work.