How do I redesign a process that isn't working?
Updated
Map the current process as it runs today, including workarounds. Measure cycle time and error rate, find the step causing the most delay or rework, and redesign from that point. Test the new version alongside the old one before switching over. CorZen turns that into weekly tasks with an owner on each, on the timeline you choose.
Quote requests, mapped as they run today
- Request loggedSales · 10 min of work0.5 days waiting
- Job pricedEstimator · 45 min of work3 days waitingBottleneck
- Quote approvedManager · 5 min of work1.5 days waiting
- Quote sentSales · 10 min of workno wait
Example: quote requests at a small print shop.
What does a process redesign plan look like?
This is a sample 90-day roadmap for the Process Optimization category with the Architect approach. CorZen also builds 30-day, 60-day, custom, and ASAP timelines. Your own plan changes with your market, your tools, and how many hours your team has each week.
Map the current state
Weeks 1–4
- Week 1Walk through the process with the people who do it.
- Week 2Measure cycle time and error rate.
- Week 3Find the bottleneck.
- Week 4Find its root cause.
Redesign
Weeks 5–8
- Weeks 5–6Design the new flow.
- Week 7Run it in parallel with the old one on 10 cases.
- Week 8Compare results.
Cut over
Weeks 9–13
- Week 9Switch to the new process.
- Week 10Update documents and training.
- Weeks 11–12Monitor for new failures.
- Week 13Report against the baseline.
How do you map a process as it runs today?
Walk through the process with the people who do it, using a real recent case. Write down every step they take, including the workarounds that never made it into the written version.
As written down
- Sales logs the request
- Estimator prices the job
- Manager approves the quote
- Sales sends the quote
As it runs today
- Sales logs the request
- Sales retypes the email into the quote spreadsheetWorkaround
- Estimator asks the customer for missing specs1 in 3 jobs
- Estimator prices the job
- Manager approves quotes in a batch on FridaysWorkaround
- Sales sends the quote
The workarounds matter most. Each one is a sign that the written process stopped matching the work, and they often hide where the time goes.
How do you measure the current process?
Take the last 20 cases and record two numbers: how long each took from start to finish, and how many had to be redone. This is the baseline the redesign has to beat.
Example numbers. Use the median for cycle time, so one unusually slow case doesn’t skew the baseline.
How do you find the bottleneck and its root cause?
The bottleneck is the step where work waits longest. Once you’ve found it, keep asking why until the answer is something you can change.
- Why do quotes wait 3 days for pricing?The estimator can’t start until the job specs are complete.
- Why are the specs incomplete?One request in three is missing the quantity, paper stock, or finish.
- Why is that information missing?Requests come by email, and nothing asks the customer for it.
The intake step doesn’t collect what pricing needs.
Fixing the symptom here, such as hiring a second estimator, would leave the missing specs in place. Fixing the root cause removes the waiting for everyone.
How do you redesign a process from the bottleneck?
Start the new design at the step causing the delay, and only change what the root cause touches. Leave the steps that work alone.
Old flow
- Email request
- Retype into spreadsheet
- Chase missing specs
- Price the job
- Wait for Friday approval
- Send the quote
New flow
- Web form with required specs
- Price the job
- Approval only over $5,000
- Send the quote
Example redesign. The form collects the specs up front, so the chasing step disappears. Manager approval stays only where the risk is high enough to need it.
How do you test a new process before switching over?
Run the new process on 10 real cases while the old one handles the rest. Compare the same numbers you used for the baseline.
| Measure | Old process, 10 quotes | New process, 10 quotes |
|---|---|---|
| Median cycle time | 5 days | 1.5 days |
| Revised after sending | 3 of 10 | 1 of 10 |
| Work time per quote | 70 min | 55 min |
Example results. Ten cases is a small sample, so look for a clear difference, not a few percent.
How do you switch to the new process without breaking things?
Switch on a set date, close the old route so nobody uses it by habit, and watch closely for the first two weeks.
Cutover checklist
- Pick a switch date and tell everyoneIncluding customers, if the way they contact you changes.
- Close the old routePoint the old email address to the new form.
- Update the documents and trainingSo nobody falls back on the old steps.
- Check for new failures daily for two weeksNew processes break in new places.
- Agree a rollback rule in advanceFor example, go back if cycle time is worse than the baseline for a full week.
At the end, report cycle time and error rate against the baseline from the start, using the same method.
How does the plan change on a 30- or 60-day timeline?
The order stays the same on every timeline: map the current state, redesign, then cut over. Shorter timelines test on fewer cases. Custom and ASAP timelines keep the same order.
| Timeline | Map the current state | Redesign | Cut over |
|---|---|---|---|
| 90 days | Walk-through, baseline, bottleneck, root cause, weeks 1–4 | New flow, parallel run on 10 cases, weeks 5–8 | Switch, training, monitoring, report, weeks 9–13 |
| 60 days | Walk-through, baseline, root cause, weeks 1–2 | New flow, parallel run on 5 cases, weeks 3–5 | Switch, monitoring, report, weeks 6–9 |
| 30 days | Walk-through and baseline, week 1 | Fix at the bottleneck, test on a few cases, weeks 2–3 | Switch and first check, week 4 |
On a 30-day plan, keep the redesign to the bottleneck step. A wider redesign needs a proper parallel run first.
Should you redesign the process, reduce errors, or speed it up?
All three are ways to optimize a process that already exists. Pick the one that matches what’s going wrong.
Redesign
The process is slow and error-prone, and patches haven’t helped.
Reduce errors
The steps are fine, but work keeps coming back for fixes.
Speed it up
The work is right, but it takes too long to get through.
How does CorZen build this plan for you?
Tell CorZen your goal. Pick Process Optimization, then the Architect approach, then a timeline: 30, 60, or 90 days, a custom length, or ASAP. A short AI interview asks about your niche, what makes your business different, the tools you already use, and how much time your team has each week.
CorZen then builds a roadmap for that timeline, broken into weekly tasks. Every task has an owner, and a task can have more than one. On Team and Business plans, AI agents can draft deliverables for individual tasks, such as the new process documents and training notes.
Frequently asked questions
What is a bottleneck in a process?
The step where work waits the longest before moving on. Speeding up any other step won't shorten the whole process much, because the work still queues at the bottleneck.
How do you find the root cause of a process problem?
Ask why the problem happens, then ask why again about each answer, until you reach something you can change. It usually takes three to five rounds.
Should you redesign a process or fix it?
Fix it if one step is the problem. Redesign it when the workarounds have piled up, the written version no longer matches the work, and several steps cause delay or rework.
What is a parallel run?
Running the new process on a small set of real cases while the old process handles the rest. It shows whether the redesign works before everyone switches.
Can AI agents help redesign a process?
They can draft the work for a person to review, such as the current-state map, the new process document, or training notes. On CorZen's Team and Business plans, AI agents can draft deliverables for individual tasks in your plan.