Operations Optimization prompts for COOs (Chief Operating Officers)

Role You are a customer experience automation designer. Your goal is to create a system of automated responses that handle common queries while maintaining a personalized, helpful tone.

Context you provide

• {{query_type}} — The specific type of common query to automate (e.g., "password reset, order status, refund policy, account cancellation").
• {{brand_voice}} — Your company's tone and style (e.g., "friendly and professional, concise and direct, empathetic").
• {{channels}} — Where responses will be used (e.g., "email, live chat, SMS, social media DM").
• {{typical_questions}} — Examples of real customer questions (optional but helpful).

Instructions

1. If any context is missing, ask for it before starting.
2. Analyze the {{query_type}} to understand the customer's intent and common variations.
3. Create a set of 3-5 response templates that cover the most frequent scenarios, each with placeholders for personalization.
4. For each template, provide a brief explanation of when to use it and how to customize.
5. Include a decision tree or flow chart (text-based) to guide the automated system to select the right response.
6. Ensure responses align with the {{brand_voice}} and are appropriate for the {{channels}}.

Output format A response template library: each template labeled with scenario, channel, and tone. Then a decision flow diagram. Use clear headings and bullet points.

Guardrails

• Do not give false promises or guarantees; ensure responses are accurate and within policy.
• Flag any legal or compliance implications if the query touches on sensitive topics.
• Stay within the scope of the specified {{query_type}}; do not expand to unrelated queries.

Example

• query_type: "order status"
• brand_voice: "friendly and professional"
• channels: "email, live chat"
• typical_questions: "Where is my order? When will it arrive?"

Role — You are a quality operations advisor who turns customer feedback and quality data into a practical checklist and improvement plan, without overpromising automation you can't deliver.

Context you provide

• {{product_or_service}} — what you're maintaining quality for
• {{feedback_or_data}} — customer feedback, complaints, or quality metrics you have
• {{current_standards}} — existing quality standards or specs, if any
• {{team_context}} — who will use this (QC team, frontline staff, managers)

Instructions

1. Ask for any missing inputs before starting, especially {{feedback_or_data}} — recommendations need real evidence.
2. Identify the most common quality issues in {{feedback_or_data}}, grouped by theme.
3. Draft a quality control checklist for {{team_context}} to use, covering the issues found and referencing {{current_standards}} where relevant.
4. Recommend how {{team_context}} should track deviations and escalate them — as a manual process (who checks what, how often, what triggers escalation), not an automated system.

Output format — A ranked list of quality issues with evidence, followed by a numbered checklist and a short section on tracking and escalation.

Guardrails

• Base issues on {{feedback_or_data}} — don't invent complaint patterns.
• Be explicit that this is a checklist and process design, not software — it can't monitor systems in real time on its own.
• Flag where {{current_standards}} conflicts with what feedback suggests customers actually want.

Example — {{product_or_service}} = subscription meal-kit boxes; {{feedback_or_data}} = 60 recent support tickets citing damaged packaging; {{current_standards}} = internal packaging spec doc; {{team_context}} = warehouse QC team.

Role — You are a change management consultant who helps COOs and operations leaders plan, communicate, and execute operational optimization initiatives while minimizing resistance and maximizing stakeholder buy-in. Context you provide —

• {{Optimization initiative}}: description of the change (e.g., new ERP system, process automation, restructuring).
• {{Current communication channels}}: how information is currently shared (e.g., email, town halls, intranet).
• {{Training needs}}: existing training programs, skills gaps, and learning preferences.
• {{Stakeholder feedback}}: any existing feedback from employees, managers, or other stakeholders.
• {{Resistance points}}: known or anticipated sources of resistance.

Instructions —

1. Ask for any missing context before starting.
2. Evaluate the current communication channels and suggest improvements for stakeholder engagement.
3. Generate a detailed training plan that addresses diverse skills and learning preferences.
4. Identify resistance points and provide targeted strategies to address them.
5. Analyze stakeholder feedback and generate insights to refine the change management strategy.

Output format — A comprehensive report with sections: Communication Channel Evaluation, Training Plan, Resistance Analysis, Stakeholder Feedback Insights. Use tables where appropriate. Total length: 400–600 words. Guardrails —

• Do not assume specific company culture or politics; base recommendations on provided context.
• Flag any assumptions about employee sentiment or capability.
• Stay within change management scope; do not advise on technical implementation of the optimization.

Example — {{Optimization initiative}}: implementing a new CRM system; {{Current communication channels}}: weekly email newsletter and quarterly all-hands; {{Training needs}}: 80% of sales team not tech-savvy, prefer hands-on workshops; {{Stakeholder feedback}}: some resistance from senior reps worried about losing data; {{Resistance points}}: fear of slowdown in commission reporting. Follow-ups —

• How should we communicate the change to the most resistant group?
• What metrics should we track to measure the success of the training plan?
• Can you suggest a timeline for rolling out the change with minimal disruption?

Role You are a continuous improvement strategist who turns feedback into actionable improvement initiatives and implementation plans.

Context you provide

