ChatGPT Prompts for Operations Managers

<context> You are an operations analyst defining a measurement framework. The function to measure is [PROCESS], owned by [TEAM]. The business goal is to improve throughput and quality without raising cost. </context> <task> 1. Propose 6-8 KPIs spanning efficiency, quality, cost, and customer-experience dimensions. 2. For each KPI give: a one-line definition, the exact formula, the data source, the reporting cadence, and a sensible starting target. 3. Distinguish leading indicators from lagging indicators. 4. Warn me about any KPI that is easy to game and suggest a counter-metric to balance it. </task>

<context> You are designing a weekly operations dashboard for [TEAM]. The KPIs we already track are listed below this prompt. </context> <task> 1. Recommend a dashboard layout that surfaces status at a glance: which metrics go top-row, which go in detail panels, and why. 2. For each metric, recommend the best visualization (trend line, gauge, bar, table) and a red/amber/green threshold. 3. Specify the time comparisons to show (week-over-week, vs target, rolling 4-week average). 4. List the data refresh schedule and who owns keeping each source current. </task>

<context> You are an operations analyst investigating why a metric moved. The KPI is [PROCESS] and it changed materially this period for [TEAM]. I will paste the recent numbers below. </context> <task> 1. List the most likely root causes for the movement, ranked by probability. 2. For each cause, state the additional data I should pull to confirm or rule it out. 3. Identify whether the change is signal or noise given the volatility in the numbers. 4. Recommend the single next diagnostic step and the question it answers. </task>

<context> You are an ops leader translating a quarterly goal into measurable objectives for [TEAM]. The high-level goal is to make [PROCESS] faster and more reliable. </context> <task> 1. Write 1 clear Objective and 3-4 Key Results that are quantified, time-bound, and outcome-based (not task lists). 2. For each Key Result, state the current baseline, the target, and the metric source. 3. Flag any Key Result that depends on another team and name the dependency. 4. Suggest a mid-quarter checkpoint metric that predicts whether each KR will land. </task>

<context> You are standardizing how [TEAM] talks about performance so everyone counts [PROCESS] the same way. I will paste the metrics currently in use below. </context> <task> 1. For each metric write a single canonical definition, the precise formula, included and excluded cases, and the unit. 2. Highlight any two metrics that are commonly confused and write a sentence distinguishing them. 3. Note where the same metric currently has conflicting definitions across teams and propose the one to adopt. 4. Output the result as a glossary table sorted alphabetically. </task>

<context> You are an operations planner forecasting whether [TEAM] can absorb upcoming demand for [PROCESS]. I will paste current headcount, throughput rates, and the demand forecast below. </context> <task> 1. Calculate current capacity, projected demand, and the gap for each of the next 3 months. 2. State your assumptions explicitly (utilization rate, ramp time, shrinkage for leave and meetings). 3. Recommend whether to hire, redistribute work, or improve process, with the trade-offs of each. 4. Identify the month where the gap first becomes critical and the lead time needed to act. </task>

<context> You are scheduling [TEAM] to cover [PROCESS] across operating hours. I will paste the demand-by-hour or demand-by-day pattern and the available staff below. </context> <task> 1. Propose a shift schedule that matches staffing to the demand curve while honoring break and rest rules. 2. Highlight any hours that are over- or under-staffed and the cost of each. 3. Build in coverage for one unplanned absence without breaking SLAs. 4. Present the schedule as a grid of people by time slot. </task>

<context> You are an ops manager with more work than capacity for [PROCESS]. [TEAM] can complete a limited number of items this sprint. I will paste the backlog with effort and impact estimates below. </context> <task> 1. Score each item using a weighted model (impact, urgency, effort, risk of delay) and show the scores. 2. Recommend what to do now, what to defer, and what to drop entirely. 3. Flag any low-effort high-impact 'quick wins' to pull forward. 4. Note any dependencies that force a particular sequence. </task>

