Business Process Architecture: Functional vs. Value Stream Approaches Explained

When it’s time to start a business process management initiative, many organisations jump straight into creating process maps without deciding how they will organise them. As the number of processes starts growing into hundreds or even thousands, storing these processes becomes difficult to navigate when needed. And after a time, it becomes likely impossible to maintain.

A process architecture is important to have a structure to organise the business processes. Even knowing its importance, PRIME BPM 2026’s BPM survey found that 45% of BPM professionals in the U.S. usually start creating process maps without defining a process structure.

Before mapping more processes, organisations need to first understand how those processes should fit together.

What Is Business Process Architecture?

Business process architecture provides a structured view of the processes that make an organisation work. It is not just a visual hierarchy of processes; it also acts as a central process repository and single source of truth for how work is structured and managed across the organisation.

Business process architecture is a structured visualisation of building blocks (your business processes) that makes your operations work. It also acts as a central process repository (single-source-of-truth) to organise all the process data in one place.

Hence, it gives a way to logically and systematically catalogue process data, including process maps, procedures or work instructions, task information, risk and control data, and other information connected with how processes are operating and will operate.

It provides a way to logically and systematically catalogue process data in one place, including process maps, procedures and work instructions, task information, risk and control data, and other information associated with how processes operate.

Instead of having hundreds or thousands of process maps and related documents scattered across folders, departments, and systems, a process architecture brings this information into a structured process landscape.

A process map shows how a particular process works. Process architecture shows where that process fits within the wider organisation and connects the dots of different types of information associated with it.

Why Process Architecture Matters for Business Strategy

The purpose of process architecture is to give your organisation a clear, bird’s-eye view of the process landscape and the information associated with those processes. That visibility can then support a range of operational and improvement initiatives.

What Process Architecture Provides

A process architecture can provide visibility into:

• The processes that exist across the organisation
• The number and names of processes
• Where processes are located within the organisation
• How processes are organised within a hierarchy
• Who owns or is responsible for processes
• The information associated with each process

It is to basically create a more consistent understanding of the organisation’s operating landscape.

Without this visibility, it can be difficult for your organisation to know whether a process has already been documented, who is responsible for it, or how it relates to other processes.

What This Visibility Enables

Once the process landscape is visible, an organisation can use it to support a range of initiatives.

Process architecture can help organisations:

• Create a foundation for process mapping and continuous improvement initiatives by understanding what processes exist and where to focus.
• Plan organisational restructuring by identifying processes, ownership and responsibilities that may be affected by organisational changes.
• Share high-level process information with stakeholders without requiring them to dig through thousands of process maps
• Assess the organisation holistically by looking across functions rather than viewing processes in isolated departmental silos
• Prioritise critical processes for detailed mapping, analysis or improvement based on their importance and potential impact
• Identify gaps in the operating model by examining how processes, ownership and responsibilities are structured across the organisation

Two Ways to Structure Your Processes: Functional vs. Value Stream

Once you have decided to establish a process architecture, the next question is:

How should the processes be organised?

There are two useful ways to create business process architecture.

Value Stream and Functional Process Architecture.

Let’s understand the strengths and limitations of each approach to choose the best for your organisation.

1. Value Stream Architecture: Follow the Journey From Start to Finish

Before defining value stream process architecture, let’s first understand what a value stream means.

A value stream is the collection of actions and processes involved in delivering a specific product, service, or any outcome that creates value for a customer. It follows the journey from the initial customer need or request through the activities performed across the organisation to the final delivery of that value.

When process architecture is structured around value streams, the process repository reflects this end-to-end view of how the organisation delivers its products and services.

Instead of organising processes primarily around departments or functions, related processes are connected based on the outcome they collectively deliver. This makes it easier to see how activities across different parts of the organisation contribute to a specific product, service, or customer outcome.

A value stream-based process architecture can therefore provide a clear view of the organisation’s core products and services and the processes that enable them. It connects the underlying processes to the outcomes the organisation ultimately exists to deliver, creating a more customer- and outcome-oriented view of the process landscape.

Example

Let’s understand with a simple example of a Procure to Pay value stream.

At a high level, the value stream may include folders or process groups such as:

Evaluate Order Goods → Receive Goods and Check Quality → Process Invoice → Make Payment → Manage Suppliers

Each represents a part of the broader value stream. When you need to examine one of these areas in more detail, you can further open the folder to reveal the underlying processes.