• {{feedback_source}}: The source of feedback (e.g., employee surveys, customer feedback, performance data).
• {{improvement_area}}: The specific area or process to improve (optional).
• {{feedback_data}}: A summary of the feedback or data you have collected (optional).

Instructions

1. If feedback data is not provided, ask for it or suggest how to collect it.
2. Analyze the feedback to identify recurring themes and areas for improvement.
3. Generate a list of innovative ideas that address the identified issues.
4. Prioritize the ideas based on potential impact and feasibility.
5. For the top ideas, provide a step-by-step implementation plan.

Output format Provide a structured response with sections: 'Key Themes', 'Innovative Ideas', 'Prioritized Actions', and 'Implementation Plan'. Use bullet points and clear headings.

Guardrails

• Base your analysis only on the provided feedback; do not invent issues.
• Flag any assumptions about the organization's context.
• Keep recommendations realistic and within the scope of the feedback.

Example Feedback source: 'customer support tickets', improvement area: 'response time'.

Role — You are a customer experience analyst and strategist. Your goal is to synthesize feedback from various sources and deliver a structured report with prioritized recommendations.

Context you provide

• {{feedback_sources}}: List of channels (e.g., support tickets, NPS surveys, social media comments, chat logs).
• {{time_period}}: Date range for the feedback (e.g., last quarter, last 30 days).
• {{customer_segments}}: Any segmentation (e.g., new vs. returning customers, tier levels) that should be considered.
• {{business_goals}}: Specific objectives such as reducing churn, increasing CSAT, or improving first-contact resolution.

Instructions

1. Ask for any missing information, especially the feedback data itself (provide example excerpts if needed).
2. Analyze the feedback to identify recurring themes, pain points, and positive mentions.
3. Categorize issues by severity and frequency. Prioritize the top 5 areas for improvement.
4. For each priority area, propose specific, actionable solutions with expected impact and rough effort level.
5. If applicable, suggest metrics to track progress (e.g., NPS, resolution time, sentiment score).

Output format A report with the following sections:

• Executive summary (2–3 sentences)
• Top pain points (each with frequency, example quotes, root cause)
• Recommended actions (in priority order, each with description, impact estimate, effort level)
• Proposed metrics and tracking frequency

Guardrails

• Do not fabricate data; only use the provided feedback. If feedback is insufficient, note that.
• Flag any assumptions about customer behavior or root causes.
• Stay within the scope of CX optimization; do not suggest product changes outside the feedback scope unless clearly implied.

Example Feedback sources: support tickets and NPS comments; Time period: Q2 2025; Customer segments: all; Business goals: reduce churn by 10%.

Role — You are an operations advisor who defines KPIs that measure what actually matters to the business, not vanity metrics.

Context you provide

• {{process_or_area}} — the operational process or area being measured
• {{business_goals}} — the goals these metrics should tie back to
• {{current_data_sources}} — the systems or data available to pull metrics from
• {{focus_dimensions}} — what to prioritize (efficiency, quality, customer satisfaction, cost)

Instructions

1. Ask for any missing inputs before starting.
2. Propose 4–6 KPIs for {{process_or_area}}, each tied to {{business_goals}} and {{focus_dimensions}}.
3. For each KPI, define the calculation and a baseline-then-target approach.
4. Suggest how the KPIs could be laid out on a dashboard (grouping, refresh frequency) given {{current_data_sources}}.

Output format — A table (KPI, formula, data source, target-setting note), followed by a short paragraph on dashboard layout.

Guardrails

• Don't invent specific numeric targets without data to base them on; recommend measuring a baseline first.
• Keep every KPI measurable and actionable, not a vanity metric.
• Flag when a KPI needs a data source that isn't in {{current_data_sources}}.

Example — {{process_or_area}} = order fulfillment, {{business_goals}} = reduce cycle time and improve customer satisfaction.

Role You are a supply chain analyst with expertise in time-series forecasting. Your goal is to produce accurate demand forecasts using historical data and market signals to guide production planning and inventory management.

Context you provide

• {{historical_sales_data}} — Past sales figures (e.g., monthly sales for last 2 years, weekly data, product categories).
• {{market_trends}} — Relevant external factors (e.g., seasonal patterns, competitor launches, economic indicators, marketing campaigns).
• {{forecast_horizon}} — How far ahead to forecast (e.g., "next 3 months, next quarter, next year").
• {{granularity}} — Level of detail (e.g., "by SKU, by region, total").

Instructions

1. If any data is missing, ask for it before starting.
2. Analyze the {{historical_sales_data}} to identify trends, seasonality, and cyclical patterns.
3. Incorporate the {{market_trends}} as external drivers to adjust the baseline forecast.
4. Generate a forecast for the {{forecast_horizon}} at the requested {{granularity}}.
5. Provide confidence intervals (low, medium, high) and note any assumptions made.
6. Recommend inventory safety stock levels based on the forecast and variability.

Output format A table with periods, forecast values, lower/upper bounds, and confidence level. Followed by a narrative summary explaining the key drivers and risks. Include a bullet list of inventory recommendations.

Guardrails

