Key Takeaways
A 28-day process can hide only 20 minutes of value creation
The time gap is startling. In a funding-document process, the average lead time was 28 days. During one pilot, the shortest measured run of value-creating work took 20 minutes. Treating all 20 minutes as valuable work, the author estimates that it represented about 0.15% of 28 days. This is an illustration, not a complete time study of every transaction. The team redesigned the process, reducing average lead time to four days.
Find the waiting. The gap points to a practical question: where does an item sit, move, or get rechecked instead of being transformed for the customer? Mapping makes those hidden intervals visible, so an improvement effort can target the causes of delay rather than simply pressuring employees to work faster.
The contrast turns an abstract efficiency problem into a question about time allocation. In operations research, waiting time can dominate a system even when each task is short, especially when work arrives unevenly or must pass through constrained queues. The 20-minute estimate should not be mistaken for proof that every idle minute is removable: regulation, demand variation, and necessary verification can all matter. Its real value is diagnostic. It prompts teams to distinguish necessary safeguards from inherited delay, and to test whether each interval protects the customer or merely reflects how the organization happens to be arranged.
Map the same work at organization, workflow, and activity levels
Three views reveal different facts. A relationship map shows organizational parts and the inputs and outputs exchanged between them, but not the activities inside each part. A cross-functional process map, also called a swimlane diagram, shows activities in the lanes of the teams or roles responsible for them. A flowchart zooms in on one activity and can distinguish value-creating work from delays, movement, decisions, and other nonvalue-creating steps.
Phil’s Quick Lube makes this concrete. Its relationship map shows Sales, Service, and Administration and how they connect during an oil change. The swimlane map shows who greets the customer, changes the oil, and collects payment. A flowchart of writing the service order reveals decisions and walking hidden by the broader view.
The three-map approach is a form of scale-aware analysis: organizational structure, cross-boundary workflow, and local task detail answer different questions. A single diagram cannot carry all three levels without becoming difficult to read. The risk is treating the views as competing truths. A department can look efficient on its own while slowing the end-to-end path, and a detailed task map can expose motion without explaining why the task exists. The maps are most useful as a connected set, with each view chosen to test a particular explanation of how work gets done.
Start with the customer's finished item, not the tasks employees recognize
Work backward from the result. The book’s outside-in method begins by identifying a specific, countable item that exits the process, who receives it, what that customer values, and how demand arrives. Only then does the team trace the item’s path upstream. This prevents the familiar activities employees perform from becoming the assumed purpose of the process.
The funding form was not the whole answer. The team initially treated the funding document itself as the output. Looking at the customers clarified that the useful results were notifications: one told a headquarters project leader that funding was in place, and another told a field leader that work could begin. Customers valued turnaround time, and their desired turnaround helped shape the improvement target.
Beginning with an outcome is a strong defense against local optimization. Employees naturally know their own tasks best, but a task is valuable only in relation to the result it helps produce. The case also shows why the word customer needs care: a process may serve more than one recipient, including internal customers whose needs affect the external service. Customer preference should guide design, but it does not automatically settle every tradeoff. Reliability, legal duties, and the needs of other stakeholders may constrain what a faster process can responsibly promise.
Inspect every handoff for queues, missing information, and unclear ownership
A handoff is a vulnerable interface. When work passes from one role or organizational part to another, the receiving person needs the right information, access to relevant systems, and a clear signal to act. In knowledge work, an email or document may wait in an inbox among unrelated requests. The next person may lack needed data, have different priorities, or be unsure what counts as complete.
Serial workflows multiply the exposure. The funding-document process involved many roles and at least 12 handoffs, along with repeated reviews and approvals. The team found queues at handoffs and unclear criteria for review. Mapping the connections exposed where the work paused, where information was incomplete, and where responsibility changed hands without a shared understanding of requirements.
Handoffs resemble interfaces in software and engineering: a system can fail not because any one component is incapable, but because the contract between components is vague. That makes explicit input requirements and completion criteria powerful design tools. Still, a handoff is not inherently wasteful. Specialized knowledge, independent verification, and regulated authority can make separation necessary. The useful question is whether each transfer has a defined purpose and reliable conditions, not whether every boundary can be eliminated. Reducing unnecessary transfers while strengthening essential ones is a more credible aim than pursuing zero handoffs.
Measure elapsed time, value time, and accuracy, not activity counts alone
Measure the customer’s experience of flow. Lead time is elapsed time from the start of a defined process to its finished item. Cycle time is the time spent on an individual activity. Value-creating time records work that transforms a resource in a way the customer values. Complete and Accurate measures whether a handoff contains all required information and whether it is correct. Together, these measures show speed, work content, and quality.
Build measurement into the work. The funding-document team lacked a baseline, so it estimated the 28-day average by examining recently completed cases and reconstructing dates from records and emails. The book recommends collecting only data that people use to manage or improve the work, preferably as part of daily operations, rather than creating a separate reporting burden.
The measures prevent a common management error: treating more completed tasks as evidence of better service. A process can move quickly while producing errors, or appear productive while items accumulate between steps. Combining time and accuracy measures makes those tradeoffs harder to ignore. The caution is that metrics can distort behavior when they become targets detached from judgment. A low lead time is meaningful only if the delivered item is correct and the measure reflects actual customer demand. Measurement should illuminate the work, not become another queue of forms and approvals.
Choose the map that answers your question, then stop mapping
A map is a selective model. It highlights chosen boundaries, activities, connections, or work properties; it cannot show everything about the work or guarantee that its picture matches current conditions. A relationship map suits questions about organizational parts and their supplier-customer links. A swimlane map suits questions about end-to-end workflow and handoffs. A flowchart suits close examination of one activity and its waste.
Use evidence beyond the diagram. The book recommends combining methods such as interviews, document review, group facilitation, and direct observation. At Phil’s Quick Lube, observation added waiting areas and vehicle movements that an interview-based map had missed. The purpose is understanding sufficient to act, not a perfectly polished diagram. If the goal is step-by-step instruction, procedures or job aids may be a better tool.
This is a practical lesson in model discipline. A diagram is useful precisely because it leaves things out, but those omissions need to be deliberate and visible. A group-created map can align language and expose different assumptions; observation can then challenge the group's recollection with the work as performed. Neither source is infallible. People may adapt their behavior while observed, and a map can make a contested interpretation look settled. Treating the diagram as a hypothesis to verify keeps it from becoming a decorative substitute for inquiry.
Find waste in the system around work, not just in workers
Waste is work that consumes resources without creating customer value. The book identifies overproduction, inventory, waiting, extra processing, correction, excess motion, and transportation. In office work, examples include documents waiting in inboxes, repeated data entry, unnecessary approvals, rework, and searching or walking for information and equipment.
Look at conditions, not character. Barriers to flow can arise from workflow design, information systems, measurement and motivation, staffing, policies, or facilities. The funding-document team found problems across several of these areas, including role-based access to information, unclear review criteria, scattered work, and physical separation. The useful investigation asks how resources are deployed, how work operates, and how components connect, rather than labeling an individual as the cause of a slow process.
The system-level framing shifts attention from blame to design, where remedies can be tested and shared. It also fits knowledge work, where a delay may be produced by access rules, incompatible databases, or competing assignments rather than a worker’s effort. Yet defining value is not purely technical. Customers may not see the benefit of a control that protects privacy or prevents a costly error, while the organization still has a duty to preserve it. A sound analysis distinguishes customer-visible value from necessary risk management instead of classifying every non-transforming step as disposable.
Replace serial reviews with coordinated work when tasks are independent
Redesign the sequence, not just its speed. The funding-document process routed work serially through reviews and approvals. The team found that much of the decision work could be done collaboratively by four functional roles at the same time, rather than passed from one role to another. The revised approach brought participants together to make the decision using shared criteria and information.
The reported results were substantial. Average lead time fell from 28 days to four. Functional touchpoint roles dropped from 12 to eight, queues from 16 to five, and review or approval steps from more than 12 to three. The initial deployment covered two of 40 program offices; the book reports that all 40 were using the revised workflow several years later.
The change illustrates a key design choice: coordination can replace sequential processing when work elements are independent and the decision benefits from simultaneous expertise. It also shows that eliminating repeated review is different from removing accountability; the team retained the required comptroller authority while changing how other work was arranged. Synchronous collaboration has costs, including scheduling and meeting overhead, and may not suit every transaction. The design is most persuasive where the work is sufficiently bounded, the right participants can prepare, and the shared decision criteria are explicit.
Make ownership, timing, and status visible across the whole workflow
Flow needs an accountable owner. The book argues for responsibility spanning the entire process, not only the separate departments that contribute to it. Resources and work should be arranged around the end-to-end path and the customer’s pattern of demand. Visual management makes status, progress, problems, and performance visible to the people doing the work, so they can distinguish normal operation from a problem that needs attention.
The redesigned funding process made coordination tangible. The team used a dedicated room, scheduled time with customers, shared checklists and decision criteria, and provided the systems and equipment needed for the work. These arrangements helped participants see and complete the decision together. Visual information is most useful when it supports immediate action, not merely when it makes a dashboard look complete.
Ownership and visibility address two different coordination failures. A process owner can resolve conflicts between local priorities, while visible status reduces the effort required to discover where an item is stuck. Together they make the workflow governable as a whole. But visibility can become surveillance if measures are used to rank individuals rather than expose system conditions. The healthier design makes exceptions legible, assigns a response, and gives the work group authority to act. A board that reports delay without enabling a fix merely displays the problem more clearly.
Analysis
The book’s central move is to shift attention from isolated tasks and departments to the path an item follows as it becomes something a customer can use. Its maps are not merely documentation formats. Each is a lens with a different unit of analysis: organizational relationships, cross-functional workflow, or the detailed activity. Used together, they help teams ask whether the structure of the organization supports the work its customers actually receive.
The method is strongest when it joins representation to observation. A map assembled from memory can reproduce the organization’s official story, while watching work exposes queues, workarounds, and movement that participants may consider too ordinary to mention. Group mapping also has a social function: it gives people from separate roles a shared object to inspect, making disagreement about boundaries and responsibilities discussable. That shared picture is an improvement in understanding, even before it produces a faster process.
The funding-document case gives the principles practical force. The team did not merely push employees to clear a 28-day backlog faster. It changed the arrangement of decision work, bringing relevant expertise together and reducing repeated checks. The reported decline to four days, followed by use in all 40 program offices, suggests that the change was operationally adoptable, not just an attractive workshop design. The source, however, offers one anonymized case rather than a controlled comparison, so it cannot establish that the same redesign will work unchanged in every setting.
The strongest general lesson is therefore not that every process should be accelerated or every handoff removed. It is that process performance emerges from the fit among work, resources, information, authority, and demand. The maps help make that fit inspectable. Their value depends on asking a precise question, checking the representation against actual work, protecting necessary controls, and measuring outcomes that matter to the people receiving the result.
Review Summary
The Basics of Process Mapping received mixed reviews, with an average rating of 3.54 out of 5. Some readers found it too basic and short, likening it to a pamphlet. Others appreciated it as a good primer for beginners. Positive reviews praised its usefulness as an introduction to process mapping, while negative reviews criticized its lack of depth and editorial mistakes. Several readers noted its brevity, with some finding it sufficient for a quick overview and others expecting more comprehensive content.
People Also Read
Glossary
Relationship map
Organization connection viewA diagram showing selected parts of an organization and the supplier-customer relationships among them. It highlights the inputs and outputs that connect those parts, often in an overall supplier, organization, customer sequence. It does not show the work activities performed inside each part.
Cross-functional process map
End-to-end workflow viewA diagram of a process in which activities are placed in horizontal lanes representing the roles, departments, systems, or other entities responsible for them. It shows the sequence of work, inputs and outputs, customer connections, and handoffs across organizational boundaries.
Flowchart
Detailed activity sequenceA graphic representation of the activities used to produce one specific output. It can show value-creating work alongside delays, storage, movement, decisions, inspection, and other forms of nonvalue-creating work. In this book, it provides the most detailed view of work.
Workflow
Architecture of an item's pathThe architecture and actual path through which a work item moves from an initial resource input, through a sequence of interrelated activities and resources, to a specific result. The term emphasizes how work is arranged and connected, not merely the list of tasks or the movement of an item.
Flow
Transformation into a valued itemThe work property describing how a resource input is transformed into a customer-valued item through value-creating activities. Movement alone does not create value. The ideal described in the book is continuous work with no delays, defects, waste, or work-in-process inventory.
Natural work group
People who perform connected workThe individuals who directly perform a process and communicate with one another to get that work done, even when they are located in different places. Mapping with this group can build shared understanding and ownership, because participants collectively describe how the work actually proceeds.
Value-creating time (VCT)
Time spent creating customer valueThe elapsed time used to transform a resource in a way that customers value. It differs from total lead time, which includes value-creating work as well as waiting, movement, and other nonvalue-creating time. Comparing VCT with lead time helps reveal how much of a process is spent producing its result.
Complete and Accurate (%C&A)
Correct, sufficient handoff measureA measure of whether information passed from a supplier to a receiving person or group contains everything needed and is correct. It is useful for assessing the quality of handoffs, where missing or inaccurate inputs can trigger delays, clarification, or rework.
Countermeasure
Action addressing a flow barrierA specific adjustment chosen to address a barrier to flow. Since several work components may interact to create a delay, countermeasures may need to be designed as a coordinated set. They can be introduced in stages, with practical time horizons, rather than treated as one final redesign.
Seven principles to improve flow
Framework for improving knowledge workA set of principles for improving knowledge-work processes: begin with customer needs, measure what matters, make end-to-end work visible, identify and remove barriers, connect value-creating activities, organize around the whole flow, and manage the work visually. The principles link process mapping to measurement, redesign, ownership, and daily management.
0.05 to 5 Rule
Estimate of value-time shareA rule of thumb attributed in the book to Boston Consulting Group work from 1990. It states that value-creating time may represent only 0.05% to 5% of the time a product or service spends in a value-delivery system. It signals a potential for delay reduction, but is not a substitute for measuring a specific process.
FAQ
What's "The Basics of Process Mapping" by Robert Damelio about?
- Introduction to Process Mapping: The book provides a comprehensive introduction to process maps, including relationship maps, cross-functional process maps (swimlane diagrams), and flowcharts.
- Purpose and Application: It explains how these maps can be used to provide different views of work, assess processes, and improve them.
- Updated Content: The second edition includes new chapters and graphics, reflecting recent developments in process mapping.
- Case Study: A detailed case study is included to demonstrate how one organization applied the principles to significantly reduce lead time.
Why should I read "The Basics of Process Mapping"?
- Practical Guidance: The book offers practical, how-to guidance for creating and using process maps effectively.
- Comprehensive Coverage: It covers various mapping conventions and includes analytics to assess and improve processes.
- Skill Development: It is suitable for both novices and practitioners, helping them develop a well-rounded understanding of process mapping.
- Real-World Application: The inclusion of a case study provides insights into real-world application and benefits of process mapping.
What are the key takeaways of "The Basics of Process Mapping"?
- Different Views of Work: Understanding how relationship maps, swimlane diagrams, and flowcharts provide different perspectives on work processes.
- Flow and Waste Concepts: Introduction to the concepts of flow and waste, and their appearance in knowledge work or business processes.
- Improvement Principles: Seven principles and 29 guidelines for improving the flow of knowledge work are detailed.
- Case Study Insights: Learning from a case study where principles and guidelines were applied to reduce lead time from 28 days to 4 days.
What are the best quotes from "The Basics of Process Mapping" and what do they mean?
- "A great how-to for novices and excellent reference for practitioners": This quote highlights the book's utility for both beginners and experienced professionals in process mapping.
- "Raises the bar on what constitutes the basics": Indicates that the book provides a more advanced understanding of process mapping fundamentals.
- "Make work visible at the organization, process, and job/performer levels": Emphasizes the book's focus on making work processes transparent and understandable at various organizational levels.
What is a relationship map according to "The Basics of Process Mapping"?
- Visual Depiction: A relationship map visually depicts the parts of an organization and the internal or external supplier-customer relationships among those parts.
- Resource Conversion Sequence: It follows a general left-to-right sequence represented by suppliers, the organization, and customers.
- Organizational View: The map helps view work at the organization level, showing input/output connections but not explicit work activities.
- Contextual Understanding: It provides context for understanding how different parts of an organization contribute to the overall workflow.
How does "The Basics of Process Mapping" define a cross-functional process map or swimlane diagram?
- Workflow Illustration: A cross-functional process map illustrates workflow in organizations, showing a set and series of interrelated work activities.
- Swimlane Pattern: It is also called a swimlane diagram because of the horizontal bands that resemble swimming lanes, representing different entities.
- Work and Location: The map shows both the work and where in the organization that work takes place, highlighting supplier-customer relationships.
- Organizational Handoffs: It identifies organizational handoffs and patterns in the workflow, such as serial, collaborative, or parallel.
What is a flowchart according to "The Basics of Process Mapping"?
- Graphic Representation: A flowchart is a graphic representation of the sequence of activities used to create, produce, or provide a specific, unique output.
- Value and Waste: It distinguishes between value-creating and nonvalue-creating activities, making types of waste visible.
- Detailed View: Of the three maps, the flowchart represents the most granular view of work, focusing on individual activities.
- Symbols and Conventions: The book details various symbols used in flowcharts to represent different types of activities and decisions.
What are the seven principles to improve flow in "The Basics of Process Mapping"?
- Outside-In Improvement: Start by identifying the item or work product that exits the workflow and what the customer values about it.
- Measure What Matters: Use measures related to the flow of the item and incorporate them into daily work.
- Visibility of Flow: Make the end-to-end flow visible to understand the workflow architecture and item path.
- Remove Barriers: Identify and remove barriers to flow by assessing workflow components and their interactions.
- Connect Work Fragments: Align value-creating work activities to optimize flow and resource utilization.
- Organize Around Flow: Deploy resources to optimize flow with respect to customer demand.
- Visual Management: Manage the flow visually to provide real-time information on status, progress, and performance.
How does "The Basics of Process Mapping" address the concept of waste?
- Definition of Waste: Waste is any activity that consumes resources but does not create or add value.
- Types of Waste: The book identifies types of waste common in knowledge-intensive work, such as overproduction, waiting, and excess motion.
- Impact on Flow: Waste increases lead time and hinders flow, making it a critical focus for process improvement.
- Identification and Removal: The book provides guidelines for identifying waste and implementing countermeasures to remove it.
What is the significance of handoffs in knowledge work according to "The Basics of Process Mapping"?
- Supplier-Customer Relationship: Every handoff is a supplier-customer relationship, usually between different roles.
- Components Involved: Handoffs typically involve information inputs, IT systems, and the knowledge worker.
- Barriers to Flow: Problematic features in these components can act as barriers to flow, causing delays and inefficiencies.
- Focus for Improvement: Understanding and improving handoffs is crucial for optimizing flow in knowledge work processes.
How does "The Basics of Process Mapping" suggest measuring flow?
- Lead Time: Lead time is a key measure of flow, representing the elapsed time from input to item.
- Value-Creating Time: The book emphasizes measuring value-creating time as a percentage of lead time to identify waste.
- Real-Time Indicators: Flow-centric measurement data should be used as real-time performance indicators.
- Customer-Centric Measures: Measures should relate directly to what the customer values about the item or work product.
What case study is included in "The Basics of Process Mapping" and what are its key lessons?
- Funding Document Process: The case study focuses on improving the funding document process in a large DoD organization.
- Lead Time Reduction: The organization applied the book's principles to reduce lead time from an average of 28 days to 4 days.
- Application of Principles: The case study illustrates the application of the seven principles and associated guidelines.
- Real-World Insights: It provides insights into the challenges and successes of implementing process improvements in a complex organization.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.