Business Process Discovery & Workflow Mapping

Map a client's workflow, quantify waste, and recommend AI automation.

Introduction

30 Second Summary

Every business has processes that look fine on paper but quietly waste hours of people's time each week. The gap between how leadership thinks work flows and how it actually flows is where consultants find the biggest opportunities.

In this project, you will conduct a complete process discovery engagement for a fictional accounting firm. You will design a stakeholder interview guide, map their workflow as a professional swimlane diagram, and deliver a report that quantifies exactly where AI and automation would save time and money.

What You'll Build

Imagine sitting across from a client partner, pulling up your annotated workflow diagram, and showing them that their 12-day onboarding process contains only 2 hours of actual value-adding work.

By the end of this project, you'll have:

A reusable interview methodology that extracts quantifiable operational data from stakeholder conversations, giving you the numbers you need to build a business case for automation.
A current-state swimlane diagram in draw.io with time annotations and color-coded waste categories that make invisible handoff failures and wait times impossible to ignore.
A Process Discovery Report with an executive summary, quantified findings, and prioritized automation recommendations backed by dollar figures that give the client a clear starting point.
Secret Mission: Build a Feasibility-Impact scoring matrix and plot each opportunity on a visual quadrant diagram that creates a defensible implementation sequence.

Do I need any special tools?

You need Microsoft Word (or a compatible word processor) and draw.io, which is completely free and runs in your browser at app.diagrams.net with no account required.

Before We Start

Before we dive in, let's lock in what you're about to build and why it matters.

You are about to conduct a process discovery engagement for a realistic consulting scenario. Before building anything, commit to what you are producing and why process discovery must come before recommending AI solutions.

Set Up Your Consulting Workspace

Every consulting engagement starts before the first meeting. You need a structured workspace where interview notes, diagrams, and deliverables each have a clear home.

In this step, you will open draw.io for professional diagramming, create a repeatable folder structure for the engagement, and start the report document that becomes your client deliverable.

In this step, get ready to:

Open draw.io and confirm swimlane shapes are available for workflow mapping.
Create a structured project folder with subfolders for interviews, diagrams, and deliverables.
Start the Process Discovery Report with a professional title page.

Open draw.io and confirm swimlane shapes are available

Your workflow diagram will use swimlane shapes to show how work moves between different people. Before you start mapping, you need to confirm the diagramming tool has these shapes ready.

Open your web browser and navigate to app.diagrams.net.
A storage location dialog appears. Select Device to save diagrams locally on your machine.
Click Create New Diagram.
In the template manager, leave Blank Diagram selected and click Create.

You should now see the draw.io editor with a blank canvas. The shapes panel is on the left side of the screen.

In the left shapes panel, confirm you can see the General shape library (basic flowchart shapes like rectangles and diamonds).
Scroll down in the left panel and confirm the Advanced shape library is also visible.
Click on the Advanced section header to expand it. You should see horizontal container shapes. These are the swimlane and pool shapes you will use for workflow mapping.

What is a swimlane diagram?

A swimlane diagram divides a process into horizontal rows, one per person or role. Each step in the workflow sits inside the lane of the person responsible for it. Arrows that cross lane boundaries represent handoffs between people.

This makes it immediately obvious who does what and where work gets stuck waiting for someone else.

Why draw.io over other tools?

draw.io is completely free with no account required, no document limits, and includes full swimlane and BPMN shape libraries. It saves files locally so you can include diagrams directly in client deliverables.

Lucidchart limits its free tier to 3 documents with 60 shapes each. For a consulting engagement with multiple diagrams, that restriction would block you mid-project.

Don't see the Advanced shapes?

If the left panel only shows General shapes, click More Shapes at the bottom of the shapes panel. Make sure the Advanced library checkbox is enabled, then click Apply.

If the shapes panel itself is hidden, press Ctrl+Shift+K (Windows) or Cmd+Shift+K (macOS) to toggle it back on.

Help me find swimlane shapes in draw.io

Create your project folder structure

A repeatable folder structure keeps your engagement organized. Every interview note, diagram export, and report draft has a predictable home.

Windows

Open a terminal by pressing the Windows key, typing PowerShell, and pressing Enter.
Create the project folder and all three subfolders by running these commands:

mkdir C:\Projects\henderson-discovery\interviews
mkdir C:\Projects\henderson-discovery\diagrams
mkdir C:\Projects\henderson-discovery\deliverables

Confirm the folders were created by running:

ls C:\Projects\henderson-discovery

You should see three folders listed: deliverables, diagrams, and interviews.

macOS

Open a terminal by pressing Cmd+Space, typing Terminal, and pressing Enter.
Create the project folder and all three subfolders by running this command:

mkdir -p ~/Projects/henderson-discovery/interviews ~/Projects/henderson-discovery/diagrams ~/Projects/henderson-discovery/deliverables

Confirm the folders were created by running:

ls ~/Projects/henderson-discovery

You should see three folders listed: deliverables, diagrams, and interviews.

What is this folder structure for?

The interviews folder stores your interview guide and stakeholder notes. The diagrams folder stores draw.io diagram files. The deliverables folder stores the final report you present to the client.

