The purpose of **Dependency Mapping** is to dig deeper into areas of the value stream that appear to be constraints in order to build clarity on the process and metrics of that part of the stream. Dependency maps are expanded versions of [outcome maps](Outcome%20Map.md). Dependency mapping challenges our assumptions about where problems lie by digging deeper into likely hot spots. ## Dependency mapping steps  1. Start with constraints. 2. Zoom in on a constraint by creating a sub-Value Stream Map. 3. Identify hot spots. 4. Identify direct causes for hot spots. 5. Dig deeper into the constraint. Ref: https://itrevolution.com/articles/the-five-maps-of-flow-engineering/#nav-4