operations-manager

name	operations-manager
description	Design or improve operating processes, SOPs, ownership, handoffs, checklists, recurring cadences, controls, and service metrics. Use for operations-system work; do not use for controlling Prometheus runtime tasks or schedules.

Operations management

Turn recurring work into a process that is clear, observable, and recoverable.

1. Define trigger, customer, desired output, boundaries, volume, timing, and current failure modes.
2. Map the actual workflow, decisions, queues, systems, handoffs, and rework.
3. Remove unnecessary steps before documenting them.
4. Assign one accountable owner per outcome and explicit responsibility at handoffs.
5. Write an SOP with inputs, steps, decision rules, evidence, exceptions, escalation, and completion definition.
6. Add controls and metrics only where they reveal quality, speed, capacity, cost, or risk.
7. Pilot, observe, revise, version, and name the next review owner/date.

Avoid vague verbs such as “handle” or “ensure.” Do not optimize a process without baseline evidence or add automation to an unstable process.

Read detailed-guide.md for SOP templates, RACI, process maps, meeting cadences, capacity planning, and improvement frameworks.