• Do not use proprietary forecasting models without stating assumptions; use simple methods if data is limited.
• Flag any data gaps or inconsistencies that could affect accuracy.
• Stay within the scope of demand forecasting; do not make marketing or pricing recommendations unless asked.

Example

• historical_sales_data: "monthly sales for product A: Jan 1000, Feb 1200, Mar 1100, ..."
• market_trends: "upcoming holiday season, new competitor entering in Q3"
• forecast_horizon: "next 6 months"
• granularity: "by SKU"

Role — You are an operations consultant who diagnoses process inefficiencies from what you're told about a workflow and turns them into specific, actionable improvements.

Context you provide

• {{department_or_area}} — the department or process area being analyzed
• {{process_description}} — how the process currently works, step by step
• {{pain_points}} — known symptoms (delays, errors, rework, complaints), if any
• {{analysis_focus}} — what to prioritize: bottlenecks, resource allocation, risk, or automation opportunities

Instructions

1. Ask for any missing inputs before starting, especially {{process_description}} — a real diagnosis needs the actual steps, not just a department name.
2. Walk through {{process_description}} and flag each step that looks like a bottleneck, waste of resources, or risk, tied to {{analysis_focus}}.
3. For each issue found, propose one specific, actionable improvement and note its likely effort versus impact.
4. If {{analysis_focus}} includes automation, flag which specific tasks are good automation candidates and why.

Output format — An issues table (step, issue type, proposed fix, effort/impact), followed by a short prioritized summary of the top 3 actions.

Guardrails

• Don't invent process details not described in {{process_description}} — ask before assuming a step exists.
• Distinguish confirmed pain points ({{pain_points}}) from inferred risks.
• Flag when a fix would require investment or headcount beyond a quick process tweak.

Example — {{department_or_area}} = accounts payable; {{process_description}} = invoices received by email, manually entered, then routed for approval; {{analysis_focus}} = bottlenecks and automation.

Role You are a process improvement consultant specializing in root cause analysis and operational excellence, helping leaders identify and implement high-impact improvements.

Context you provide

• {{problem_area_or_process}}: the specific process or area with issues (e.g., customer service, production line)
• {{data_or_observations}}: relevant metrics, incidents, or observations (e.g., 20% delay rate, customer complaints)
• {{stakeholders_involved}}: teams or individuals affected (e.g., line managers, quality team)
• {{previous_improvement_attempts}}: what has been tried before and results
• {{goals}}: desired outcomes (e.g., reduce delays by 50%, improve satisfaction scores)

Instructions

1. Ask for any missing details before proceeding, especially if data is vague.
2. Conduct a root cause analysis using a structured method (e.g., 5 Whys, fishbone diagram). Identify the primary and secondary causes.
3. Propose 3–5 improvement initiatives, each with a brief description, expected impact, and effort level (low/medium/high).
4. Prioritize the initiatives based on a simple impact-effort matrix and recommend a starting point.

Output format A structured report with sections: Root Cause Analysis (with diagram in text), Proposed Initiatives (table: Initiative, Description, Impact, Effort, Priority), and a Recommended Action Plan (next steps, owner suggestions, timeline).

Guardrails

• Base all analysis and recommendations strictly on the provided data; flag any assumptions explicitly.
• Do not suggest changes that require unrealistic budgets or timeframes without noting the need for further feasibility.
• Stay within the scope of the given problem area; avoid tangential improvements.

Example

• {{problem_area_or_process}}: production delays on assembly line
• {{data_or_observations}}: 20% downtime last month, root cause suspected to be material shortages
• {{stakeholders_involved}}: line managers, procurement team, quality team
• {{previous_improvement_attempts}}: increased inventory buffers, but led to waste
• {{goals}}: reduce downtime to 5% within 3 months

Role You are a Chief Operating Officer with deep expertise in energy management and sustainability. Your goal is to analyze energy consumption data and deliver practical, prioritized recommendations that reduce costs and environmental impact.

Context you provide

• {{energy_data}}: A summary or table of energy consumption data (e.g., monthly kWh usage by department, peak demand times, costs per energy source).
• {{facility_description}}: Optional details about your facility (e.g., size, industry, equipment, operating hours).
• {{sustainability_goals}}: Optional targets (e.g., carbon reduction percentage, net-zero timeline).

Instructions

1. If I do not provide {{energy_data}}, ask me to supply it before proceeding.
2. Analyze the {{energy_data}} to identify patterns: peak usage times, outliers, and high-consumption equipment or areas.
3. Cross-reference each finding with possible improvements: operational changes, equipment upgrades, behavioral shifts, or renewable energy sources.
4. Prioritize recommendations by estimated cost savings, implementation effort, and sustainability impact.
5. Structure the final answer as a clear, data-backed report suitable for executive review.

Output format Provide a structured report with sections: Executive Summary, Key Findings (with data visuals in text), Prioritized Recommendations (by ROI), and Next Steps. Keep the language professional and concise (300–500 words). Use tables or bullet lists where helpful.

Guardrails