For example, let’s say you are willing to evaluate Order Goods. It may contain processes such as:

Process Requisition → Approve Requisition → Track Vendor Quotes → Create Purchase Order → Expedite Order → Resolve Order Exception

This example shows an important characteristic of value stream architecture: the high-level architecture shows the end-to-end value stream, while the underlying process structure provides increasing levels of detail.

The result is a process landscape that can be viewed at both levels – you can understand the overall value stream while still being able to dig down into the individual processes that contain the detailed process maps to complete the journey.

Benefits of a Value Stream Approach

You can get the following benefits from a value stream approach:

• Aligned with how work happens in practice — reflects the end-to-end flow of work, hence making it more intuitive and relevant for frontline teams.
• Makes process connectivity visible — shows how processes interact and highlights dependencies and handoffs across functions.
• Simplifies upstream and downstream gap analysis — makes it easier to identify gaps, dependencies, and potential issues across the value stream.
• Helps prioritise critical processes — provides a clear view of the processes that directly contribute to core products, services, and customer outcomes.

Constraints of a Value Stream Approach

While this end-to-end approach is beneficial, it also comes up with its own challenges, which are:

• Process ownership can be harder to establish — value streams often cross multiple functions, making accountability less straightforward.
• Lower-priority processes can be overlooked — focusing on core value streams may make supporting or less critical processes less visible.
• More complex to maintain — cross-functional relationships and dependencies can make a value stream architecture harder to maintain than a functional structure.

Functional Process Architecture: Organising Processes Around the Organisation

A functional process architecture, also known as a hierarchical structure, organises processes according to the way an organisation itself is structured. It will help you mirror the hierarchy of your organisational functions, making departments, business units, teams, and their associated processes visible within the process architecture.

Unlike a value stream structure, which is organised around outcomes and how the organisation delivers value, a functional approach is organised around functions, capabilities, roles, and ownership. To navigate a functional process repository, you therefore follow the organisational structure rather than a customer journey or business outcome.

The functional approach can be viewed as a logical and systematic catalogue of process information, where users drill down through the organisational hierarchy. The structure will start from the organisation to departments, business units, teams, and ultimately the processes performed within them.

Example

Let’s also understand this approach with a simple example of creating a purchase order.

You will need to create an organisational hierarchy that forms the basis of the functional structure. It will look like this:

At the top is the Company, which will be divided into departments such as Supply Chain, Customer Service, and Finance. Within Supply Chain, the structure is further divided into business units such as Demand Forecasting, Vendor Management, and Procurement. The Procurement Business Unit is then divided into teams, including Tenders and Purchase Orders.

To find the Create Purchase Order process, a user can navigate through:

Company → Supply Chain Department → Procurement Business Unit → Purchase Orders Team → Create Purchase Order

This illustrates how a functional architecture provides a systematic way to organise and locate processes based on where they belong within the organisation.

Benefits of a Functional Approach

You will get the following advantages when building and managing an organisation-wide process architecture:

• Supports architecture completeness — provides a systematic way to identify and catalogue processes across your anisation, regardless of which processes are currently considered a priority.
• Represents all functions consistently — ensures that processes across your different organisational areas are represented rather than focusing only on core or high-priority value streams.
• Provides a systematic top-down structure — you can navigate from the organisation level through departments, business units, teams, and processes in a logical sequence.
• Reduces gaps and duplication — following the organisational structure, you can easily identify where processes should belong and reduce the risk of missing or duplicating processes.
• Creates clear process ownership — processes can be associated with the functions, teams, and organisational areas responsible for them.
• Is relatively easy to develop and maintain — because the architecture follows the existing organisational structure, it can be straightforward for process owners to understand, populate, and maintain.

Constraints of a Functional Approach

The same organisational structure that makes functional architecture systematic can also limit the perspective it provides.

• High-level process connectivity is not visible — because processes are organised around functions, it can be difficult to see how processes connect across departments to deliver an end-to-end outcome or customer journey.
• Less aligned with how work is experienced by frontline teams — frontline employees often experience work as an end-to-end flow that crosses functional boundaries. Navigating through departments, business units, and teams may therefore feel less intuitive than following the actual flow of work.

Which Process Architecture Approach to Choose – Combine the Power of Both