This separation means you can copy this exact structure for every new engagement. The only thing that changes is the client name in the top-level folder.

Seeing a permission error?

On Windows, make sure you are running PowerShell as a regular user. The C:\Projects\ folder does not require admin privileges to create.

On macOS, the ~/Projects/ folder is inside your home directory and should not require elevated permissions.

Help me create my project folders

Start the Process Discovery Report

The report document is your primary client deliverable. Starting it now with a professional title page means you have a living document to build on throughout the engagement.

Press Cmd+Space (macOS) or the Windows key (Windows) to open your search bar.
Type Word and press Enter to open Microsoft Word.
Create a new blank document.
Click File then Save As.
Navigate to your henderson-discovery\deliverables folder.
Name the file Process-Discovery-Report.docx and click Save.

Now add a title page to set the professional tone of your deliverable.

On the first page, type the project name: Business Process Discovery & Workflow Mapping.
Below it, type the client name: Henderson & Associates CPAs.
Add your own name as the consultant.
Add today's date.
Add a DRAFT watermark by clicking the Design tab, then Watermark.
Select the DRAFT option and click OK.
Save the document with Ctrl+S (Windows) or Cmd+S (macOS).

Why start the report now?

Professional consultants create their deliverable structure before beginning analysis. This ensures findings flow into the document as you discover them rather than requiring a separate writing sprint at the end.

The DRAFT watermark signals to anyone who sees the document that it is still in progress. You will remove it before final delivery.

Can't find the Watermark option?

The watermark location varies slightly between Word versions. If you do not see it under Design, try Page Layout or Format in the ribbon. On macOS Word, look under Design in the menu bar.

If you cannot find it at all, skip the watermark for now. You can add it later. The important part is that the title page content is saved.

Help me add a DRAFT watermark in Word

Before you move on, do a quick mental check. What do you think your folder should contain at this point?

Open the henderson-discovery folder in File Explorer (Windows) or Finder (macOS).
Confirm you see three subfolders: interviews, diagrams, and deliverables.
Open the deliverables folder and confirm Process-Discovery-Report.docx is saved there.

Your consulting workspace is ready. You have a diagramming tool with swimlane shapes loaded, an organized folder structure, and a report document waiting for findings.

Next up, you will design a stakeholder interview guide and use it to conduct discovery interviews that surface the quantifiable data every automation business case needs.

Design Your Stakeholder Interview Guide and Conduct Discovery

Your consulting workspace is organized and your report template is waiting for content. Now it's time to build the methodology that fills it with real, actionable data.

Without a structured interview framework, discovery conversations produce vague pain descriptions like "things are slow" instead of the quantifiable data you need to build a business case. Structured questions that target specific numbers (time per task, error frequency, handoff delays) are what separate professional process discovery from a casual chat.

In this step, get ready to:

Design a stakeholder interview guide with questions that extract quantifiable data.
Conduct simulated discovery interviews with three personas at Henderson & Associates.
Identify and highlight quantified data points that will power your analysis.

Design your stakeholder interview guide

A good interview guide follows a deliberate sequence. You open with rapport-building, then walk through the process, then drill into numbers, then probe for pain, and finally map the tool landscape. Each section builds on what the previous section uncovered.

Open Microsoft Word and create a new document.
Save it as Interview-Guide.docx inside your henderson-discovery\interviews folder.
Add a title at the top: Stakeholder Interview Guide - Henderson & Associates Process Discovery.

Now structure the document with these five section headings. Under each heading, write 3-4 specific questions using the examples below as a starting point.

Add the heading Section 1: Interview Opening and write questions like:
Add the heading Section 2: Process Flow Questions and write questions like:
Add the heading Section 3: Quantification Questions and write questions like:
Add the heading Section 4: Pain Point Questions and write questions like:
Add the heading Section 5: Tools & Systems and write questions like:

Save Interview-Guide.docx.
Scroll through your document and count the total questions. You should have at least 15 specific questions across the 5 sections.

Why five sections in this order?

The sequence is deliberate. Opening questions build rapport and establish context. Process flow questions map what actually happens. Quantification questions attach numbers to each step. Pain point questions surface frustrations. Tools questions reveal the system landscape.

By the time you reach the pain points, the interviewee has already described their process in detail. They give you specific, grounded answers instead of vague complaints.

Not sure what questions to write?

Focus on questions that force a number into the answer. "How long" and "how often" are your best friends. Every question should make it hard for someone to answer without giving you a time, a count, or a percentage.

Help me write quantification questions for a process discovery interview.

Conduct simulated discovery interviews

Henderson & Associates is a 35-person accounting firm whose IT your MSP manages. The managing partner has asked you to look at their new client onboarding process because it feels "too slow." You are about to interview three people who each touch a different part of that process.

Read each persona's response below as if you conducted the interview in person. Then create a notes document capturing the key data points from their answers.

Sarah Chen, Office Manager (8 years at firm)

"New client intake starts when a partner forwards me an email saying they have agreed to take on someone new. I print the engagement letter template from Word, manually fill in the client details, then scan it and email it to the client for signature. Once signed, I re-enter all the client information into our practice management system."