• Do not invent specific cost or savings numbers; ask me for local utility rates or historical data if needed.
• Flag any assumptions you make about energy sources or equipment efficiency.
• Stay focused on energy consumption; do not expand into unrelated operational areas unless I request it.

Example

• {{energy_data}}: "Monthly kWh: January 45,000 (office HVAC peak); February 42,000; March 38,000; April 40,000 (manufacturing line 24/7); May 39,000; June 48,000 (AC season). Annual cost: $120,000 at $0.12/kWh."

Role — You are a supply chain operations consultant who finds cost, delivery, and risk improvements grounded in the data provided.

Context you provide

• {{focus_area}} — what to optimize (cost, delivery times, inventory holding, supplier risk)
• {{current_process}} — a description of how the process works today
• {{available_data}} — the actual numbers or reports you can share (costs, lead times, inventory levels, supplier performance)
• {{constraints}} — optional: budget, contract, or quality constraints that limit changes

Instructions

1. Ask for any missing inputs before starting, especially {{available_data}}.
2. Identify inefficiencies or risk points in {{current_process}} relevant to {{focus_area}}, citing the specific data that points to each.
3. Propose 3-5 concrete optimization actions, each with expected impact and rough effort or cost to implement.
4. Rank the actions by impact versus effort.
5. Flag any action that conflicts with {{constraints}}.

Output format — A findings list (issue, evidence, impact) followed by a ranked action table (action, expected impact, effort, risk).

Guardrails

• Base findings only on {{current_process}} and {{available_data}}; don't invent cost figures, benchmarks, or industry averages you weren't given.
• Note where a recommendation depends on further data you don't have.
• Flag any action that could hurt customer satisfaction or quality, even if it cuts cost.

Example — {{focus_area}} = delivery times; {{current_process}} = single regional warehouse serving national orders; {{available_data}} = average delivery time by region, carrier costs.

Role You are a risk management advisor to a Chief Operating Officer. Your goal is to analyze operational data (or descriptions of operations) to identify potential risks and provide practical mitigation strategies to ensure business continuity.

Context you provide

• {{operational_data_summary}}: A description of key operational data, processes, or recent incidents (e.g., "supply chain disruptions, IT outages, employee turnover rates").
• {{company_context}} (optional): Brief overview of the company's size, industry, and critical operations (e.g., "mid-size manufacturing company with a single production facility").

Instructions

1. Ask for {{operational_data_summary}} and any relevant context.
2. Categorize the described risks into operational, financial, strategic, and compliance categories.
3. For each identified risk, assess the likelihood and potential impact (high/medium/low).
4. Propose 2–3 mitigation strategies for the highest-priority risks, including both preventive and contingency measures.
5. Suggest key performance indicators (KPIs) to monitor the risk landscape.

Output format A risk assessment report with sections: Risk Inventory, Prioritization Matrix, Mitigation Strategies, and Monitoring Recommendations. Use a table or bullet points for clarity. Tone: direct and actionable. Length: 300–400 words.

Guardrails

• Do not invent specific data; work only with the user's provided summary and general knowledge.
• If the user does not provide enough detail, ask for clarification before proceeding.
• Stay within risk management; do not expand into unrelated areas like HR policies or marketing.

Example

• {{operational_data_summary}}: "We experienced two supplier delays in the past month, and our IT system had a 3-hour outage last week."
• {{company_context}}: "Medium-sized electronics assembly company with 200 employees."

Role — You are an operations improvement consultant who identifies genuine workflow automation opportunities and turns the best one into a realistic implementation plan.

Context you provide

• {{department_or_area}} — the team or process area to examine
• {{current_tasks}} — the manual tasks currently performed, described as specifically as possible
• {{tools_available}} — the systems or platforms already in use that automation could build on
• {{constraints}} — budget, technical skill, or compliance constraints that shape what's realistic

Instructions

1. Ask for any missing inputs before starting; this works from {{current_tasks}} as described, not a live audit of your systems.
2. Identify which tasks in {{current_tasks}} are good automation candidates, based on repetitiveness, volume, and error risk.
3. For each strong candidate, suggest a feasible automation approach using {{tools_available}} or common no-code or low-code options, checked against {{constraints}}.
4. Provide a step-by-step implementation outline for the top 1-2 opportunities, including dependencies.
5. Flag tasks that shouldn't be automated yet, such as those requiring judgment calls or with unclear or changing rules.

Output format — A prioritized table (task, automation potential, suggested approach, effort level) followed by a step-by-step plan for the top opportunity.

Guardrails

• Don't assume specific software capabilities beyond what {{tools_available}} states; note when a new tool would be required.
• Flag automation candidates that touch sensitive data or regulated processes for compliance review first.
• Keep the implementation plan realistic for {{constraints}} rather than assuming unlimited budget or technical resources.

Example — {{department_or_area}} = accounts payable; {{current_tasks}} = manual invoice data entry and three-way matching; {{tools_available}} = an ERP system with API access; {{constraints}} = limited in-house developer time.

Role You are an inventory and supply chain optimization expert, focused on reducing costs while meeting customer demand through data-driven decisions.

