Martin, K., & Osterling, M. (2026). Value Stream Mapping: How to Visualize Work and Align Leadership for Organizational Transformation. TKMG Press. Further information about the book is available through TKMG Press.
Why This Book Matters
Organizations often believe they have a productivity problem when they actually have a flow problem. Work sits in queues, decisions move unevenly between departments, and employees spend significant amounts of time managing coordination overhead rather than producing meaningful outcomes. In Value Stream Mapping, Karen Martin and Mike Osterling argue that organizations cannot improve performance sustainably until they learn to visualize how work actually travels through the enterprise.
The book emerges from the broader Lean management tradition associated with the Toyota Production System, but Martin and Osterling adapt those principles to administrative and knowledge-work environments rather than manufacturing floors alone. Their central argument is that value stream mapping exposes hidden inefficiencies that organizations gradually normalize through habit and structural fragmentation.
The book succeeds as a practical framework for diagnosing operational friction. At the same time, it leaves important questions unresolved about why organizations continue reproducing inefficient systems even after those inefficiencies become visible. Martin and Osterling provide a strong methodology for identifying breakdowns in flow, but the human and political dimensions of organizational resistance receive less sustained attention.
Summary
The opening chapters introduce the conceptual foundations of value stream mapping, including process time, lead time, and the distinction between value-adding and non-value-adding work. Martin and Osterling argue that organizations often normalize activities that consume resources without delivering customer value (Martin and Osterling, 2014, p. 93).
A recurring theme throughout the book is visibility. The authors consistently emphasize the importance of understanding work in a highly visual way, arguing that visualizing disconnects and redundancies creates organizational clarity that many companies otherwise lack (Martin and Osterling, 2014, p. 109). This emphasis on “seeing the truth” about how work actually flows becomes one of the conceptual anchors of the text (Martin and Osterling, 2014, p. 74).
The middle sections focus on methodology. Martin and Osterling guide readers through the construction of current-state and future-state maps, explaining how organizations can identify delays, excessive approvals, batching behavior, rework loops, and communication failures. Their distinction between process time and lead time is especially important. Process time reflects active work, while lead time includes queue time, interruptions, delays, and waiting between functions (Martin and Osterling, 2014, pp. 92–93).
The book closes by emphasizing leadership alignment and continuous improvement. Martin and Osterling argue that mapping should not become an exercise in excessive data collection, but rather a disciplined method for identifying the few operational barriers that most significantly affect flow and performance.
Analysis
Seeing the Waste Between Activities
One of the book’s strongest contributions is its focus on delays between activities rather than the activities themselves. Martin and Osterling show convincingly that organizations often become highly efficient at managing departmental work while remaining surprisingly ineffective at moving work across the enterprise.
This distinction felt particularly relevant in light of my own experience working on large infrastructure expansion programs. In one environment, engineering teams initially assumed provisioning delays stemmed primarily from technical limitations. Once operational workflows were mapped more fully, the bottlenecks looked different. Procurement approvals remained in queues for days. Security reviews restarted after midstream requirement changes. Escalations multiplied because ownership boundaries were unclear. The technical implementation itself was rarely the slowest component.
Martin and Osterling capture these kinds of dynamics effectively. Their discussion of batching is especially persuasive because they identify batching itself as a “barrier to flow” that office and service organizations often fail to recognize as problematic (Martin and Osterling, 2014, p. 97). Similarly, their analysis of work-in-process accumulation demonstrates how hidden queues emerge from overproduction, batching, poor incoming quality, and conflicting prioritization rules (Martin and Osterling, 2014, p. 99).
The distinction between current-state and future-state mapping is also one of the book’s most useful methodological contributions. The authors argue that current-state mapping enables organizations “to see the truth about how the value stream is performing” before redesigning future processes (Martin and Osterling, 2014, p. 74). That sequencing matters. Too many transformation initiatives attempt to redesign systems before fully understanding operational reality.
Visibility Does Not Always Produce Alignment
At the same time, I found myself questioning one of the book’s underlying assumptions: that organizational visibility naturally creates operational alignment.
Martin and Osterling repeatedly frame inefficiency as a visibility problem. There is substantial truth in that argument. Teams often do not recognize how fragmented their systems have become until they physically map the workflow. Still, awareness alone does not necessarily resolve structural conflict. This broader distinction between local optimization and systems-level coordination connects closely to larger traditions in systems thinking, which emphasize that organizations must be understood as interconnected structures rather than isolated functional units. See Systems Thinking Overview – Society for Organizational Learning.
In practice, organizations frequently understand at least some sources of friction already. The harder issue is that different groups operate under competing incentives. Approval layers may persist because they reinforce authority structures. Reporting complexity may survive because visibility threatens existing managerial control or exposes inconsistent decision-making.
The book acknowledges resistance to change, but usually from a process management perspective rather than a behavioral one. At several points, I wanted deeper engagement with the emotional dimensions of organizational complexity. Some forms of redundancy persist not because leaders misunderstand the process, but because those structures provide institutional or psychological security.
I am somewhat conflicted here, however. Martin and Osterling did not set out to write a study of organizational psychology. Judged strictly as an operational methodology guide, the book largely succeeds. Still, modern transformation efforts rarely separate process redesign cleanly from human behavior.
Lean Thinking in Contemporary Enterprises
I was also less convinced by some of the future-state examples involving healthcare and administrative environments. In several cases, the redesigned workflows appeared more operationally flexible than many highly regulated enterprises actually permit.
The future-state diagrams occasionally imply a cleaner linearity than contemporary digital organizations usually experience. Cloud governance reviews, cybersecurity controls, vendor dependencies, and compliance obligations often create overlapping operational flows rather than the more sequential movement represented in some of the examples.
This may reflect a broader tension within Lean management literature itself. Lean frameworks often assume that redundancy signals inefficiency. In some environments, however, redundancy exists intentionally as part of risk management. The book acknowledges compliance constraints, but not with the same depth it applies to flow optimization.
Even so, Martin and Osterling make an important observation when they note how organizations mistake activity for progress. Teams can become extremely busy managing coordination structures created by the system itself. The book consistently pushes readers to ask whether work is genuinely moving or simply circulating.
Style and Methodology
The prose is clear, direct, and highly teachable. Martin and Osterling avoid excessive jargon, which makes the methodology accessible to readers without deep prior exposure to Lean systems thinking. The diagrams and workshop structures are especially effective pedagogically.
At times, the text becomes somewhat repetitive. Similar examples of delays, approvals, and batching appear across multiple chapters. Readers already familiar with Lean operational principles may find parts of the instructional material overly procedural.
Still, the book’s practicality remains one of its greatest strengths. Many management texts discuss transformation abstractly without offering usable operational tools. Martin and Osterling provide readers with methods that can be tested immediately inside their own organizations.
Conclusion
Value Stream Mapping remains a valuable operational text because it teaches leaders to examine movement rather than appearances. Martin and Osterling demonstrate convincingly that organizations often struggle not because employees are unwilling to work hard, but because systems themselves interrupt flow through delays, fragmented ownership structures, and poorly coordinated decision-making.
The book is particularly relevant for operations leaders, program managers, transformation consultants, and technology executives responsible for coordinating work across multiple functions. Readers seeking a deeply theoretical treatment of organizational behavior may find the analysis limited, but practitioners will likely appreciate the clarity and usability of the framework.
Its lasting contribution lies in the discipline of learning to see operational friction before attempting to solve it. In increasingly digitized organizations where complexity expands faster than institutional coordination, that discipline remains highly relevant.