"Then I create folders in SharePoint, set up their profile in our tax software, and add them to our billing system. The whole thing takes me about 90 minutes per client, and we onboard 8-12 new clients per month. The worst part is entering the same name, address, EIN, and entity type into four different systems."

"I make typos maybe 15% of the time because I am rushing between screens. When that happens, it takes another 20 minutes to find and fix across all systems."

Create a new Word document and save it as Sarah-Chen-Notes.docx in your interviews folder.
Write up your interview notes capturing the key data: 90 minutes per client for data entry across 4 systems, 8-12 clients per month, 15% typo rate, 20 minutes to fix each error, and the specific systems involved (practice management, SharePoint, tax software, billing).
Save the document.

David Park, Senior Accountant (5 years at firm)

"After Sarah sets up the client, I get an email saying they are ready. But I usually do not see it for a day or two because it gets buried. Then I need to request prior-year tax returns and financial statements from the client. I send a checklist email and wait."

"Average response time is 5 business days, but I have to send follow-up emails to about 60% of clients. Once documents arrive, I review them for completeness. About 30% of the time something is missing and I go back to the client again. The document review itself takes 45 minutes. I spend probably 3 hours per week just on follow-up emails for various clients in the pipeline."

Create a new Word document and save it as David-Park-Notes.docx in your interviews folder.
Write up your interview notes capturing the key data: 1-2 day delay before seeing handoff emails, 5 business day average client response time, 60% of clients needing follow-up reminders, 30% incomplete document submissions, 45-minute document review, and 3 hours per week on follow-up emails.
Save the document.

Michael Torres, Managing Partner (founding partner)

"I have no visibility into where a new client sits in the onboarding pipeline unless I ask Sarah directly. Sometimes clients call me asking why nobody has reached out yet, and I am embarrassed because I assumed it was already handled."

"I estimate we lose 2-3 potential clients per year because onboarding takes too long and they go elsewhere. At our average client value of $8,500/year in fees, that is real money. I also spend about 30 minutes per new client reviewing and signing the engagement letter, but half the time Sarah brings it to me with errors I have to catch and send back."

Create a new Word document and save it as Michael-Torres-Notes.docx in your interviews folder.
Write up your interview notes capturing the key data: no pipeline visibility, 2-3 clients lost per year, $8,500 average annual client value ($17,000-$25,500 in lost revenue), 30 minutes per engagement letter review, and 50% of letters returned with errors.
Save the document.

Open your interviews folder in File Explorer (Windows) or Finder (macOS). You should see four files: Interview-Guide.docx, Sarah-Chen-Notes.docx, David-Park-Notes.docx, and Michael-Torres-Notes.docx.

Missing a file?

Make sure you saved each document into the interviews subfolder specifically, not the parent henderson-discovery folder. Check the parent folder and the deliverables folder in case a file landed in the wrong place.

Help me organize my discovery project files.

Review and highlight quantified data points

Your three sets of notes contain a mix of qualitative pain descriptions and hard numbers. The numbers are what set professional process discovery apart from a casual conversation. They are what you will use to build the business case in your final report.

Open each of your three interview note documents one at a time.
Highlight or bold every data point that includes a specific number. Look for time durations, frequencies, percentages, error rates, and dollar figures.
In Sarah's notes, you should find at least 5 quantified data points (90 min, 8-12 clients/month, 4 systems, 15% error rate, 20 min rework time).
In David's notes, look for at least 5 data points (1-2 day delay, 5 day response time, 60% needing follow-up, 30% incomplete, 45 min review, 3 hours/week).
In Michael's notes, look for at least 4 data points (2-3 clients lost, $8,500 per client, 30 min review, 50% error rate on letters).
Save all three documents after highlighting.

Why do these numbers matter so much?

A consultant who says "the onboarding process has problems" gets a polite nod. A consultant who says "you are losing $17,000-$25,500 per year in client attrition because onboarding takes 12 days instead of 2" gets a signed contract.

Every highlighted number in your notes is ammunition for the business case you will build in your Process Discovery Report. The more specific your data, the harder it is for a stakeholder to dismiss your recommendations.

Look across all three sets of notes. You should notice recurring themes appearing: duplicate data entry, handoff delays, lack of visibility, and manual chasing.

Confirm that your interview guide has at least 15 specific questions across all 5 sections.
Confirm that each of your three interview note documents contains specific time estimates, frequencies, error rates, and at least one dollar implication.

You now have a complete set of discovery artifacts: a reusable interview methodology and three sets of data-rich notes. Next, you will transform these scattered observations into a single visual that makes the process problems impossible to ignore.

Map the Current-State Workflow

You now have three sets of interview notes packed with specific numbers, pain points, and process descriptions. The problem is that each person described their own slice of the workflow from their own perspective.

A swimlane diagram transforms these scattered observations into a single visual. It shows exactly how work moves between people, where handoffs happen, and where each role's responsibilities begin and end.

In this step, get ready to:

Set up a horizontal pool with four swimlanes representing each role in the onboarding process.
Map the complete new client onboarding workflow using shapes from your interview data.
Connect all steps with arrows and identify every handoff where work crosses between people.