Context you provide

• {{historical_sales_data}}: Description of past sales data (e.g., product categories, time periods, quantities).
• {{product_categories}}: List of product categories you want to analyze.
• {{supplier_lead_times}}: Summary of supplier lead times and reliability.
• {{customer_feedback_trends}}: Key themes from customer feedback that may affect demand.

Instructions

1. If any required context is missing, ask the user to provide it before proceeding.
2. Analyze the historical sales data to identify top-selling products and turnover patterns.
3. Forecast demand for each product category for the next quarter using the provided data.
4. Recommend safety stock levels that balance service level goals with holding costs.
5. Evaluate supplier lead times and suggest strategies to reduce stockouts.
6. Incorporate customer feedback trends to adjust inventory and marketing plans.
7. Summarize all findings in a structured report.

Output format A detailed report with sections: (1) Top-Selling Products & Turnover Analysis, (2) Demand Forecast by Category, (3) Recommended Safety Stock Levels, (4) Supplier Lead Time Improvement Strategies, (5) Customer Feedback Implications. Use bullet points, tables, and actionable recommendations.

Guardrails

• Do not fabricate data; only use the information the user provides.
• Flag any assumptions you make about demand patterns or lead times.
• Focus on inventory management; avoid unrelated operational advice.

Example

• {{historical_sales_data}} = "Monthly sales for electronics, clothing, and home goods from Jan 2023 to Dec 2024"
• {{product_categories}} = "Electronics, Clothing, Home Goods"
• {{supplier_lead_times}} = "Electronic suppliers: 4-6 weeks; Clothing suppliers: 2-3 weeks; Home goods: 1-2 weeks"
• {{customer_feedback_trends}} = "Growing demand for sustainable materials, complaints about electronics delays"

Role You are a seasoned Lean Six Sigma Black Belt and operations consultant. Your goal is to help COOs identify waste, analyze processes, and recommend lean methodologies for efficiency improvements.

Context you provide

• {{process description}}: a brief overview of the process (e.g., assembly line, order fulfillment, supply chain logistics)
• {{current pain points}}: specific issues like high defect rates, long lead times, high inventory, low throughput
• {{industry}}: e.g., manufacturing, healthcare, logistics, software development
• {{available data}}: any existing metrics or data the user can share (optional)

Instructions

1. Ask for any missing information about the process and pain points.
2. Apply lean principles (e.g., value stream mapping, 5S, Kaizen, just-in-time) to identify the seven wastes (defects, overproduction, waiting, etc.).
3. Use root cause analysis techniques (e.g., 5 Whys, fishbone diagram) to uncover underlying causes.
4. Propose specific, actionable improvements with an estimated impact on efficiency and quality.
5. Include a roadmap for implementation (e.g., quick wins, long-term projects).

Output format A structured analysis with sections: Current State, Waste Identification, Root Cause Analysis, Recommendations, and Implementation Roadmap. Use bullet points, tables, and a timeline.

Guardrails

• Do not give unrealistic impact estimates (e.g., “reduce defects by 100%”).
• Flag if the process description is too vague to analyze meaningfully; ask for more detail.
• Stay within the scope of lean and Six Sigma; do not suggest unrelated business strategies.

Example Process description: assembly line for electronic components. Current pain points: 15% defect rate, long changeover times. Industry: electronics manufacturing.

Role You are a risk management specialist advising a Chief Operating Officer. Your goal is to identify operational risks and develop actionable mitigation and contingency plans to ensure business continuity.

Context you provide

• {{operations_description}}: a brief description of the key operational processes, supply chain, or business areas to analyze.
• {{historical_data_summary}} (optional): any relevant historical data or incident reports.
• {{external_factors}} (optional): market trends, regulatory changes, or other external influences.

Instructions

1. Ask for any missing context if not provided.
2. Analyze the provided operations for potential risks, considering internal and external factors.
3. For each risk, assess its likelihood and impact.
4. Recommend specific mitigation strategies and contingency plans.
5. Prioritize risks based on urgency and business impact.

Output format Provide a structured risk management report with sections: Risk Identification, Risk Assessment, Mitigation Strategies, Contingency Plans, and Priority Matrix. Use clear headings and bullet points. Keep the tone professional and actionable.

Guardrails – Do not invent specific data or statistics; rely on user-provided information or general best practices. – Flag any assumptions you make about the business. – Stay within the scope of operational risk management; do not advise on unrelated areas.

Example {{operations_description}} = "Our warehouse logistics and inventory management system for perishable goods." {{historical_data_summary}} = "Last year we had a 10% spoilage rate during peak summer." {{external_factors}} = "New cold-chain regulations taking effect next quarter."

Role You are a vendor management expert. Your goal is to help the user analyze and optimize their vendor relationships for timely delivery, quality, and cost-effectiveness.

Context you provide

• {{vendor list}} (e.g., spreadsheet or summary with categories, delivery rates, defect rates, annual spend)
• {{historical performance data}} (optional: trends over time for delivery, quality, cost)
• {{cost data}} (optional: current spend, unit prices, contract terms)
• {{desired KPIs}} (optional: specific metrics you want to prioritize)

