Process Bottleneck Diagnosis and Workflow Redesign With Pilot Plan

Maps a current team workflow, finds bottlenecks and handoff failures, designs a leaner future-state process with roles and automation candidates, and outlines a low-risk pilot with success metrics.

You get: Executive Summary and Pilot Recommendation, current-State Process Table and bottleneck Ranking

More like this

The prompt

process-bottleneck-diagnosis-and-workflow-redesign-with-pilot-plan.md
Role: You are an operations excellence consultant experienced in process mapping, lean workflows, and practical AI-assisted automation for business teams.

Context: The workflow in question is {workflow_name} owned by {team_name}. The business problem is {problem_statement}. Volume is roughly {volume_per_period}. The tools and systems currently used are {current_tools}. Team size and roles: {team_roles}. Compliance or approval constraints: {compliance_constraints}.

Task: Diagnose where this workflow loses time, quality, or money and design a better future-state workflow. The job-to-be-done is to help {decision_owner} decide whether to fund and pilot a redesign, and what the pilot should look like.

Inputs (collect before analysis):
- Step-by-step description of the current process, including handoffs, approvals, and waiting points: {current_process}
- Observed pain points, error types, and rework: {pain_points}
- Any timing data (cycle time, wait time, error rate) I can provide: {timing_data}
- Target outcome and metric: {target_outcome}
- Budget and change-capacity limits: {budget_limits}
If steps or timing are missing, ask up to 6 clarifying questions first. List every gap and assumption separately. Mark any estimated figure as an estimate.

Workflow:
1. Restate the process as a numbered step table: step, owner, tool, input, output, typical duration, known failure mode.
2. Identify bottlenecks, handoff delays, rework loops, and unclear ownership. Rank the top 5 by estimated impact on {target_outcome} and give the evidence from my inputs.
3. Classify each step as Keep, Simplify, Automate, Delegate, or Remove, with a one-line reason.
4. Design the future-state workflow with a step table in the same format, plus a RACI table (Responsible, Accountable, Consulted, Informed).
5. Identify automation or AI-assist candidates. For each, state the task, human review point, data it needs, and risk if it errs. Do not recommend automation where compliance constraints require human sign-off.
6. Build a pilot plan: scope, duration, participants, baseline metrics, success threshold, stop criteria, and rollback steps.
7. Build a risk register: risk, likelihood, impact, mitigation, owner role.
8. Summarize the cost, effort, and expected benefit range, labeled as estimates with the logic shown.

Output format:
1. Executive Summary and Pilot Recommendation (go, go with conditions, or no-go, with reasons)
2. Current-State Process Table
3. Bottleneck Ranking (table with evidence)
4. Step Disposition (Keep, Simplify, Automate, Delegate, Remove)
5. Future-State Process Table and RACI
6. Automation and AI-Assist Candidates (table)
7. Pilot Plan (scope, metrics, thresholds, stop criteria, rollback)
8. Risk Register
9. Assumptions, Missing Information, and Next Actions (owner, action, date)

Constraints: Do not invent time savings, costs, or tool capabilities. Use ranges and show assumptions. Do not include private or personal data in examples. Keep the redesign achievable with {budget_limits}. Avoid generic advice; tie every recommendation to a step in the process.

ChatGPT-specific instructions: Ask clarifying questions in one numbered message before building the tables. If I attach process documents or screenshots, extract steps and confirm your reading before redesigning. Present tables in markdown and offer to create a canvas version of the pilot plan or a checklist for the team.

Acceptance criteria:
- Each bottleneck is linked to a specific step and to evidence from my inputs
- The future-state process has named owners and fewer or clearer handoffs
- The pilot has a measurable success threshold, stop criteria, and rollback
- Estimates are labeled and their logic is visible
- Next actions are specific enough to start within one week

Quality checks (run silently, then show a brief checklist):
- Every step in the current-state table appears in the disposition table
- Every automation candidate has a human review point
- No figure appears without an input or an assumption label

Example output

AI-written example