Create a new diagram and set up your swimlanes

Each horizontal lane in a swimlane diagram represents a person or role. Any shape placed inside a lane belongs to that person's responsibility. When an arrow crosses from one lane into another, that crossing is a handoff.

Switch to your draw.io browser tab.
Click File in the top menu, then select New.
In the template dialog, edit the filename at the top to client-onboarding-current-state.
Select the Swimlane Diagram template from the Basic template collection, then click Create.

A default swimlane diagram appears on the canvas with a pool shape containing two lanes.

Double-click the pool title (the label at the top or left edge of the outer container) and rename it to New Client Onboarding - Current State.
Delete the existing sample shapes inside the template lanes by selecting them and pressing Delete or Backspace. Keep the pool and lane structure.
Rename the existing swimlane labels by double-clicking each lane's label text. Name the top lane Client and the second lane Managing Partner (Torres).
Add two more swimlanes: select the outer pool shape, then in the Arrange tab of the format panel on the right, click Insert Row After twice.
Label the third lane Office Manager (Chen) and the fourth lane Senior Accountant (Park).

Your canvas now shows an empty pool with four labeled horizontal lanes stacked top to bottom.

Save your diagram by pressing Ctrl+S (Windows) or Cmd+S (macOS). When prompted, save the file into your C:\Projects\henderson-discovery\diagrams\ folder.

What is a swimlane diagram?

A swimlane diagram organizes process steps into horizontal rows, one per role. Think of it like lanes in a swimming pool. Each person "swims" in their own lane, and the work flows left to right.

The outer container is called a pool. It represents the entire process. Inside the pool, each lane shows who is responsible for which steps.

Can't find the Arrange tab or Insert Row After?

The format panel lives on the right side of the screen. If you don't see it, click Format in the top menu to toggle it on. Make sure you have the outer pool shape selected (click its outer border) before looking for Insert Row After in the Arrange tab.

Help me set up swimlanes in draw.io

Map the process steps from your interview data

Now you will translate the interview notes into diagram shapes. Use rounded rectangles for activities, diamonds for decision points, a green circle for the start event, and a red circle for the end event.

In the Managing Partner (Torres) lane, drag a circle shape from the shape panel on the left and place it at the far left. Set its fill color to green using Format > Style in the format panel. Double-click to label it Partner agrees to take on client.
Add a rounded rectangle in the same lane to the right. Label it Partner emails Sarah about new client.

The process now moves into Sarah's lane. Drag the next shapes into the Office Manager (Chen) lane.

Add a rounded rectangle labeled Print and fill engagement letter.
Add another rounded rectangle labeled Email letter to Partner for review.

The letter goes back to Torres for review. Add the next shapes in the Managing Partner (Torres) lane.

Add a rounded rectangle labeled Review engagement letter.
Add a diamond shape (decision point). Label it Errors found?.
From the "Yes" path of the diamond, add a rounded rectangle back in the Chen lane labeled Correct errors and resend. This creates a rework loop.

From the "No" path (no errors), the letter goes to the client. Add the next shapes in the Client lane.

Add a rounded rectangle labeled Sign and return engagement letter.

The signed letter returns to Sarah. Add the data-entry steps in the Office Manager (Chen) lane.

Add a rounded rectangle labeled Enter client data into 4 systems.
Add a rounded rectangle labeled Email David that client is ready.

David picks up from here. Add the remaining steps in the Senior Accountant (Park) and Client lanes.

In the Park lane, add a rounded rectangle labeled Request documents from client.
In the Client lane, add a rounded rectangle labeled Send documents to firm.
Back in the Park lane, add a diamond labeled Documents complete?.
From the "No" path, add a rounded rectangle in the Park lane labeled Send follow-up request. Loop this back to the client response step.
From the "Yes" path, add a rounded rectangle in the Park lane labeled Review documents for completeness.
Finally, add a circle at the far right of the Park lane. Set its fill color to red. Label it Onboarding complete.

Count your shapes. You should have approximately 15-18 shapes distributed across all four lanes.

Why rounded rectangles and diamonds?

These are standard flowchart conventions. Rounded rectangles represent activities (work someone does). Diamonds represent decision points (a question with branching paths). Circles mark the start and end of the process.

Following these conventions means any business professional will immediately understand your diagram without a legend.

Shapes landing outside the lane?

When you drag a shape into a swimlane, the lane outline turns purple to confirm the shape will be added inside it. If you do not see the purple highlight, move the shape slightly until it appears, then drop. If a shape ends up outside a lane, drag it back over the lane until you see the purple outline and release.

Help me position shapes inside swimlanes in draw.io

Connect all steps and count your handoffs

Arrows turn a collection of shapes into a process flow. Every arrow that crosses from one lane into another represents a handoff. Handoffs are where work gets lost, delayed, or degraded in most business processes.

Connect your shapes in sequence: hover over the first shape until you see blue direction arrows appear, then drag from the arrow toward the next shape and release when the target shape highlights.
Start from the green circle and draw an arrow to Partner emails Sarah about new client.
Continue connecting each step to the next in the order you built them. When an arrow goes from a shape in one lane to a shape in a different lane, that arrow will cross the lane boundary visually.
For the two decision diamonds, draw two outgoing arrows each. Label one arrow Yes and the other No by double-clicking the arrow line and typing the label.
For the two rework loops (errors correction back to review, and follow-up back to client), draw arrows that loop back to earlier steps.

