Diagrams
Diagrams for communicating how things work and how things can be done better.
| Name | Purpose |
|---|---|
| Abstraction Laddering | |
| Affinity Diagram | |
| Business Model Canvas | |
| Capability Map | Assess your team's capabilities and identify areas for improvement |
| Conflict Resolution Diagram | |
| Dependency Map | Identify external factors affecting the ability to deliver value |
| Design Map | |
| Empathy Map | |
| Flowchart | |
| Inversion | |
| Ishikawa | |
| Issue Trees | |
| Process Map | |
| Process and Instrument Diagram | |
| Productive Thinking Model | |
| Outcome Map | Clarify and align your team on desired outcomes and contributing factor |
| UML Diagram | |
| Value Stream Map | Visualize and measure the flow of work through the delivery process |
See Drawing Tools
Capturing Flow of Value
How to use diagrams for mapping the flow of value through your systems.
- Start with the Outcome Map to align on goals.
- Create Value Stream Maps to visualize current, ideal, and target states.
- Develop a Dependency Map to identify external constraints.
- Build a Capability Map to assess internal strengths and weaknesses.
- Use insights from all maps to create a Journey Roadmap.
- Monitor progress using the DORA metrics.
Best Practices
- Involve representatives from all parts of the value stream in mapping exercises.
- Use collaborative tools for remote-friendly mapping sessions.
- Focus on relative measurements initially; precise data can come later.
- Prioritize improvements based on impact and effort.
- Communicate findings and plans visually to all stakeholders.
- Celebrate quick wins to build momentum.
- Be prepared to iterate and adjust as you learn.
Outcome Map
Clarify and align the team on the desired outcome and contributing factors.
- Desired outcome
- Contributing factors
- Obstacles
- Investigations
- Measures (to be defined later)
- Optional: Indicators, Impacts, Roles, Methods
Benefits:
- Creates alignment and shared understanding
- Helps identify potential challenges early
- Sets the foundation for subsequent mapping exercises
Value Stream Maps
Visualize and measure the flow of work through the software delivery process.
- Types:
- Current State Map
- Ideal State Map
- Target State Map (3-6 months out)
- Key components:
- Activities in the workflow
- Wait times between activities
- Process time for each activity
- Quality metrics (e.g., defect rates)
- Value-added vs. non-value-added activities
- Benefits:
- Identifies bottlenecks and waste in the process
- Provides data for prioritizing improvement efforts
- Helps visualize the gap between current and ideal states
Dependency Map
Purpose: To identify external factors affecting the team's ability to deliver value.
Key components:
- Shared services
- Meetings
- SLAs
- Approvals
- Other external obligations
Benefits:
- Highlights areas where the team lacks autonomy
- Identifies opportunities to break or mitigate dependencies
- Provides context for capability building needs
Capability Map
Purpose: To assess the team's internal capabilities and identify areas for improvement.
Key components:
- Critical capabilities required for success
- Skill levels
- Training needs
- Resource availability
- Comfort levels with different tasks
Benefits:
- Identifies skill gaps and training needs
- Helps prioritize capability building efforts
- Supports decisions on internalizing dependencies
Diagram Library
Create matrices to mind the gaps and diagrams to follow the flow of value.