Redesign a process for speed and quality with a future-state map
Redesigns a current process into a faster, higher-quality future-state workflow and compares the two side by side so you can get approval.
The prompt
Redesign this process for speed and quality, create the future-state workflow, and compare it with the current process.
Process and its purpose: [WHAT IT DOES and who receives the result]
Current-state steps: [PASTE the steps with roles, systems, and times - or a process map description]
Known problems: [delays, errors, complaints, rework, bottlenecks]
Goals for the redesign: [e.g. "cut cycle time from 10 days to 3", "halve error rate"]
Constraints: [systems we must keep, budget, compliance controls, headcount]
Design principles to apply: remove steps that add no value, do work in parallel where possible, move quality checks to the point where errors are made, reduce handoffs, standardize inputs with templates or forms, set clear decision rules, and automate only after simplifying.
Return:
1. Future-state workflow: numbered steps with role, action, system, expected time, and the check or control at each step. Also give it as a simple swimlane outline (lane = role) that I can draw in Visio, PowerPoint, or Miro.
2. Comparison table: Measure | Current | Future | Change - covering number of steps, handoffs, approvals, cycle time, work time, likely error points, and manual touches.
3. What changes for each role.
4. What it needs to work: tools, templates, training, policy changes.
5. Risks of the new design and how to reduce them.
6. A rollout approach: pilot scope, success measures, and a fallback.
Only calculate time savings from times I provided; mark estimates [EST]. Keep every compliance or control step unless I confirm it can change. The people who run the process should validate the design before rollout.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- WHAT IT DOES and who receives the result
- delays, errors, complaints, rework, bottlenecks
- e.g. "cut cycle time from 10 days to 3", "halve error rate"
- systems we must keep, budget, compliance controls, headcount
- EST
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Turn my project plan into an Excel task tracker with owners and dependenciesBreaks a project or plan into a task tracker with owners, dates, dependencies, and status columns you can paste into Excel.
- Run a health check on my project and find what is going wrongScores your project across scope, schedule, budget, risk, team, and stakeholders, and pinpoints the real problems behind the noise.
- Audit my project plan for missing owners, deadlines, and unaddressed risksChecks your plan or tracker for tasks with no owner, no deadline, vague deliverables, and risks nobody is managing.
- Resolve conflicting stakeholder priorities on my projectLays out where stakeholders' demands on one project clash, what each choice costs, and a clear decision request for whoever can settle it.