Field notes · 11 May 2026

What belongs in a weekly infrastructure operations pack

A practical cut of which application analytics should reach supervisors every week — and what can stay in the monthly pack.

Weekly packs fail when they try to mirror every chart available in an operations application. Supervisors need a short set of signals they can act on before the next shift briefing — not a reprint of the vendor’s default dashboard.

Start with availability of critical infrastructure services, open incidents that crossed a severity threshold, and maintenance windows that slipped. Those three items almost always deserve weekly space. Capacity forecasts and trend comparisons usually belong in the monthly pack unless a site is under active constraint.

Ask report owners one question: if this number moved by 10%, would a supervisor change a decision this week? If the answer is no, move it out of the weekly pack. Keep source application names next to each figure so disputes about data provenance are settled quickly.

Infra Data Services often finds that teams can cut weekly packs by a third without losing operational clarity — simply by separating ‘watch this week’ from ‘review this month.’

Back to field notes · Ask about an engagement