By now, it is clear that a well-structured process architecture will provide the foundation for organising, managing, and using process information. But which architecture approach is right for your organisation?

To get the best answer to this, these two questions can help:

1. Who are the primary users of the process repository?
2. What is the purpose of creating the repository?

When a Functional Approach Makes More Sense

If your process repository will mainly be used by process modellers, process owners, and other experts for analytical purposes, and ongoing ownership and maintenance are important, then a functional approach may be the better choice.

When a Value Stream Approach Makes More Sense

If your processes are mainly meant to be consumed by frontline staff, who need to find processes easily and understand how their work fits into a broader journey, then a value stream approach may be more suitable. It provides a more intuitive way for people to find the processes they need and helps standardise the way work is performed.

However, if you need the best of both worlds, you can combine the two approaches.

What Happens When You Combine Both Approaches?

The functional approach can ensure that you have a complete process repository with no gaps or duplicates, while value stream journey maps can provide a user-friendly entry point into the repository for frontline staff.

This gives you a structure that is easier to maintain, reusable across different needs, and scalable as the organisation grows. It can also help future-proof the process architecture against the inevitable changes in organisational structure.

But There Is One Important Thing to Keep in Mind

You need to be careful when combining the two approaches.

Simply starting with a functional hierarchy and then switching to a value stream structure somewhere in the middle can become confusing. It can even magnify the drawbacks of both approaches rather than giving you the benefits of each.

The hybrid model works best when both views are developed in parallel, using the building blocks from the functional structure to create the value stream journeys.

This means that the functional structure remains the foundation, while you can connect the same process into value stream journeys to give users a different way of navigating the repository.

The approach becomes even more effective when the system you use does not allow duplicate processes in the functional structure. This means that a process only needs to be created and maintained once, even when it is used as part of different value stream journeys.

In simple terms:

Build the process once. Use it in the functional structure. Connect it to value streams when needed.

This allows you to maintain the completeness and structure of the functional approach while giving frontline users the simpler, end-to-end experience of a value stream approach.

5 Steps to Harness the Best of Both Options

Building a hybrid process architecture does not mean creating two separate repositories. The key is to build a strong functional structure and then use the processes within it to create value stream journeys.

Here is a practical way to approach it.

Step 1: Select a Focus Area

Start with a specific value stream, product, service, or business outcome that you want to understand.

For example, if you want to map the Procure to Pay journey, start by defining what the end-to-end value stream should include and what outcome it is expected to deliver.

Step 2: Build the Functional Framework

Once the focus area is clear, identify the functions, departments, business units, and teams involved.

Build the functional structure and create the relevant process libraries under each area. This gives you the foundation for systematically capturing the processes involved.

At this stage, focus on making the functional repository complete, logical, and free from duplicate processes.

Step 3: Identify the Processes That Contribute to the Value Stream

Now look across the functional structure and identify the processes that contribute to the selected value stream.

These processes may sit under different departments or teams. The objective is to understand which existing processes collectively contribute to the end-to-end outcome.

You are not creating new copies of these processes. You are identifying and connecting the relevant building blocks that already exist in the functional structure.

Step 4: Build the Value Stream Journey

Connect the processes you identify into an end-to-end value stream journey.

This creates a different way of looking at the same process repository. Instead of navigating through departments and teams, users can follow the journey from the initial need to the final outcome.

In this example:

Procure to Pay → Evaluate Order Goods → Receive Goods and Check Quality → Process Invoice → Make Payment

Each stage can then lead users to the underlying processes that support it.

Step 5: Maintain One Source of Process Information

The final and most important step is that you need to maintain the process information only once.

When you update the process, the change will reflect wherever that process is going to be used. Whether someone accesses it through the functional structure or through a value stream journey.

This is what makes the hybrid approach scalable.

Build a Strong Process Architecture to Support Process Improvements

Creating a process architecture is not the end goal. The real value comes from what you can do with the process information once it is structured, connected, and easy to access.

When process maps are connected with information such as tasks, roles, procedures, business rules, KPIs, and other process data, teams can move beyond simply documenting processes to understanding how they work and where they can be improved.

A BPM platform such as PRIME BPM brings this information together in a central process repository and supports process mapping, process analysis and improvement, and process monitoring with the power of AI.

Ultimately, a well-designed process architecture gives organisations the foundation to manage processes more consistently, identify improvement opportunities faster, and continuously improve how work gets done.