💬 Modeling Decisions in Processes with ValueStreamer
This article explains how to effectively model decision logic (e.g., Yes/No branches) in a phase-based system like ValueStreamer, despite its linear structure.
🔍 Contents
- Background: Decision logic vs. linear structure
- Decision as a task card
- Implementation on the board
- Alternative paths with swimlanes
- Tips & Best Practices
- FAQ
📖 Background: Decision logic vs. linear structure
Traditional process models (e.g., BPMN) represent decisions as branching flows. ValueStreamer, however, uses a linear Kanban-style system with phases. Nevertheless, decision logic can be integrated in a structured way.
🧩 Decision as a task card
-
Model decisions as separate task cards in the appropriate phase (e.g., "PSM Review").
-
Use a clear title, such as "Execution known?"
-
In the task description, document the decision options:
-
✅ Yes → Follow-up task: "Create calculation"
-
❌ No → Follow-up task: "Check feasibility (PED)"
-
📋 Implementation on the process board
-
After making a decision, the appropriate follow-up task is created or assigned manually.
-
Use task labels or categories to visually indicate the chosen decision path.
🔀 Alternative paths with parallel swimlanes
-
For decisions leading to distinctly different flows, use parallel swimlanes or subprocesses (e.g., standard process vs. special review).
-
Tasks can be directed into the appropriate path accordingly.
⚠️ Caution: Automated logic jumps, as in BPMN, are not supported in ValueStreamer. All decisions must be made consciously and manually.
✨ Tips & Best Practices
-
📌 Use task templates with predefined decision steps.
-
🔗 Link tasks to reflect dependencies between decisions and follow-up processes.
-
📑 Document complex decision trees in parallel using BPMN diagrams for better orientation.
❓ FAQ
How can I represent a Yes/No decision in the process board?
➡️ Create a separate task for the decision. Describe the options and manually manage the follow-up tasks based on the outcome.
What if a decision leads to two completely different process flows?
➡️ Use separate process boards or swimlanes with distinct phase structures.
Can I automate decision logic?
➡️ No. ValueStreamer is not rule-based. Decisions are made consciously by the user.
Where should I document complex decision trees?
➡️ Use BPMN diagrams or process manuals for documentation. Operational execution is done in ValueStreamer.