quick-green · weekly tech-ops
Tech-OPs KPIs22.09.2026 - 28.09.2026 · inclusive
Slack Linear Better Stack
Lines under each KPI show the last eleven reporting weeks - 2.7 · 13.7 · 21.7 · 28.7 · 4.8 · 11.8 · 18.8 · 25.8 · 1.9 · 15.9 · 22.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 (15.09-21.09)
▲ 100%
2
Ops support
threads · Slack
+1
1
Incidents
22.09 12:44, 4 min, Sev 2
flow · linear · delta vs prev week
0%
15
Issues shipped
Ready4Live / Deployed / Done
▼ 26%
14
Estimated points
across the 15 issues
0%
5 · 33%
Urgent or Bug
of 15 shipped
▼ 58%
4.1d
Avg cycle time
Ready for Dev → target · 9 of 15
Cycle time is 4.1d across 9 issues. Points-per-issue sits at ~0.9. Flow counts Done since 21.7, so it is not fully like-for-like with weeks before then.
Observation
22.09 - 28.09
- Two small ops items, both resolved same-day. One QA check on Stripe-to-Retool payment sync (a few orders needed manual correction), one deprioritised feature ask for multi-pharmacy admin accounts - ticket filed (QG-1032), not urgent.
- One real incident this week: a brief Supabase-adjacent error spike (Sev 2, 4 min). It landed the same morning as an unrelated bulk Linear status clean-up - worth a quick sanity check that the two aren't connected, though nothing points that way yet.
- Cycle time is back to a normal 4.1d (n=9), after last week's backlog-correction skew. Only one ticket this week (QG-1011) shows the same direct Ready for Dev. → Deployed jump with no tracked work in between - a much smaller footprint than the two-ticket sweep last week.