1. Executive Summary: Go with conditions
Invoice approval for the AP team averages 11 days against a 6-day target. Approval wait (about 5 days) and PO-mismatch exceptions (18%) cause most of the delay. Pilot with one department for 6 weeks, on the condition that the Controller confirms invoices over $5,000 keep manual manager approval.

2. Current State

#StepOwnerToolDaysFailure mode
1Receive invoiceClerkShared inbox0.5Duplicates, lost emails
2Key dataClerkERP1Typos
3PO matchClerkERP1.518% mismatch
4Route for approvalClerkEmail5No reminders
5Fix exceptionsClerk/BuyerEmail2 (est.)Unclear owner
6Payment runAP LeadERP1Weekly batch

3. Bottlenecks (ranked)

  1. Step 4: email approvals with no escalation (5-day wait, from timing data)
  2. Step 5: exceptions with no named owner (est. 2 days)
  3. Step 3: manual matching (18% mismatch)
  4. Step 6: weekly payment batch (adds up to 7 days of wait, est.)
  5. Step 2: manual keying (typo rework, est.)

4. Disposition
1 Simplify · 2 Automate · 3 Automate (flag only) · 4 Simplify · 5 Delegate · 6 Simplify

5. Future State and RACI

StepRACI
Intake to ERP queueClerkAP LeadVendorn/a
Match checkClerkAP LeadBuyer
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Describe the real current process, including workarounds and waiting time, not the documented ideal. Provide even rough timing data. Start with one workflow rather than a whole department. Validate estimates with the people who do the work before presenting the plan.

Questions about this prompt

Repetitive Task to Zapier, n8n or Make Automation Spec

Turns a repetitive task into a build-ready automation spec with triggers, AI steps, human checkpoints, failure handling and a test plan.

Process Transcript to Standard Operating Procedure

Converts a pasted process description or transcript into an SOP with purpose, roles, numbered steps, checklists and common mistakes.

Weekly Operating Review: KPI Variance Diagnosis and Action Plan

Analyzes weekly KPI data against targets, separates signal from noise, proposes ranked root-cause hypotheses, and produces owner-assigned actions and an escalation list for a team operating review.

Operations Bottleneck Diagnosis and 30-Day Process Fix Plan

Diagnoses where a workflow slows down using your process steps and metrics, then ranks causes and produces a 30-day improvement plan with owners, measures, and risks.

4-Week Small Business Launch Plan: $0 and Small-Budget Versions

Builds a 4-week launch plan for a product or service in a specific market, with channels and weekly tasks in a $0 version and a small-budget version.

Customer Support Macro Set for Refunds, Delays, Angry Customers and Escalation

Writes 10 ready-to-send support reply macros in your brand tone covering refunds, delays, angry customers and escalation.

Executive Decision Memo Builder With Options, Risks, and Recommendation

Turns a pending business decision into a one-page-style decision memo with scored options, explicit assumptions, risks, missing information, a recommendation, and next actions an executive can approve or reject.

Standard Operating Procedure From a Screen-Recording Transcript

Turns the transcript of a recorded walkthrough into a numbered SOP with prerequisites, steps, screenshots to capture, decision points, and common mistakes, ready for a team wiki.

Excel and Google Sheets Formula Builder With a Plain-English Explanation

Writes the formula for what you want a spreadsheet to do, in both Excel and Google Sheets syntax, explains each part, and gives a test case so you can check it works.

Meeting Notes to Action Items, Owners and a Ready-to-Send Follow-Up Email

Turns raw meeting notes or a transcript into decisions, action items with owners and dates, open questions, and a short follow-up email you can send right after the call.

Spreadsheet and CSV Cleanup Report Skill (SKILL.md)

A SKILL.md that has your agent profile a messy CSV or spreadsheet, fix it in a copy with a script, and report every change so the cleaned data can be trusted.

Trending

Developmental Edit Memo for an Essay Draft With Revise-or-Cut Decisions

Gives a draft essay a structured developmental edit: thesis check, paragraph-by-paragraph audit, and a prioritized revision plan so you can decide what to keep, rewrite, or cut before line editing.