Operational Focus

Keep work visible, stable, and prioritized.

The operations page is now inside `apps/web`, giving the production web boundary a real day-to-day delivery surface instead of only a placeholder description.

Audience: IT manager, team leads, service ownersCadence: daily review + weekly pulseView type: operational control room

queue pressure

Open requests in queue

past target

High-priority items needing active watch

steady

96%

Change success rate

planned share

71%

Planned work vs unplanned load

recovery

4.6 hrs

MTTR for high-priority incidents

Workload By Class Of Work

Operational demand should be visible enough that overload shows up before churn does.

Watch capacity

Support requests28 open | 6 older than 10 days

Projects and enhancements19 open | 4 blocked

Security and access work8 open | 2 audit-linked

Data / analysis / reporting5 open | 1 leadership sponsor

Unplanned incidents4 active | 1 service degradation

Incident And Escalation Watch

Items here should show up in daily standup and the IT manager update.

1 service risk

Issue	Owner	Current State	Next Move
Remote access latency for remote staff	Infrastructure lead	Vendor case open, packet analysis in progress	Update incident runbook at 10:30 AM and confirm workaround message.
Leadership escalation: dashboard timing	Data / apps pair	Temporary manual extract used for Friday briefing	Decide whether to automate the data extract this sprint or hold for next cycle.
Identity queue backlog	Service desk lead	2 pending approvals from business owners	Escalate approvals before noon to avoid day-3 breach.