Technical Lead & BPMN Educator·11 min read
The folder-of-diagrams problem
Most process documentation starts the same way: someone models their first diagram, then their second, then their tenth. Before long you have 50 BPMN files in a folder structure that only one person understands. There is no overview. No hierarchy. No way to see how a customer order flows from sales through fulfillment through invoicing.
A process landscape solves this. It is the map that shows where every detailed process fits within the bigger picture. Think of it as the table of contents for your organization's operational knowledge.
What is a process landscape?
A process landscape is a structured hierarchy of your organization's processes, arranged in levels of detail. It starts with the broadest view (the value chain) and drills down to individual workflows.
The standard leveling convention uses three tiers:
L0: Value Chain
The highest level. Shows the 5 to 10 major end-to-end process areas that define how the organization creates value. Examples: "Order to Cash", "Procure to Pay", "Hire to Retire". These are typically shown as a horizontal chain or a grid. No BPMN notation at this level.
L1: Process Groups
Each L0 area breaks down into 3 to 8 process groups. These are named business capabilities or macro-processes. Example: "Order to Cash" becomes "Lead Management", "Order Processing", "Fulfillment", "Invoicing", "Collections". Still no detailed BPMN, just named groupings with brief descriptions.
L2: Detailed Processes
Each L1 group contains the actual BPMN diagrams that show how work gets done. Example: "Order Processing" contains "Receive Order", "Validate Payment", "Allocate Inventory", "Confirm Order". This is where pools, lanes, gateways, and the full BPMN notation live.
"Some organizations use L3 and L4 for sub-processes and task-level detail. Start with three levels. You can always add depth later. The most common mistake is building too much detail too early, before the structure is stable."
Why you need one before you model anything
Jumping straight into detailed BPMN diagrams without a landscape is like writing chapters of a book without an outline. You will create good individual pieces that do not connect into a coherent whole.
Navigation
New team members, auditors, and consultants can find any process without asking the one person who knows where things are.
Completeness
The landscape reveals gaps. If "Invoicing" has zero L2 processes modeled, that is a known gap, not an unknown unknown.
Prioritization
When leadership asks "what should we improve first?", the landscape gives you the map to identify critical paths and bottlenecks across the organization.
Governance
Process owners can be assigned at the L1 level. Every detailed process has a clear home and a clear owner.
M&A readiness
After a merger, both organizations bring their landscapes. Overlaps and gaps become visible immediately. See our guide on process harmonization for more.
How to build a process landscape (step by step)
Step 1: Define the value chain (L0)
Start with the question: What are the 5 to 10 end-to-end process areas that define how this organization delivers value?
For most companies, the value chain follows a variation of Michael Porter's model: inbound logistics, operations, outbound logistics, marketing and sales, service. But real organizations are messier than textbooks.
A practical approach: list the major "noun-to-noun" flows. "Lead to Customer", "Order to Cash", "Idea to Product", "Hire to Retire", "Procure to Pay", "Issue to Resolution". These become your L0 boxes.
Naming convention
Use "X to Y" format for L0. It forces clarity about where the process starts and ends. "Sales" is ambiguous. "Lead to Customer" is not.
Step 2: Break down into process groups (L1)
Take each L0 area and identify 3 to 8 process groups within it. These should be distinct stages or capabilities, not just smaller versions of the L0.
Example: "Order to Cash" breaks down into:
- Lead Qualification
- Quote Generation
- Order Entry
- Fulfillment
- Invoicing
- Payment Collection
- Returns and Credits
Each L1 group should be assignable to a single process owner. If you cannot identify one owner, the group is either too broad or spans organizational boundaries that need to be acknowledged.
Step 3: Map detailed processes (L2)
This is where BPMN lives. Each L1 group contains one or more detailed process diagrams that show the actual workflow with pools, lanes, gateways, events, and tasks.
Do not model all L2 processes at once. Start with the processes that are most critical to the business or most frequently questioned. The landscape tells you which L1 groups to prioritize. See our step-by-step process mapping guide for the detailed methodology.
Step 4: Connect the levels
The power of a landscape comes from navigation. Each L0 area should link to its L1 groups. Each L1 group should link to its L2 diagrams. A user should be able to start at the value chain and drill down to any specific process in two clicks.
In practice, this means your tool needs to support hierarchical navigation, not just a flat list of diagrams. Some tools handle this natively (ARIS, Signavio, Crismo). Others require manual folder structures or wiki pages to simulate the hierarchy (draw.io, bpmn.io).
Step 5: Validate with stakeholders
The L0 and L1 structure should be reviewed by leadership, not just the process team. The value chain defines how the organization thinks about itself. If leadership does not recognize their business in your L0, the landscape will not be adopted.
Run a 30-minute workshop: show the L0 on screen, walk through each area, and ask "does this cover what we do?" You will get corrections and additions that make the landscape real. For more on this, see our guide on as-is vs to-be modeling.
Common mistakes
Mistake: Starting with L2
Build the structure (L0 and L1) before modeling any detailed processes. Without the structure, you are building rooms without a floor plan.
Mistake: Too many L0 areas
If you have more than 10 L0 areas, some are probably L1 groups in disguise. "Customer Onboarding" is not a value chain area. It is a process group within "Lead to Customer".
Mistake: Inconsistent naming
Pick a naming convention and enforce it. "X to Y" for L0, verb-noun for L2 ("Validate Payment", "Allocate Inventory"). Inconsistent naming makes the landscape unusable at scale.
Mistake: No process owners at L1
Every L1 group needs an owner. This is the person accountable for the processes within that group. Without owners, the landscape becomes orphaned documentation.
Mistake: Modeling everything at the same depth
Not every process needs the same level of detail. Critical processes get full L2 BPMN diagrams. Support processes might only need a brief description at L1. Read our guide on process documentation best practices for more.
"The landscape is a living document. Schedule a quarterly review with process owners to update the L1 structure and flag L2 processes that are out of date. A landscape that was built once and never updated becomes a historical artifact, not a working tool."
Which tools support process landscapes?
Not every BPMN tool supports hierarchical process landscapes. Most open-source editors (bpmn.io, draw.io) work at the individual diagram level. You need a platform that understands the L0/L1/L2 structure natively.
For a detailed comparison, take our tool finder quiz or browse all 16 tool profiles.
FAQ
How many levels should a process landscape have?
Three is the standard: L0 (value chain), L1 (process groups), L2 (detailed BPMN). Some organizations add L3 for sub-processes. Start with three and add depth only when you need it.
Is a process landscape the same as a value chain?
No. The value chain is the top level (L0) of the landscape. The landscape includes the value chain plus all the levels beneath it.
Do I need BPMN at every level?
No. L0 and L1 are typically shown as boxes or cards with names and descriptions. BPMN notation is only used at L2 (detailed processes) and below.
How long does it take to build one?
The L0 and L1 structure can be built in 2 to 3 workshops (1 to 2 weeks). Detailed L2 processes are modeled incrementally over months, prioritized by business need.
What if we already have dozens of diagrams but no landscape?
Build the L0 and L1 structure first, then assign each existing diagram to an L1 group. You will discover gaps and overlaps. This is a valuable exercise even if many diagrams need updating.
Continue reading
- As-Is vs To-Be Process Modeling (next step after building the landscape)
- How to Map a Process (Step by Step) (the L2 modeling methodology)
- Process Documentation Best Practices (how much detail to capture at each level)
- Best BPMN Tools 2026 (which tools support process landscapes)