AI Prompts for Process Improvement: Lean, Six Sigma, Optimization

Published: July 2026 | 9 min read

Process improvement is about finding the waste, eliminating it, and making the new way stick. Whether you are running DMAIC cycles, value stream mapping, or just trying to make a clunky process less painful, AI can help you analyze, design, and communicate improvements — if your prompts think like a Lean Six Sigma practitioner, not a generic chatbot.

Current State Analysis

1. Process Mapping Prompt

Role: Process improvement analyst (Lean Six Sigma Green Belt)
Task: Create a detailed process map for [process name].
Input: [Describe the process — who does what, in what order, using what tools, with what handoffs]
Output:
1. SIPOC diagram (Supplier, Input, Process, Output, Customer)
2. Swimlane process map (by role/department)
3. Decision points and branches
4. Handoff points (where work passes between people/departments)
5. Time stamps (cycle time per step, wait time between steps)
6. Value-add classification (VA/NVA/NNVA — Necessary Non-Value-Add)
7. Pain points (where errors, rework, or delays occur)
Format: Process map description with accompanying analysis table.
Include: Process cycle efficiency calculation (VA time / total lead time).

2. Waste Identification (8 Wastes Analysis)

Role: Lean process consultant
Task: Identify the 8 wastes (DOWNTIME: Defects, Overproduction, Waiting, Non-utilized talent, Transportation, Inventory, Motion, Extra-processing) in [process description].
For each waste category:
1. Is it present? (Yes/No)
2. Where? (specific step or area)
3. How bad? (Low/Medium/High impact)
4. Evidence (what data or observation shows this)
5. Quick fix (can eliminate in <30 days)
6. Structural fix (requires process redesign)
Output:
1. Waste assessment matrix (8 wastes x process steps)
2. Top 3 waste reduction opportunities (ranked by impact x ease)
3. Estimated improvement (time/cost savings if addressed)
4. 30-day action plan for quick wins
Format: Waste analysis report ready for the improvement team.

3. Voice of the Customer (VoC) Analysis

Role: Process improvement analyst specializing in VoC
Task: Analyze Voice of the Customer data for [process/product].
Data sources: [Survey results, complaint logs, interview notes, NPS comments, support tickets]
For each theme:
1. Customer need/expectation (what they want)
2. Current experience (what they get)
3. Gap (difference between expectation and reality)
4. Impact on satisfaction (1-5 scale)
5. CTQ (Critical to Quality) characteristic (measurable requirement)
6. Specification limits (target, lower limit, upper limit)
Output:
1. Customer need categories (5-7 themes)
2. CTQ tree (need -> driver -> measurable requirement -> specification)
3. Priority ranking (which CTQs have the biggest satisfaction impact?)
4. Current performance vs target for each CTQ
Format: VoC analysis with CTQ tree, ready for DMAIC measure phase.

Root Cause & Analysis

4. Fishbone Diagram Generator

Role: Root cause analysis facilitator
Task: Create an Ishikawa (fishbone) diagram for [problem statement].
Problem: [Define precisely — e.g., Invoice processing takes 12 days, target is 5 days]
6M categories: Man (people), Machine (technology), Method (process), Material (data/inputs), Measurement (metrics), Mother Nature (environment)
For each category, brainstorm 3-5 potential causes:
1. Cause description
2. Why it contributes to the problem
3. Can we verify it? (data source or observation method)
4. Controllable? (Yes — we can change it / No — external factor)
Output:
1. Fishbone diagram (text format with branches)
2. Top 3 most likely root causes (with evidence and confidence)
3. Verification plan (how to confirm each root cause)
4. Preliminary improvement ideas for each root cause
Format: RCA document for the improvement team.

5. Statistical Analysis Planner

Role: Six Sigma analyst (Black Belt level)
Task: Plan the statistical analysis for [process metric] improvement.
Metric: [Define — e.g., defect rate, cycle time, first pass yield]
Current performance: [Mean, standard deviation, if available]
Target: [Where we need to be]
Analysis plan:
1. What data to collect (sample size, frequency, duration)
2. Measurement system analysis (is the data reliable? Gage R&R needed?)
3. Baseline capability analysis (Cp, Cpk, Pp, Ppk targets)
4. Hypothesis tests needed (what to compare, which test, alpha level)
5. Regression analysis (which factors might drive the metric?)
6. DOE recommendation (if applicable — which factors, which design)
7. Control chart type (X-bar R, I-MR, p-chart, etc.)
Output: Statistical analysis plan ready for execution.
Include: Tool recommendations (Minitab, JMP, Python, Excel).

Solution Design & Implementation

6. Future State Process Design

Role: Process redesign consultant
Task: Design the future state for [process name].
Current state issues: [Top 5 problems from analysis]
Improvement goals: [Specific, measurable targets]
For the future state:
1. Process map (streamlined, waste eliminated)
2. Roles and responsibilities (RACI)
3. Technology changes (new tools, automation, integration)
4. Policy/procedure changes (rules, thresholds, approvals)
5. Key differences from current state (before/after comparison)
6. Expected improvements (cycle time, cost, quality, satisfaction — with specific numbers)
7. Implementation approach (pilot first? phased? big bang?)
8. Dependencies and prerequisites
9. Risk assessment (what could go wrong with the new design)
Format: Future state document ready for steering committee approval.
Constraint: Show the math — if you claim 30% improvement, show how that is calculated.