Before you count your handoffs, predict how many lane-boundary crossings you expect based on the interview data. Think about every time one person's work depends on another person acting.

Count every arrow that crosses a lane boundary in your diagram. Each one is a handoff.

You should find 7-9 handoffs. These include: partner to Sarah (email), Sarah to partner (letter for review), partner back to Sarah (errors), partner/Sarah to client (letter for signature), client back to Sarah (signed letter), Sarah to David (ready email), David to client (document request), client to David (documents sent), and David's follow-up loop.

Save your diagram with Ctrl+S (Windows) or Cmd+S (macOS).
Verify your completed diagram reads left to right and tells the full story from "Partner agrees to take on client" through to "Onboarding complete".

Why do handoffs matter so much?

Every handoff is a potential failure point. Work can sit in an inbox for days (David's 1-2 day delay). Information can degrade (Sarah's 15% error rate re-typing data). Status can become invisible (Torres having no pipeline visibility).

The more handoffs a process has, the more places things can go wrong. Your diagram just made these invisible failure points impossible to ignore.

Arrows not connecting to the target shape?

Make sure you drag from the blue direction arrow on the source shape and release directly on top of the target shape when it shows a green highlight. If an arrow floats disconnected, delete it and try again. Zoom in if the shapes are small.

Help me connect shapes with arrows in draw.io

Your diagram now tells the complete story of client onboarding at Henderson & Associates. It looks like a reasonable process. In the next step, you will overlay time data from your interviews and discover just how much hidden waste is lurking beneath this clean-looking flowchart.

Annotate with Time Data and Expose Hidden Waste

Your swimlane diagram from the previous step tells a clear story of how work moves between people. It looks like a reasonable process.

But a clean flowchart hides the truth. When you overlay the quantitative data from your interviews, you will discover that a process spanning 10+ business days contains less than 4 hours of actual work. The rest is waiting, rework, duplicate data entry, and chasing people. That gap between elapsed time and value time is what makes the business case for automation self-evident.

In this step, get ready to:

Add time annotations showing active work vs. wait time on every process step.
Apply a color-coded waste classification to expose bottlenecks, repetitive tasks, handoff failures, and duplicate data entry.
Calculate the process efficiency ratio that quantifies the waste in a single number.

Add time annotations to every step

Each shape in your diagram represents a task that has two time dimensions. There is the active time someone spends doing the work, and the wait time before the next person picks it up. Showing both on every step reveals where the process is actually spending its days.

Switch back to your client-onboarding-current-state.drawio diagram in draw.io.
For each shape, you will add a text label showing time in this format: Active: Xm | Wait: Xd. Right-click a blank area near the first shape and select Insert then Text to place a text label.
Start in the Managing Partner lane. Add a label near the "Partner agrees to take on client" start event: Active: 5m | Wait: 0.
Add a label near the "Partner emails Sarah" step: Active: 2m | Wait: 0.
Move to the Office Manager lane. Add a label for "Print and fill engagement letter": Active: 15m | Wait: 0.
Add a label for the "Partner reviews letter" decision point: Active: 30m | Wait: 0.5d. Michael said he spends 30 minutes reviewing, and half the time Sarah has to fix errors and resubmit.
Add a label for "Client signs engagement letter": Active: 5m | Wait: 2-3d. The client only spends minutes signing, but the firm waits days for the return.
Add a label for "Enter client data into 4 systems": Active: 90m | Wait: 0. This is Sarah's biggest time sink per client.

You should now see several time labels in the first half of the diagram. The pattern is becoming visible already.

Continue to the Senior Accountant lane. Add a label for "Sarah emails David": Active: 2m | Wait: 1-2d. David said emails get buried for a day or two.
Add a label for "Request prior-year documents from client": Active: 10m | Wait: 5d. The 5-day average wait is a massive process delay.
Add a label for the "Documents complete?" decision point: Active: 45m | Wait: 3-5d. 30% of the time documents are incomplete, triggering another round-trip.
Add a label for "Send follow-up emails": Active: 15m | Wait: 3d. David spends 3 hours per week total on follow-ups across all clients.
Add a label for the final "Document review" step: Active: 45m | Wait: 0.
Review your diagram and add time labels to any remaining steps that do not have them yet. Every shape in your process should have a corresponding time label.
Press Ctrl+S (Windows) or Cmd+S (macOS) to save your diagram.

Your diagram should now have time labels on every step. Notice how the wait times (measured in days) dwarf the active times (measured in minutes).

Why separate active time from wait time?

Active time is when someone is actually doing work. Wait time is dead time where nothing happens but the clock keeps ticking. Most executives assume their processes are slow because the work itself is complex. The annotations you just added prove that the work is fast. The slowness comes entirely from waiting between steps.

This distinction is the foundation of lean methodology. Automation targets wait time and repetitive active time. It cannot speed up judgment-based work.