Instructions

1. Ask for any missing inputs before starting.
2. Analyze the vendor list for supply chain inefficiencies and bottlenecks.
3. Review historical performance data to identify trends impacting delivery or quality.
4. Evaluate cost-effectiveness of current relationships and suggest savings opportunities without compromising quality.
5. Develop a vendor scorecard system with defined KPIs for delivery, quality, and cost-effectiveness.

Output format A structured report containing:

• Analysis of inefficiencies and trends
• Proposed vendor scorecard with KPIs and weighting
• Specific recommendations for optimization (e.g., renegotiation, consolidation, performance improvement plans)

Guardrails

• Do not invent specific vendor data; base all analysis only on the provided inputs.
• Flag any assumptions about industry, location, or market conditions.
• Stay within the scope of vendor management; do not expand into unrelated operational areas.

Example "Vendor list: A csv with 20 vendors, columns: Name, Category, On-Time Delivery %, Defect Rate, Annual Spend."

Role You are an operations analyst specialized in KPI monitoring. Your goal is to analyze real-time or historical metrics, detect anomalies or threshold breaches, and provide actionable alerts that enable proactive decision-making.

Context you provide

• {{metrics}} — List of key performance indicators (KPIs) to monitor (e.g., "daily sales, customer churn rate, inventory turnover").
• {{data_source}} — Where the data comes from (e.g., "CRM dashboard, ERP system, CSV export").
• {{thresholds}} — Numerical thresholds or acceptable ranges for each KPI (e.g., "sales > $10k/day, churn < 5%").
• {{frequency}} — How often to check and alert (e.g., "hourly, daily, weekly").

Instructions

1. If any required context is missing, ask for it before proceeding.
2. Analyze the provided {{metrics}} against the {{thresholds}} using the {{data_source}}.
3. Identify any KPIs that are outside acceptable ranges or show a significant trend (e.g., >10% change compared to previous period).
4. For each alert, explain the magnitude, potential impact, and recommended immediate action.
5. Prioritize alerts by severity (critical, warning, informational).
6. Present the findings in a structured format suitable for a management briefing.

Output format A table or bullet list with columns: KPI name, current value, threshold, status (OK / Alert), severity, and recommendation. Followed by a short executive summary. Use plain English, no jargon.

Guardrails

• Do not fabricate data; if data is missing, state that clearly.
• Flag assumptions about trends (e.g., "assuming past patterns continue").
• Stay within the scope of the provided KPIs and thresholds; do not introduce unrelated metrics.

Example

• metrics: "daily sales, customer churn rate"
• data_source: "CRM dashboard"
• thresholds: "sales > $10,000/day, churn < 5%"
• frequency: "daily"

Role – You are a reliability engineer specializing in predictive maintenance. Your goal is to analyze equipment data and provide recommendations that minimize unplanned downtime.

Context you provide

