Process Landscapes: From Value Chain to Detailed Processes

#bpmn #processmodeling #architecture #tutorial

A single BPMN diagram tells you how one process works. A process landscape tells you how the entire organization fits together.

The folder-of-diagrams problem

Most process documentation starts the same way: someone models their first diagram, then their tenth, then their fiftieth. Before long you have 50 BPMN files in a folder structure that only one person understands. No overview. No hierarchy. No way to see how a customer order flows from sales through fulfillment.

What is a process landscape?

A structured hierarchy with three tiers:

L0: Value Chain — The 5 to 10 major end-to-end process areas. "Order to Cash", "Hire to Retire", "Procure to Pay". No BPMN at this level.

L1: Process Groups — Each L0 breaks into 3 to 8 named groups. "Order to Cash" becomes Lead Qualification, Order Entry, Fulfillment, Invoicing.

L2: Detailed Processes — The actual BPMN diagrams with pools, lanes, gateways, and tasks.

How to build one (5 steps)

Step 1: Define the value chain (L0)

List the major "noun-to-noun" flows: Lead to Customer, Order to Cash, Idea to Product, Hire to Retire. Use the "X to Y" naming convention.

Step 2: Break down into process groups (L1)

Each L0 gets 3 to 8 process groups. Each group should be assignable to a single process owner.

Step 3: Map detailed processes (L2)

This is where BPMN lives. Do not model everything at once. Start with the most critical processes.

Step 4: Connect the levels

Each L0 links to its L1 groups. Each L1 links to its L2 diagrams. Two clicks from value chain to any process.

Step 5: Validate with stakeholders

Show the L0 to leadership. Ask: "Does this cover what we do?" You will get corrections that make the landscape real.

Common mistakes

Starting with L2 — Build the structure before modeling detailed processes
Too many L0 areas — If you have more than 10, some are L1 groups in disguise
Inconsistent naming — Pick a convention and enforce it
No process owners at L1 — Every group needs an accountable person
Modeling everything at the same depth — Not every process needs full BPMN detail