The Decision Point step marks a place in the workflow where the process splits into two or more different paths based on a condition or question. Each path, called a branch, continues independently from that point.
WHEN TO USE IT
Use Decision Point when:
- The next steps depend on whether something is approved or rejected
- Different client types get routed to different processes
- Work is either accepted or sent back for revision
- The outcome of a check determines what happens next
Examples:
- "Are designs approved?" branches to Yes (post to social media) and No (send back with feedback)
- "Is this a new or returning client?" branches to two different onboarding paths
- "Did the client respond within 48 hours?" branches to Follow Up Sequence and Close Lead
FIELDS
Title
Frame it as a question: "Are Designs Approved?", "Is Budget Authorised?", "Did Client Sign the Contract?"
Decision Criteria
What information or conditions determine which branch is taken? What does the person or system look at to make the decision?
Decision Maker
Choose whether a human or a technology makes the decision. Human decisions involve judgement. Technology decisions are rule-based (if X then Y).
Branches
Add a label for each branch. Keep labels short and clear: "Yes / No", "Approved / Rejected", "New Client / Returning Client". You can add more than two branches if the decision has multiple outcomes (e.g. "Approve", "Reject", "Request Changes").
External Resource Link
Link to any criteria document, policy, or reference that governs how this decision is made.
ADDING STEPS TO A BRANCH
After adding a Decision Point, each branch extends downward from the decision card. Click the + button below each branch label to add steps to that path. Each branch is built independently, and each branch must end with an End Process step.
BRANCHES CANNOT MERGE BACK TOGETHER
Currently, branches in WorkflowMaps cannot converge back into a single shared path. If your workflow splits at a Decision Point and then reconverges (for example, both the approval and rejection paths eventually lead back to the same final step), you have two options:
1. Duplicate the shared steps on each branch. This works well when the shared section is short.
2. Map the converging section as a separate workflow map and reference it via an external link.
WHEN TO USE A SEPARATE MAP INSTEAD
If a branch becomes so large that it is essentially a complete workflow in its own right, consider mapping it as a separate map. You can link to it from the branch using the external resource link field on the first step of that branch. This keeps individual maps manageable and readable.
DECISION POINTS DURING DISCOVERY SESSIONS
Decision Points are one of the most useful moments in a discovery session because they reveal paths clients have never fully mapped. After adding a decision, ask: "What happens if the answer is no?" Many clients have a clear process for the positive path and no real process for the negative one. That gap is a finding in itself and often leads to a project recommendation.