Labels overlapping your shapes?

If your text labels are crowding the shapes, try placing them just below or to the right of each shape. You can also reduce the font size by selecting the text label, then changing the font size in the Format panel on the right side to 9 or 10pt.

Still having layout issues?

Apply color-coded waste classification

Time labels show where the delays are. Color coding goes further by classifying the type of waste at each step. This makes it instantly obvious which automation approach would fix each problem.

Use this color system for classifying waste. Each color represents a different category of problem:

Red fill = bottleneck. A step where work piles up or stalls the entire process.
Orange fill = repetitive/manual task. Done frequently, the same way every time, requires no judgment.
Yellow fill = handoff failure. Work gets lost, delayed, or degraded when passing between people.
Blue fill = duplicate data entry. The same information entered into multiple systems.

Select the "Enter client data into 4 systems" shape by clicking on it.
In the Format panel on the right side, click the color swatch next to Fill and choose a blue color. This step is the clearest example of duplicate data entry in the process.
Select the "Wait for documents" step in the Senior Accountant lane. Change its fill to red. This is the biggest bottleneck in the entire process because it stalls everything for 5 days on average.
Select the "Sarah emails David" handoff step. Change its fill to yellow. David told you emails get buried for 1-2 days.
Select the "Partner emails Sarah" step. Change its fill to yellow. This is another handoff failure point where work sits in an inbox.
Select the "Print and fill engagement letter" step. Change its fill to orange. This is a repetitive manual task done the same way every time.
Select the "Send follow-up emails" step. Change its fill to orange. David sends the same types of follow-ups repeatedly with no judgment involved.
Select the "Documents complete?" decision point. Change its fill to red. 30% failure rate here means the process loops back and adds 3-5 more days.

Continue applying colors to any remaining steps that fit the waste categories. You should end up with 8-10 colored shapes total. Steps that remain white are value-adding activities that require human judgment.

Save your diagram.
Step back and look at your diagram. The colored shapes should visually dominate the process. Most of the workflow is now flagged as waste in one form or another.

Why do the colors dominate?

A well-run process should be mostly white shapes with occasional colored exceptions. When 8-10 out of 15-18 steps flag as waste, it means the process was never designed. It evolved organically as people layered workarounds on top of manual procedures.

This visual impact is deliberate. When you present this diagram to a client, the sea of color tells the story before you say a word.

Not sure which color to assign?

Some steps fit multiple categories. Choose the primary problem. If Sarah enters data four times, that is primarily blue (duplicate entry) even though it is also repetitive (orange). If a handoff causes delay AND creates a bottleneck, ask: is the root cause the transfer between people (yellow) or the pile-up of waiting work (red)?

Help me classify my process steps into waste categories.

Calculate the process efficiency ratio

Your diagram now shows where time goes at each step. The final piece is a single number that captures the total waste across the entire process. This is the process efficiency ratio: the percentage of elapsed time spent on work the client actually values.

Before you add this calculation, think about what you expect the number to be. The process takes 12-15 business days from start to finish. How much of that time do you think is genuinely value-adding work that the client perceives?

Click on a blank area below your swimlane pool in the draw.io canvas.
Double-click the blank canvas to create a text box. Type the following summary calculation:

Line 1: Total elapsed time (start to finish): 12-15 business days.
Line 2: Total active work time: ~3.5 hours.
Line 3: Value-added time (work the client actually perceives): ~2 hours.
Line 4: Process efficiency ratio: 2 hours / 96 hours (12 days x 8h) = 2.1%.

Select the text box you just created. In the Format panel, increase the font size to 12 or 14pt so it is clearly readable at a glance.
Save your diagram.

What does 2.1% efficiency mean?

Out of every 100 hours that pass from start to finish in this process, the client receives about 2 hours of value. The remaining 98% is spent waiting in inboxes, re-entering data, chasing documents, and fixing errors.

For service processes, ratios below 5% are actually common. Most executives have never seen their processes quantified this way. This single number gets more executive attention than any other finding in a discovery report.

Why is value-added time less than active work time?

Active work time (~3.5 hours) includes everything someone physically does. Value-added time (~2 hours) counts only the work a client would pay for. Typing the same name into four systems is active but not value-adding. Reviewing documents for completeness adds value. The gap between these two numbers measures internal waste that the client cannot see but still pays for.

Look at your completed diagram one more time. Compare it to how it looked before this step. The clean flowchart that seemed reasonable 20 minutes ago now screams inefficiency. Red, orange, yellow, and blue shapes dominate the process. The time annotations make it impossible to look at this diagram and think things are fine.

Why this reveal matters for consulting

You just experienced the same insight your client will have when you present this diagram. A process map without quantitative annotations hides waste. The annotations and color coding transform a diagram from documentation into a diagnostic tool. This is why professional process discovery always combines visual mapping with time-and-motion data.

Your annotated diagram is now a powerful analytical artifact. Next, you will translate these findings into the client-facing Process Discovery Report that turns insight into action.

Compile the Process Discovery Report

Your annotated diagram now tells the truth about Henderson & Associates' onboarding process. The color-coded waste and the 2.1% efficiency ratio make the problem undeniable.

