quick-green · weekly tech-ops
Tech-OPs KPIs15.09.2026 - 21.09.2026 · inclusive
Slack Linear Better Stack
Lines under each KPI show the last eleven reporting weeks - 23.6 · 2.7 · 13.7 · 21.7 · 28.7 · 4.8 · 11.8 · 18.8 · 25.8 · 1.9 · 15.9 - current week marked; hover a point for its value. 8-12.7 was not reported. 8-14.9 was not reported. Windows vary, the flow definition changed on 21.7.
ops & reliability · delta vs prev week (01.09-07.09)
▼ 75%
1
Ops support
thread · Slack
0%
0
Incidents
none · 1 false trigger
flow · linear · delta vs prev week
▼ 12%
15
Issues shipped
Ready4Live / Deployed / Done
▲ 12%
19
Estimated points
across the 15 issues
0%
5 · 33%
Urgent or Bug
of 15 shipped
▲ 112%
9.8d
Avg cycle time
Ready for Dev → target · 5 of 15
Cycle time is 9.8d across 5 issues. Points-per-issue sits at ~1.3. Flow counts Done since 21.7, so it is not fully like-for-like with weeks before then.
Observation
15.09 - 21.09
- The one support case was user-side. A customer received the SMS but with no usable code, and WhatsApp failed too - which points to a device or carrier-side filter, not a QG fault. Same recurring shape: once delivery fails downstream of Twilio, ops has little visibility and few levers.
- The incident trigger was a false alarm. No real incident - a monitoring alert fired wrongly. Worth a quick look at the threshold, since repeated false positives quietly erode trust in the on-call signal.
- Flow includes two backlog corrections and one real queue outlier. Two of the 15 shipped issues jumped straight from Ready for Dev. to Deployed with no tracked work in between - pure status clean-up, not a real cycle, so they're excluded from the cycle-time average. The remaining 5-issue subset averages 9.8d, driven mostly by one ticket that queued 13 days before anyone picked it up - worth a look at whether Ready for Dev. triage is keeping pace.