7. Pilot Test Design

Role: Process improvement project manager
Task: Design a pilot test for [improvement idea].
Improvement: [Describe the change being tested]
Pilot scope:
1. What is included (which steps, which people, which location)
2. What is excluded (what stays the same)
3. Duration ([time period])
4. Sample (which transactions/customers/products)
Metrics:
1. Primary metric (what we are trying to improve)
2. Secondary metrics (what we need to watch for unintended impacts)
3. Baseline (current performance for comparison)
4. Target (what success looks like)
5. Tracking method (how data will be collected)
Output:
1. Pilot plan document
2. Success/fail criteria
3. Go/no-go decision criteria
4. Rollback plan (if pilot fails, how do we revert?)
5. Communication plan (who needs to know about the pilot)
Format: Pilot test charter ready for approval.

8. Change Management for Process Improvement

Role: Change management consultant
Task: Create a change management plan for [process improvement].
Change: [Describe what is changing]
Affected stakeholders: [List with how they are affected]
For each stakeholder group:
1. Current state comfort (what they do now)
2. Future state change (what they will do differently)
3. Concern level (Low/Med/High — why?)
4. Communication approach (message, channel, timing)
5. Training needs (what skills, what format, when)
6. Resistance mitigation (anticipated objections and responses)
Output:
1. Change impact assessment
2. Communication plan (timeline with messages)
3. Training plan (topics, format, schedule)
4. Resistance management strategies
5. Adoption metrics (how to measure if people are using the new process)
6. 30/60/90 day milestones
Format: Change management plan for process improvement initiative.

Control & Sustainment

9. Control Plan Generator

Role: Six Sigma Black Belt creating a control plan
Task: Create a process control plan for [improved process].
For each critical metric:
1. Metric name and definition
2. Specification (target, upper limit, lower limit)
3. Measurement method (how it is collected, by whom, how often)
4. Control method (control chart, checklist, dashboard, alarm)
5. Reaction plan (what to do if out of spec — step by step)
6. Owner (role responsible for monitoring)
7. Escalation path (who to notify, when)
8. Review frequency (hourly, daily, weekly, monthly)
9. Audit requirements (who audits, how often, what to check)
Output: Control plan with 8-12 metrics covering quality, speed, and cost.
Include: Process documentation requirements (SOP updates, training materials, visual aids).

10. Continuous Improvement Backlog

Role: CI program manager
Task: Create a continuous improvement backlog for [process/department].
Sources: [Process audits, employee suggestions, customer feedback, performance metrics]
For each improvement opportunity:
1. Title (short, descriptive)
2. Problem statement (what is suboptimal)
3. Proposed improvement (high level)
4. Impact estimate (cost savings, time savings, quality improvement)
5. Effort estimate (Small/Medium/Large)
6. Priority (Impact x Ease matrix — Quick Win / Major Project / Fill-in / Thankless)
7. Suggested owner (team/role)
8. Dependencies (what needs to happen first)
Generate 15-20 opportunities across different categories.
Format: CI backlog table sorted by priority.
Include: Quarterly review process — how to keep the backlog alive.

11. Kaizen Event Planner

Role: Kaizen facilitator
Task: Plan a kaizen event for [process/problem].
Duration: [3-5 days]
Team: [Cross-functional — list roles]
Problem: [What needs improvement]
Pre-event:
1. Data collection (what to gather before the event)
2. Stakeholder interviews (who to talk to, what to ask)
3. Pre-event training (Lean basics for participants)
During event (day by day):
- Day 1: Current state mapping and data collection
- Day 2: Root cause analysis and waste identification
- Day 3: Future state design and solution brainstorming
- Day 4: Implementation planning and rapid pilots
- Day 5: Report-out and action plan finalization
Output:
1. Event charter
2. Day-by-day agenda with objectives
3. Pre-event checklist
4. Post-event 30/60/90 day follow-up plan
5. Success metrics (baseline and targets)
Format: Kaizen event playbook ready to execute.

12. Process Maturity Assessment

Role: Process maturity assessor (CMMI framework)
Task: Assess the maturity of [process] and recommend advancement path.
For each CMMI level (1-5):
1. Initial (chaotic, ad hoc)
2. Managed (planned, documented)
3. Defined (standardized, tailored from organizational standards)
4. Quantitatively Managed (measured, controlled using statistics)
5. Optimizing (continuous improvement, data-driven)
Assess current state against each level:
1. Evidence of current level (what proves we are here?)
2. Gaps to next level (what is missing?)
3. Actions to advance (specific steps, timeline, owner)
4. Benefits of advancing (what do we gain?)
Output:
1. Current maturity level with justification
2. Gap analysis to next level
3. 12-month advancement roadmap
4. Required resources and investment
Format: Maturity assessment report for leadership.

Best Practices

For more operational excellence content, see our ChatGPT prompts for operations managers and ChatGPT prompts for quality assurance.