<context> You are resourcing a project that touches [PROCESS] and requires people from [TEAM]. I will describe the deliverables, timeline, and available skills below. </context> <task> 1. Break the project into workstreams and estimate the effort (person-days) for each. 2. Map required skills to available people and flag any skill gap. 3. Build a week-by-week resource allocation showing who works on what and at what percentage. 4. Identify the over-allocated weeks and propose how to smooth the load. </task>

<context> You are stress-testing capacity for [PROCESS] under a change. The baseline numbers for [TEAM] are below. The scenario to model is described after them. </context> <task> 1. Recalculate throughput, utilization, and SLA attainment under the scenario. 2. Compare baseline vs scenario side by side and quantify the delta. 3. Identify the breaking point: at what demand or staffing level does the operation fail its SLA. 4. Recommend the cheapest mitigation that keeps the SLA intact. </task>

<context> You are sourcing a new supplier for [VENDOR] services to support [PROCESS]. I will describe our requirements and constraints below. </context> <task> 1. Write a complete RFP with: background, scope of work, requirements (must-have vs nice-to-have), service levels, pricing format requested, evaluation criteria with weights, and timeline. 2. Include 10 specific questions that reveal whether a vendor can actually deliver, not just claim to. 3. Add a scoring rubric I can use to compare responses objectively. 4. Flag any requirement that vendors commonly struggle with so I can probe it in detail. </task>

<context> You are setting up ongoing performance reviews for [VENDOR], who delivers [PROCESS] for [TEAM]. I will paste the contract SLAs below. </context> <task> 1. Design a quarterly vendor scorecard covering quality, delivery/timeliness, responsiveness, cost adherence, and partnership. 2. For each dimension give a measurable metric, a target tied to the SLA, and a 1-5 rating scale anchored with descriptions. 3. Recommend a weighting that reflects what matters most for this service. 4. Define the score thresholds that trigger a corrective-action conversation or contract review. </task>

<context> You are negotiating a renewal with [VENDOR] for [PROCESS]. I will paste the current terms, our usage, and pain points below. </context> <task> 1. Identify our top 3 negotiation objectives and rank them must-win vs nice-to-have. 2. List our sources of leverage and the vendor's likely sources of leverage. 3. Draft target, acceptable, and walk-away positions for price and key terms. 4. Anticipate the vendor's 4 most likely objections and write a response to each. </task>

<context> You are reviewing a [VENDOR] agreement covering [PROCESS] before signing. I am not a lawyer and will get legal sign-off, but I need an operational risk read. I will paste the key clauses below. </context> <task> 1. Summarize the obligations on us and on the vendor in plain language. 2. Flag clauses that create operational risk: auto-renewal, weak SLAs, liability caps, data handling, termination notice, price-escalation. 3. For each flagged clause, state the risk and a suggested redline or question for legal. 4. List anything important that is missing from the contract entirely. </task>

<context> You are escalating a recurring service failure with [VENDOR] affecting [PROCESS] and [TEAM]. I will describe the timeline of issues and the business impact below. </context> <task> 1. Write a firm but professional escalation email that states the facts, the SLA breaches, and the business impact with dates. 2. Make a specific, measurable ask and a deadline for the vendor to respond. 3. State the consequence if the issue is not resolved, without burning the relationship. 4. Provide a short internal summary for my leadership covering status, impact, and next step. </task>

<context> You are the incident commander for an active issue affecting [PROCESS] and [TEAM]. I will describe the symptoms, timeline, and what is impacted below. </context> <task> 1. Assign a severity level with a one-line justification. 2. List the immediate containment actions to limit impact before root cause is known. 3. Generate a prioritized diagnostic checklist to isolate the cause. 4. Draft a holding status update for stakeholders that states impact, what we know, and next update time. 5. Identify who needs to be paged or informed right now. </task>

<context> You are running a post-incident root-cause analysis for an issue in [PROCESS] owned by [TEAM]. I will paste the incident timeline and contributing factors below. </context> <task> 1. Apply the 5 Whys to drive from symptom to underlying cause, showing each layer. 2. Separate the root cause from contributing factors and triggers. 3. Distinguish process failures from human-error framing and reframe any blame toward the system. 4. Recommend corrective actions split into immediate fixes and systemic preventions, each with an owner. </task>

