Operational Efficiency & Process Optimization System
Optimize operational efficiency by mapping processes, identifying waste, and implementing improvements. Includes change management and continuous improvement protocols.
Use This When
SOPs, task systems, delegation, automation mapping.
Inputs Needed
Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules.
Expected Output
Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence.
The Workflow Prompt
You are a operations consultant and productivity systems designer. Objective: Operational Efficiency & Process Optimization System Context: Optimize operational efficiency by mapping processes, identifying waste, and implementing improvements. Includes change management and continuous improvement protocols. Original task: **You are an operations excellence specialist focused on process optimization and waste elimination. I want to improve operational efficiency in [AREA: sales, fulfillment, support, etc.]. Current state: [CURRENT METRICS], bottlenecks are [BOTTLENECKS], and constraints are [CONSTRAINTS].Create a comprehensive operational improvement system including:(1) A detailed process map showing the current state with steps, actors, timelines, and handoffs(2) A waste assessment using lean principles identifying delays, redundancies, and non-value-add steps(3) A root cause analysis for each major inefficiency using 5 whys(4) Optimization solutions ranked by impact and implementation ease(5) A detailed implementation plan including team training and change management(6) New process documentation and standard operating procedures(7) Metrics and dashboards tracking efficiency improvements(8) Ongoing continuous improvement protocols. Include Gantt chart for implementation and specific metrics showing before/after impact.** Inputs I may provide: Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules. Operating instructions: - First, restate the objective in one clear sentence. - If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them. - Use a Detailed response style. - Be specific to the business, audience, channel, and constraints provided. - Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use. - When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources. - Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead. - End with a short QA checklist that helps me verify the output. Required output: Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence. Caution: Use live web research or source documents before finalizing claims.
QA Follow-Up Checklist
After the AI returns its output, verify against:
- Output is specific to the provided business/context.
- Assumptions are clearly labeled.
- No unsupported claims without source checks.
- Next actions are clear and usable.
Follow-Up Prompt
Now turn the result for 'Operational Efficiency & Process Optimization System' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.
Avoid / Cautions
Use live web research or source documents before finalizing claims.
How Different Verticals Use This Workflow
Restaurant & Hospitality
A 6-location quick-service chain maps their kitchen prep process with timing data per step. Output identifies the 18-second avg wait at the assembly station as the bottleneck (driving 14% lost customers at peak). Optimization: pre-stage 4 high-velocity SKUs every 30 min. Throughput rises 22%, food cost stays flat, peak-hour revenue lifts 18%.
Retail & E-commerce
A DTC brand maps their order-to-ship process. Output identifies the 4-hour gap between QC and shipping due to manual handoff. Optimization: integrate ShipStation with their WMS to auto-batch. Time-to-ship drops from 18 hrs to 6 hrs, NPS lifts 8 points, ad ROAS lifts 12% due to faster delivery messaging.
Professional Services & B2B
A 24-person consulting firm maps their proposal-generation process with cycle time per step. Output identifies the 4-day pricing approval as the bottleneck. Optimization: 3-tier pricing authority (under $50K = partner auto-approve). Median proposal time drops from 11 to 4 days, close rate lifts 9% due to faster turnaround.
Beauty & Personal Care
A medspa maps their new-client intake process. Output identifies the 14-day delay between consult and treatment booking due to manual insurance verification. Optimization: real-time verification at consult via integrated tool. Conversion from consult to treatment lifts from 48% to 71%, monthly revenue lifts $42K.
Local & Trade Services
A residential plumbing company maps their dispatch-to-completion process. Output identifies the 90-min average drive-time waste between jobs due to non-geographic dispatching. Optimization: geographic clustering plus a 3-day rolling schedule. Drive time drops 38%, jobs per truck per day rise from 4.2 to 5.6, revenue per truck lifts 27%.
Frequently Asked
What inputs actually move the needle for real process optimization vs a flowchart that sits in Notion?
Three things: a process map of the current state with handoffs and timing data (not 'we have a sales process'), the bottleneck identified with cycle time data, and the constraint you're optimizing against (cycle time vs cost vs quality — they trade off). Process optimization fails when input is qualitative ('it feels slow'). It works when input is quantitative ('proposals take 11 days median, 28 days p90, target is 5 days'). Numbers tell you what to fix; feelings tell you what's annoying.
What's the most common failure mode for process improvement?
Optimizing the wrong step. The team complains about the proposal handoff being slow, you optimize that, then realize the real bottleneck was 6 steps upstream where qualifying leads got stuck. The fix is mapping the full process with cycle times per step before touching anything. Find the actual constraint (the longest queue, the highest variance step) and optimize there. Theory of Constraints: anywhere else is local improvement that doesn't move the system.
When is this the wrong tool to reach for?
Skip process optimization if you have under 10 people — your processes are tribal knowledge and formalizing them too early creates rigidity. Skip if the process is being redesigned (don't optimize what you're about to throw out). Skip if you don't have at least one quantitative metric on cycle time or output quality. Process work needs data. Without data, you're documenting opinions and calling them processes.
How is this different from hiring a McKinsey associate or running Six Sigma?
McKinsey and Six Sigma bring methodology and rigor; AI brings speed. For a 20-person company, McKinsey is overkill ($300K+ engagement). Six Sigma certification is the right framework but takes 18-24 months to deploy. The AI-powered version gives you a 70% solution in a week: process map, bottleneck identification, optimization recommendations, implementation plan. Use it to move fast, then bring in specialized help for the truly complex problems (multi-site manufacturing, regulated process redesign).