But the diagram is for your own understanding. The client-facing deliverable is a Process Discovery Report that translates visual findings into business language with prioritized recommendations. This document justifies the next phase of work and proves your value as a consultant.

In this step, get ready to:

Write an Executive Summary with methodology, key findings, and the top recommendation.
Document 5 waste categories with quantified impacts and root cause analysis.
Prioritize automation recommendations and propose next engagement phases.

Write the Executive Summary

The Executive Summary is the only page many decision-makers will read. It must communicate the full story in under one page: what you analyzed, how you analyzed it, what you found, and what to do about it.

Switch back to your Process-Discovery-Report.docx in Microsoft Word.
After the title page, add a new page with the heading Executive Summary.
Write a Process Analyzed paragraph stating: New Client Onboarding at Henderson & Associates CPAs.
Write a Methodology paragraph stating: Stakeholder interviews conducted with 3 roles (Office Manager, Senior Accountant, Managing Partner), followed by current-state workflow mapping with quantitative time analysis.
Write a Key Findings paragraph containing these specific metrics from your analysis:
Write a Top Recommendation sentence: Implement automated client intake with form-to-system integration to eliminate duplicate data entry and reduce onboarding time by 60-70%.
Keep this entire section to one page maximum.

Save Process-Discovery-Report.docx. Your document should now be 2 pages: the title page plus the Executive Summary.

Why one page maximum?

Managing partners like Michael Torres read one page before deciding whether to keep reading. If your Executive Summary runs longer, you are burying the business case in detail the partner will skip.

The dollar figure ($17,000-$25,500 lost per year) is what earns the second page turn. Lead with it.

Not sure what to write?

Pull every number directly from your annotated diagram's summary box and your interview notes. The Executive Summary is not creative writing. It is a structured summary of data you already have.

If your efficiency ratio or time figures differ slightly from the outline numbers, use your own calculations. Consistency within your report matters more than matching exact values.

help me structure my Executive Summary using the data from my interviews and diagram

Build the Findings section with quantified waste categories

The Findings section is where you prove each claim from the Executive Summary. Each category of waste gets its own subsection with a consistent four-part structure that builds an airtight case.

Add a new heading after the Executive Summary: Findings.
For each of the 5 findings below, create a subsection with four labeled parts: Current State (what happens now), Impact (quantified in time and money), Root Cause (why it happens), and Recommended Approach (what type of automation addresses it).

Write Finding 1: Duplicate Data Entry Across 4 Systems.

Current State: Sarah manually enters client name, address, EIN, and entity type into practice management, SharePoint, tax software, and billing system separately.
Impact: 90 minutes per client x 10 clients/month = 15 hours/month. 15% error rate generates approximately 2.5 hours of rework monthly.
Root Cause: No integration between systems. Each application maintains its own client record with no shared data source.
Recommended Approach: Form-to-system integration with auto-population from a single intake form.

Write Finding 2: No Pipeline Visibility.

Current State: Managing Partner has no way to check onboarding status without asking Sarah directly.
Impact: 2-3 client losses per year at $8,500 average client value = $17,000-$25,500 in lost annual revenue.
Root Cause: Process state exists only in individual email inboxes and Sarah's memory. No shared tracking system.
Recommended Approach: Workflow automation with real-time status dashboard accessible to all stakeholders.

Write Finding 3: Manual Document Chasing.

Current State: David sends checklist emails and manually follows up. 60% of clients need reminder emails.
Impact: 3 hours per week spent on follow-up emails. Average 5 business day response time extends the process by a full week.
Root Cause: No automated reminder system. Clients forget or deprioritize email requests without nudges.
Recommended Approach: Automated document request portal with scheduled reminders and status tracking.

Save your document. You should now have the Executive Summary plus 3 completed findings, totaling approximately 3 pages.

Write Finding 4: Paper-Based Engagement Letters.

Current State: Sarah prints a Word template, manually fills client details, partner reviews and signs, then the letter is scanned and emailed for client signature.
Impact: 30 minutes of partner review time per client. 50% returned with errors requiring correction. 2-3 day delay waiting for client signature.
Root Cause: Template is not connected to client data. Manual transcription introduces errors. Physical signature workflow adds days.
Recommended Approach: Auto-populated engagement letter templates with electronic signature integration.

Write Finding 5: Email-Based Handoffs.

Current State: Work transfers between roles via email notifications that get buried in inboxes.
Impact: 1-2 day average delay at each of the 7-9 handoff points. Collectively adds 7-18 days of pure wait time to the process.
Root Cause: Email is asynchronous and competes with hundreds of other messages. No priority signaling or escalation mechanism.
Recommended Approach: Task-based workflow automation with assignment notifications, due dates, and escalation rules.

Save your document. The Findings section should span 2-3 pages with all 5 waste categories documented.

Why this four-part structure for each finding?

The Current State / Impact / Root Cause / Recommended Approach structure does three things at once. It proves you understand what actually happens (not just what should happen). It quantifies the cost so the client cannot dismiss it as subjective. It connects the problem to a solution category without over-prescribing a specific vendor.