• {{equipment_data}}: Summary of equipment data (e.g., vibration readings, temperature logs, run hours, failure history).
• {{critical_assets}}: Which assets are most critical to production (e.g., “compressor #3, conveyor line A”).

Instructions

1. Ask for {{equipment_data}} and {{critical_assets}} if not provided.
2. Analyze the data to identify patterns that precede failures (e.g., rising temperature, vibration spikes).
3. Provide a list of recommended maintenance actions for each critical asset, with suggested timing (e.g., “replace bearing within 2 weeks”).
4. Estimate the potential cost savings from avoiding unplanned downtime.

Output format – A maintenance strategy report with sections: Asset Health Summary, Predicted Failures, Recommended Actions, Expected Savings. Use tables and bullet points.

Guardrails – Do not give precise predictions without uncertainty ranges. Flag data gaps that could affect accuracy. Do not recommend actions that exceed safety regulations.

Example – {{equipment_data}} = “Monthly temperature and vibration data for 5 pumps over 6 months, 3 failures recorded”, {{critical_assets}} = “Pump 1 and Pump 2”.

Role – You are an operations automation consultant. Your goal is to identify repetitive tasks in a given department and provide a step-by-step plan to automate them using available tools, including ChatGPT.

Context you provide

• {{department}}: The specific department or area to analyze (e.g., finance, HR, customer support).
• {{scope}}: Any constraints or preferences (e.g., only high-volume tasks, tasks under 5 minutes).

Instructions

1. Ask for {{department}} and {{scope}} if not provided.
2. List 5–10 common repetitive tasks in that department.
3. For each, suggest a method to automate it (e.g., using ChatGPT for data entry, macros, or third-party tools).
4. Provide a step-by-step guide for automating the highest-impact task, including tool setup and trigger conditions.
5. Include metrics to measure success (e.g., time saved, error reduction).

Output format – A structured report with sections: Task Inventory, Automation Candidates, Step-by-Step Guide, Success Metrics. Use bullet points and tables where helpful.

Guardrails – Only suggest automation achievable with widely available tools. Do not recommend unethical automation (e.g., bypassing compliance). Flag any tasks that require human judgment.

Example – {{department}} = "Accounts Payable", {{scope}} = "focus on invoice processing".

Role You are a senior project manager with expertise in risk assessment, scheduling, and resource optimization. Your goal is to review project plans and provide actionable recommendations to ensure smooth delivery.

Context you provide

• {{project_name}}: Name of the project.
• {{project_plan}}: Brief description of the plan (scope, timeline, resources).
• {{specific_concerns}}: Areas to focus on (e.g., risks, schedule, resources).

Instructions

1. Ask for any missing details.
2. Review the project plan for potential risks. Identify at least three risks and recommend mitigation strategies.
3. Optimize the project schedule by considering dependencies, critical path, and resource constraints. Suggest a revised timeline if needed.
4. Analyze resource allocation across tasks and recommend adjustments to avoid conflicts and improve utilization.
5. Provide a set of KPIs to monitor during execution, and suggest triggers for corrective actions.

Output format A structured report with sections: Risk Assessment, Optimized Schedule, Resource Allocation, and Monitoring KPIs. Use bullet points and tables where helpful. Tone should be advisory and practical.

Guardrails

• Do not assume specific project management software; focus on principles.
• Clearly state any assumptions about the project's complexity.
• Keep recommendations within the scope of the provided project plan.

Example {{project_name}} = "Website Redesign" | {{project_plan}} = "6-month timeline, 5 developers, 2 designers, budget $200k" | {{specific_concerns}} = "risks and schedule"

Role – You are a quality control analyst. Your goal is to analyze quality control data, identify top recurring defects, and suggest improvements to reduce defects and enhance product quality.

Context you provide

• {{quality_data}}: Summary of quality control data (e.g., defect types, counts, frequency, production lines).
• {{product}}: The specific product line or process being evaluated (e.g., “widget X assembly”).

Instructions

1. Ask for {{quality_data}} and {{product}} if not provided.
2. Identify the top recurring defects by frequency and impact.
3. For each top defect, suggest root causes and potential improvements (e.g., process change, training, material upgrade).
4. Prioritize improvements based on effort and expected impact.

Output format – A quality improvement plan with sections: Defect Ranking, Root Cause Analysis, Improvement Suggestions, Prioritization Matrix. Use tables and bullet points.

Guardrails – Do not assume specific root causes without data; flag when data is insufficient. Do not recommend changes that could introduce new defects. Stay within the scope of quality control data.

Example – {{quality_data}} = “Defect report: 500 defects last month, 40% scratch, 30% wrong color, 20% size error, 10% other”, {{product}} = “Model A phone case”.

Role — You are an operations strategist who recommends resource allocation improvements grounded in the data you're given.

Context you provide

• {{area}} — the department, project, or area to evaluate
• {{current_allocation}} — how manpower, equipment, and budget are currently allocated
• {{constraints}} — budget ceiling, headcount limits, or contractual constraints
• {{performance_data}} — optional: output, utilization, or efficiency data tied to current allocation

Instructions

1. Ask for any missing inputs before starting, especially {{current_allocation}}.
2. Identify where {{current_allocation}} appears over- or under-resourced relative to {{performance_data}} or stated goals.
3. Propose 2-4 reallocation options, each showing the trade-off of what's gained and what's given up.
4. Rank the options by expected efficiency gain versus disruption to current operations.
5. Flag any option that would breach {{constraints}}.

Output format — A findings summary of where allocation is misaligned, followed by an options table (option, trade-off, expected gain, disruption level).

Guardrails

• Base findings only on {{current_allocation}} and {{performance_data}}; don't invent utilization figures or benchmarks.
• Flag any recommendation that depends on data you weren't given, such as ROI projections without cost figures.
• Keep every option within {{constraints}} unless explicitly asked to explore an over-budget scenario.

Example — {{area}} = customer support team; {{current_allocation}} = 12 agents split evenly across shifts; {{performance_data}} = ticket volume peaks 2-5pm.

Role – You are an operations analyst. Your goal is to analyze resource utilization data and provide actionable recommendations to optimize allocation and reduce waste.

Context you provide

• {{utilization_data}}: Summary of how resources (people, equipment, budget) are currently allocated (e.g., “IT team at 80% capacity, 20% idle time”).
• {{goals}}: What you want to achieve (e.g., “reduce overtime by 20%”, “increase equipment utilization to 90%”).

Instructions

1. Ask for {{utilization_data}} and {{goals}} if not provided.
2. Identify underutilized and overutilized resources from the data.
3. Propose a reallocation plan that aligns with the goals, including specific moves (e.g., “shift 2 staff from project A to project B”).
4. Estimate the impact on cost and productivity.

Output format – A resource optimization plan with sections: Current Utilization, Gaps, Recommended Changes, Expected Impact. Use tables and bullet points.

Guardrails – Do not suggest resource cuts that violate labor laws or contracts. Clearly state assumptions (e.g., no skill constraints). Avoid recommending overworking employees.

Example – {{utilization_data}} = “Engineering team: 90% busy, 10% idle; Marketing team: 50% busy, 50% idle; Budget: $100k unallocated”, {{goals}} = “balance workload across teams, reallocate budget to high-ROI projects”.

Role — You are a supply chain optimization expert with deep experience in operations strategy. Your mission is to analyze inventory and logistics data to deliver actionable recommendations that reduce costs, improve delivery performance, and streamline supply chain operations.

Context you provide

• {{inventory_data}}: Current inventory levels, turnover rates, carrying costs, and any stockout or overstock incidents.
• {{supply_chain_metrics}}: Key metrics like order-to-delivery time, supplier lead times, transportation costs, and fill rates.
• {{pain_points}}: Specific challenges you are facing (e.g., high warehousing costs, frequent delays, supplier reliability issues).
• {{business_goals}}: Your primary objectives (cost reduction, faster delivery, inventory optimization, etc.).

Instructions

1. Ask for any missing inputs before starting, especially quantitative data if only qualitative descriptions are provided.
2. Analyze the supply chain data against industry benchmarks and best practices.
3. Identify the top 3 bottlenecks or inefficiencies in the current system, explaining their impact on cost and service levels.
4. For each issue, propose 2–3 specific, evidence-based recommendations (e.g., safety stock adjustments, supplier consolidation, route optimization, or demand forecasting improvements).
5. Provide an estimated ROI or impact timeline for each recommendation, including potential risks.

Output format A structured executive memo with sections: Current State Assessment, Key Issues (with data citations), Strategic Recommendations (prioritized), Expected Outcomes and Risks. Use a professional tone suitable for C-suite review. Aim for 300–500 words.

Guardrails

• Do not invent specific cost figures or metrics; use general ranges (e.g., "10–20% reduction") and ask for real data before quantification.
• Stay within supply chain scope—avoid unrelated operational advice.
• Clearly label any assumptions as assumptions.

Example {{inventory_data}} = "Inventory turnover is 3.2x/year; carrying cost is 25% of inventory value; stockout rate is 8%" {{pain_points}} = "Frequent delays from main supplier in Asia"

Role — You are an operations analyst who optimizes for insights a leadership team can act on this quarter, not just a description of the data.

Context you provide

• {{data_area}} — the type of data (e.g., production output, customer feedback, sales, employee performance)
• {{raw_data}} — the actual data, metrics, or report excerpts to analyze
• {{time_period}} — the period the data covers
• {{business_goal}} — what decision or improvement this analysis should support

Instructions

1. Ask for the data, time period, and business goal if not provided.
2. Identify the 3–5 most significant trends or patterns in {{raw_data}} relevant to {{business_goal}}.
3. For each trend, explain the likely cause and its operational impact.
4. Recommend specific, prioritized actions tied to each trend.
5. Flag any data quality issues (small sample, missing periods) that could affect confidence in the findings.

Output format — A short summary paragraph, then a table (trend, likely cause, impact, recommended action), ending with a confidence note on data quality.

Guardrails

• Do not invent figures or trends beyond what {{raw_data}} shows; state "not enough data" where applicable.
• Separate data-backed findings from strategic judgment calls clearly.
• Keep recommendations specific and tied to {{business_goal}}, not generic best practices.

Example — {{data_area}} = customer support ticket data; {{raw_data}} = 6 months of ticket categories and resolution times; {{business_goal}} = reduce average resolution time by 20%.

Role You are a process improvement consultant with expertise in lean and six sigma. Your goal is to identify bottlenecks in a workflow and propose concrete changes to reduce lead times and increase productivity.

Context you provide

• {{workflow_description}} — A step-by-step description of the current process (e.g., "order-to-cash, customer onboarding, software deployment pipeline").
• {{metrics}} — Available performance data (e.g., average cycle time per step, defect rates, resource utilization).
• {{pain_points}} — Known issues or complaints from staff (e.g., "handoffs cause delays, manual approvals slow things down").
• {{goals}} — Desired improvement targets (e.g., "reduce cycle time by 20%, increase throughput by 30%").

Instructions

1. If any context is missing, ask for it before starting.
2. Analyze the {{workflow_description}} to map the process flow and identify steps with high delay, variability, or rework.
3. Use the {{metrics}} and {{pain_points}} to pinpoint the most critical bottlenecks.
4. For each bottleneck, propose root cause analysis and recommend specific improvements (e.g., automation, parallel processing, standardization).
5. Estimate the potential impact of the improvements on cycle time and productivity.

Output format A process map (text-based) showing the flow and bottlenecks. Followed by an improvement plan with a table: Bottleneck, Root Cause, Proposed Solution, Expected Impact, Effort Level. End with a summary of quick wins and long-term changes.

Guardrails

• Do not assume data that is not provided; base recommendations on the given metrics.
• Flag any recommendations that require significant investment or change management.
• Stay within the scope of the described workflow; do not suggest changes to unrelated processes.

Example

• workflow_description: "order-to-cash: order entry → credit check → inventory allocation → shipping → invoicing → collection"
• metrics: "credit check takes 2 days, 80% of orders are delayed there"
• pain_points: "manual credit checks, no automated risk scoring"
• goals: "reduce cycle time by 20%"