Branching Within Process: Flowcharts for Decision Points and Process Mapping
PMBOK v8 Definition
Flowcharts are visual representations that map out the sequence of steps and branching possibilities within a process. They are also known as process maps and are used to transform one or more inputs into one or more outputs. Flowcharts are instrumental in illustrating the activities, decision points, branching loops, parallel paths, and overall order of processing within a horizontal value chain.
This concept is a Tool and Technique used across multiple processes, particularly within Planning Process Group and Monitoring and Controlling Process Group.
Why It Matters for the Exam
The PMI exam frequently tests flowcharts as a data representation technique for quality management, risk management, and process improvement. Questions often focus on distinguishing flowcharts from other diagrams (like cause-and-effect diagrams) and understanding how branching logic helps identify process inefficiencies, decision points, and potential risks. Expect situational questions where you must select the correct diagram for mapping process steps with decision branches.
Key Points to Remember (for the exam)
- Primary Purpose: Illustrates the sequence of steps, decision points, branching loops, parallel paths, and overall processing order
- Key Tool for: Quality management (process improvement), risk identification, and process analysis
- Common Name: Also called process maps
- Core Function: Transforms one or more inputs into one or more outputs
- Branching Logic: Shows what happens when decisions are made (yes/no paths, alternative routes)
- External Funding Application: When seeking external funds, flowcharts help map funding requirements and decision points
- Horizontal Value Chain: Flowcharts show processing across the entire value chain, not just isolated steps
Typical PMI Exam Example
A project manager is analyzing the approval process for change requests. The team needs to visualize where decisions are made, what happens when a change is approved versus rejected, and how rework loops back into the process. Which tool should the project manager use?
Answer: Flowchart (process map)—because it maps decision points, branching possibilities, and parallel paths within the approval sequence.
PMI Exam Traps
-
Trap: Confusing flowcharts with cause-and-effect diagrams (fishbone/Ishikawa)
- Reality: Flowcharts map process steps and decisions; cause-and-effect diagrams trace an effect back to root causes
-
Trap: Thinking flowcharts only show linear sequences
- Reality: Flowcharts explicitly show branching loops, parallel paths, and decision points—not just straight-line sequences
-
Trap: Assuming flowcharts are only for quality management
- Reality: Flowcharts apply across multiple knowledge areas, including risk management (identifying risk triggers) and scope management (mapping requirements)
-
Trap: Confusing flowcharts with burn charts or cumulative flow diagrams
- Reality: Burn charts track work completed over time; cumulative flow diagrams show work in different states; flowcharts map process logic and decisions
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Cause-and-Effect Diagram | Complementary tool | Flowcharts show process steps; cause-and-effect diagrams show root causes of problems |
| Process Analysis | Application area | Flowcharts are used to identify inefficiencies, bottlenecks, and unnecessary steps |
| Risk Identification | Input to process | Flowcharts help identify risk triggers at decision points and branching paths |
| External Funding Requirements | Specific use case | When funding is external, flowcharts map funding entity requirements and compliance steps |
Quick Review Questions
-
A project team wants to visualize all possible decision points and rework loops in their quality control process. Which diagram type should they use?
-
During a risk identification workshop, the team needs to understand where risks might occur based on process decisions. What tool helps map these branching possibilities?
-
What is the difference between a flowchart and a cause-and-effect diagram in terms of what they illustrate?
-
A project is funded externally, and the funding entity has specific requirements. Which tool helps map these requirements into the project process?
-
Flowcharts are known by what alternative name in PMBOK v8?
PMBOK v8 Reference
Section 5.2 - Collect Requirements (Data Representation: Flowcharts) Section 8.2 - Manage Quality (Data Representation: Flowcharts) Section 11.2 - Identify Risks (Data Representation: Flowcharts)
Note: Flowcharts appear as a data representation technique in multiple PMBOK v8 sections. The specific content about external funding and branching within processes is addressed in the context of project funding requirements and process mapping.