This structure is standard across consulting deliverables from firms of all sizes. Clients trust it because each finding stands alone as a defensible argument.

Findings section feeling too long?

Keep each finding to 4-6 sentences total across the four parts. Use bullet points or a table format if paragraphs feel dense. The goal is scanability. A partner should be able to read any single finding in under 30 seconds.

how can I make my Findings section more concise and scannable

Add prioritized recommendations and next steps

The Findings section proves the problems exist. The Recommendations section tells the client exactly where to start. Prioritization by impact and complexity gives them a defensible decision framework.

Add a new heading: Recommendations.
Write Priority 1 (highest time savings, lowest complexity): Form-to-system integration with auto-population. Explain that this eliminates 15 hours/month of duplicate entry and the 15% error rate in one implementation.
Write Priority 2: Automated document request portal with status tracking. Explain that this recovers 3 hours/week of David's time and reduces client response time from 5 days to 2-3 days.
Write Priority 3: Workflow automation with status dashboard. Explain that this eliminates handoff delays, provides partner visibility, and protects $17,000-$25,500 in annual revenue at risk.
Add a final heading: Next Steps. Propose the engagement phases that would follow this discovery:
Save Process-Discovery-Report.docx.

Why propose phases in Next Steps?

Phased recommendations serve two purposes. They reduce the client's perceived risk by breaking a large transformation into manageable pieces. They also create recurring engagement opportunities for you as the consultant.

A client who sees "implement everything at once" hesitates. A client who sees "start with one integration that saves 15 hours/month, then expand" says yes.

Before you check your final page count, predict: how many pages do you think your report is now? Count the title page, Executive Summary, Findings (5 subsections), Recommendations, and Next Steps.

Scroll through your full document from title page to Next Steps.

Your completed report should be 4-6 pages total. It contains specific dollar and time figures throughout. A client partner reading this would understand exactly what is broken, what it costs them, and what to do about it.

Report shorter than 4 pages?

Check that each finding has all four parts filled in (Current State, Impact, Root Cause, Recommended Approach). Thin findings are the most common reason for a short report.

Also verify your Recommendations section explains the benefit of each priority, not just names it. One sentence per priority is too brief for a client deliverable.

help me expand my Process Discovery Report to reach 4-6 pages

You now have a professional consulting deliverable that would hold up in a real client engagement. Your report translates a colorful diagram into a clear action plan backed by hard numbers. Next, you will tackle the Secret Mission and build a scoring matrix that makes your prioritization even more defensible.

Secret mission

Build the Feasibility-Impact Opportunity Matrix

Your prioritized recommendations are strong, but they rely on your judgment alone. What if you could back them with a visible, defensible scoring methodology that any executive could follow? In this extension, you will score each automation opportunity on two dimensions, plot them on a quadrant diagram, and give your client a clear visual answer to the question: where do we start?

Clean Up Your Resources

This project runs entirely locally, so there are no ongoing costs. Decide whether to keep your resources for future engagements, or delete them entirely.

Resources you used:

Local project folder: C:\Projects\henderson-discovery\ containing all interview notes, diagrams, and your final report.
draw.io browser tab at app.diagrams.net (no account created, no stored data on their servers).

Keep everything running

No action needed. Choose this if you plan to reuse your interview guide and report structure for future client engagements.

Your interview guide, diagrams, and report are reusable templates. Copy the folder structure for each new client engagement.
Export your draw.io diagrams as PNG or PDF for inclusion in client presentations.
The report is already in Word format, ready to share or adapt for a real engagement.

Pause - I'll come back to this later

Since all files are local and there are no running processes or cloud resources, there is nothing to pause. Your files will remain on disk exactly as you left them.

Close your draw.io browser tab. Your diagram files are saved locally and can be reopened anytime.
Close Microsoft Word. All documents are saved in your project folder.

Delete - I don't want to use this again

Remove all project files from your machine. This permanently deletes your interview guide, diagrams, and report.

Close any open Word documents and the draw.io browser tab.
Delete the entire project folder. On Windows, open File Explorer, navigate to C:\Projects\henderson-discovery\, right-click it, and select Delete.
Alternatively, open a terminal and run the following command:

rmdir /s /q C:\Projects\henderson-discovery

If you also want to remove the parent folder, delete C:\Projects\ only if it contains no other project files.

Nice Work!

Nice work! You just completed a full process discovery engagement for a realistic consulting scenario. You went from blank documents to a client-ready deliverable that quantifies exactly where time and money are being lost.

You've learned how to:

Design a structured stakeholder interview guide that extracts quantifiable data (time per task, error rates, dollar costs) from multiple personas and turns vague pain descriptions into actionable metrics.
Build a swimlane workflow diagram in draw.io with time annotations and color-coded waste categories that reveals a 12-15 day process contains only 2 hours of value-added work at 2.1% efficiency.
Compile a portfolio-ready Process Discovery Report with an executive summary, quantified findings with root cause analysis, and prioritized automation recommendations backed by dollar figures.
Secret Mission: Built a Feasibility-Impact scoring matrix with defined criteria and plotted opportunities on a visual quadrant diagram to create a defensible implementation sequence.

Ready to quiz yourself?