What doesn't a Value Stream Map do?

Based on the principles of the PeopleCert DevOps Leader certification, here is the analysis of the question.

As the multiple-choice options were not provided, this answer assumes a standard set of options commonly associated with this topic in an exam context.

Assumed Options:
A. Identify waste in a process
B. Visualize the flow of work and information
C. Calculate process cycle efficiency
D. Define the organizational reporting structure

Correct Answer: D

A Value Stream Map (VSM) does not define the organizational reporting structure.

Explanation

A Value Stream Map is a fundamental Lean tool used to analyze and improve the flow of value to a customer. Its primary purpose is to visualize all the steps—both value-adding and non-value-adding—in a specific process, from request to delivery. This visualization helps teams identify sources of waste (muda), calculate key performance metrics like lead time and process cycle efficiency, and design a more streamlined future state. A VSM is process-centric, focusing on how work flows across teams and departments. It is distinct from an organizational chart, which is a human-resources tool designed specifically to depict formal hierarchical reporting lines and departmental structures.

Why Incorrect Options are Wrong

A. Identify waste in a process: This is a primary function of VSM. It visually exposes delays, rework, handoffs, and other forms of waste.

B. Visualize the flow of work and information: This is the core definition of a VSM; it maps the end-to-end flow of both the work item and the information required to process it.

C. Calculate process cycle efficiency: VSM captures the necessary data—Value-Added Time and Total Lead Time—to calculate this critical Lean metric.

References

1. Rother, M., & Shook, J. (2003). Learning to See: Value Stream Mapping to Add Value and Eliminate Muda. Lean Enterprise Institute.
Reference: Page 3 defines a value stream as "all the actions (both value added and non-value added) currently required to bring a product through the main flows essential to every product." The book's methodology focuses exclusively on mapping process steps, information flows, and timelines, not organizational hierarchies.

2. Kim, G., Humble, J., Debois, P., & Willis, J. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations. IT Revolution Press.
Reference: Chapter 8, "The Second Way: Amplify Feedback Loops," describes value stream mapping as a critical tool to "make the flow of work visible" and to "see where work is flowing well and where it is queued or stalled." The focus is entirely on the process flow, not the reporting structure.

3. Martin, K., & Osterling, M. (2014). Value Stream Mapping: How to Visualize Work and Align Leadership for Organizational Transformation. McGraw-Hill.
Reference: Chapter 1, "What is Value Stream Mapping?", explicitly states, "Value stream mapping is a method of visualizing the flow of a product or service from the time an order is placed... until the product or service is in the hands of the customer." It contrasts this with other tools, implicitly separating it from organizational charting.

4. MIT OpenCourseWare. (2005). 16.852J / ESD.62J Integrating the Lean Enterprise, Fall 2005. Massachusetts Institute of Technology.
Reference: Lecture 5 notes on "Value Stream Mapping" detail the symbols and metrics used, such as process boxes, inventory triangles, and data boxes for cycle time and lead time. The entire framework is designed to analyze process flow and efficiency, with no elements for representing managerial reporting lines.

A – Mapping explicitly visualises each material/information hand-off in the end-to-end flow. B – A core purpose of VSM is to surface bottlenecks and the seven Lean wastes. C – Lead time, process time, inventory counts, etc., are captured on every VSM as baseline metrics.

1. Singh, B., Sharma, S.K., and Sharma, R. “Value Stream Mapping: Literature Review and Implications for Research.” International Journal of Production Research 49(18), 2011, pp. 5531-5553. DOI:10.1080/00207543.2011.596351 – Sec. 3, para 2 (“VSM is a diagnostic tool… it cannot by itself remove waste”).

2. Krafcik, J.F., and Shook, J. “MIT Lean Aerospace Initiative – Lean Enterprise Model.” MIT OCW Course 16.852J (2009), Module 4, slide 27 (“VSM highlights waste; improvement comes from subsequent Kaizen”).

3. Rother, M., and Shook, J. Learning to See. Lean Enterprise Institute, 3rd ed., 2009, pp. 6-7 (“The map only makes problems visible; action is required to eliminate them”).

4. Humble, J., Kim, G., and Walls, J. DevOps Handbook. IT Revolution, 2016, Ch. 2, p. 35 (“Use VSM to see work flow and queue times; the map does not change the system”).