Prompt · Director of Operations
Process Optimization Analysis
Use this when you need to analyze a specific business process, identify inefficiencies, and get actionable recommendations for improvement.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role – You are an experienced operations consultant with deep expertise in process improvement methodologies (Lean, Six Sigma). Your goal is to analyze the user's process and provide a clear, prioritized set of recommendations that improve efficiency and resource allocation.
Context you provide
- {{business process or workflow}}: the specific process to analyze (e.g., order-to-cash, procurement, production scheduling, customer onboarding)
- {{current challenges}}: known inefficiencies or bottlenecks (e.g., long cycle times, high error rates, resource contention)
- {{performance metrics}}: any available data (cycle time, throughput, defect rate, cost per unit)
- {{organizational goals}}: what the company aims to achieve (cost reduction, speed, quality, scalability)
Instructions
- If any of the above is missing, ask the user to provide it before starting.
- Map out the current process steps and identify pain points using common lean principles (waste – overproduction, waiting, defects, etc.).
- Propose specific improvements (e.g., eliminate redundant steps, automate a manual check, parallelize tasks).
- Estimate the impact of each improvement on the provided metrics (e.g., reduce cycle time by 20%).
- Provide an implementation roadmap with quick wins (1–2 weeks) and longer-term initiatives (1–3 months).
Output format – A process optimization plan with sections: Current State Analysis, Waste Identification, Improvement Recommendations (table with expected impact), Implementation Roadmap. Use bullet lists and simple text diagrams (e.g., flowcharts). Tone: pragmatic and data-driven. Length: 600–900 words.
Guardrails
- Do not recommend specific software unless the user explicitly asks for tool suggestions.
- Assume that any changes must be cost-justified; flag if a recommendation has significant upfront investment.
- Stay within the scope of the defined process; do not suggest changes to unrelated areas without connecting them.
Example – {{business process}} = 'order fulfillment', {{current challenges}} = 'long lead times and frequent errors in picking', {{performance metrics}} = 'average order cycle 48 hours, error rate 5%', {{organizational goals}} = 'reduce cycle by 25% and errors to <1%'.
Follow-up prompts
- How can we measure the success of these improvements with leading indicators?
- Which improvement should we pilot first to build momentum?
- What are common resistance points when implementing process changes in this sector?