<context> You are documenting a resolved incident in [PROCESS] for [TEAM] and leadership. I will paste the timeline, root cause, and actions taken below. </context> <task> 1. Write a post-mortem with: summary, impact (who/what/how long), timeline, root cause, what went well, what went poorly, and action items. 2. Quantify the impact wherever possible (downtime, affected count, cost, SLA breach). 3. Make every action item specific, owned, and dated, and tag it prevention vs detection vs response. 4. Add a short executive summary readable in 30 seconds at the top. </task>

<context> You are defining how issues in [PROCESS] get escalated within [TEAM] and beyond. We want fewer judgment calls and faster routing. </context> <task> 1. Define 3-4 severity tiers with concrete, observable criteria for each (not vague words like 'major'). 2. For each tier specify: who is notified, response-time target, resolution-time target, and the communication cadence. 3. Define the trigger and authority to escalate one tier up. 4. Output the result as an escalation matrix table. </task>

<context> You are tackling an issue that keeps recurring in [PROCESS] for [TEAM]. I will paste the history of past occurrences and the fixes that were tried below. </context> <task> 1. Identify the pattern across occurrences: common triggers, time-of-day, conditions, or upstream causes. 2. Explain why previous fixes did not stop recurrence (treated symptom vs cause). 3. Recommend a durable prevention plan with detection, prevention, and a fallback if it happens again. 4. Define a leading metric that tells us the recurrence is actually trending down. </task>

<context> You are running a recurring operations meeting for [TEAM] focused on [PROCESS]. Meetings have been running long and unfocused. </context> <task> 1. Design a tight agenda with time-boxed segments and a clear purpose for each (decide, inform, or discuss). 2. List the pre-reads or data each segment requires so no time is spent catching up live. 3. Specify who owns each segment and the decision or output expected. 4. Add a 5-minute closing ritual that captures action items, owners, and due dates. </task>

<context> You are coordinating a hand-off in [PROCESS] between [TEAM] and another team. Things fall through the cracks at the boundary. </context> <task> 1. Map the hand-off: what is passed, in what format, through what channel, and the acceptance criteria for the receiving team. 2. Define a clear definition-of-done for the sending side and a checklist for the receiving side. 3. Identify the 3 most likely failure points at the boundary and a safeguard for each. 4. Recommend a single source of truth that both teams update so status is never ambiguous. </task>

<context> You are mediating competing priorities on [TEAM] where [PROCESS] is being crowded out by other demands. I will describe the conflicting asks and stakeholders below. </context> <task> 1. Lay out the competing demands, their stakeholders, and the cost of delay for each. 2. Recommend a prioritization with a clear rationale tied to business impact. 3. Draft the message I send to the deprioritized stakeholder that explains the decision and offers an alternative. 4. Suggest a lightweight intake rule that prevents this conflict from recurring. </task>

<context> You are delegating part of [PROCESS] to a member of [TEAM]. Past delegations have come back wrong because expectations were fuzzy. </context> <task> 1. Write a delegation brief covering: the outcome wanted, why it matters, constraints, the deadline, and the level of authority (decide vs recommend vs ask first). 2. Define what 'done well' looks like with 3 concrete success criteria. 3. List the resources and people the owner can draw on. 4. Specify the check-in points so I can course-correct without micromanaging. </task>

<context> You are reporting weekly status on [PROCESS] for [TEAM] to busy stakeholders. I will paste this week's raw updates, blockers, and metrics below. </context> <task> 1. Write a status update in the format: overall RAG status, key wins, in-progress, blockers needing help, and what is coming next. 2. Lead with the one thing stakeholders most need to know and the one decision you need from them. 3. Quantify progress against targets rather than describing activity. 4. Keep it under 200 words and end with a clear 'help needed' ask if there is one. </task>