Process-Driven vs Capability-Driven Approaches in SAP Enterprise Architecture

This infographic contrasts process-driven and capability-driven approaches for connecting SAP investments and changes across an automotive supplier.

When planning an ERP transformation, a familiar question arises: should the assessment begin with business processes or business capabilities?

For an Enterprise Architect (EA), the central task is to connect decisions about where to invest with decisions about how business operations and systems should change.

In SAP Enterprise Architecture, process-driven and capability-driven approaches provide perspectives for assessment and scoping, depending on the purpose of the transformation. Drawing on official SAP sources, this article explains their differences and how to apply them in practice.

Where Do Process-Driven and Capability-Driven Approaches Begin?

Capability-Driven Approach: Start with the Capabilities the Enterprise Needs

A capability-driven approach starts with the question: “What must the enterprise be able to do to execute its business strategy?”

SAP LeanIX describes business capabilities as follows:

“Business capabilities define what your organization does to deliver value, independent of how it is achieved by processes or technology.”

Source: SAP LeanIX Help – Add Business Capabilities

In manufacturing, capabilities such as demand planning, inventory management, and production planning can serve as assessment units. For each, the architect examines strategic importance, current capability, and the gap between the current and target states.

The question the EA seeks to answer is: which capabilities should be strengthened, to what extent, and in what order of priority?

Process-Driven Approach: Start with the Flow of Work

A process-driven approach starts with the question: “How does work flow through the business, and where do problems occur?”

For example, an architect may trace the process from order receipt to delivery, examining responsibilities, required information, supporting systems, handoffs, and exception handling at each step. This reveals the causes of delays and rework and informs the design of future processes.

SAP’s transformation guidance describes the approach as follows:

“The process-driven approach outlined in these guides is best suited for a new ERP implementation (Greenfield) where scoping starts from the process perspective.”

This identifies new ERP implementations as a suitable context because their scope is defined from a process perspective.

Source: SAP Learning – Establishing Business and IT Transparency

The question the EA seeks to answer is: which business activities should change, how should they change, and which data and applications should support them?

Key Differences Between the Two Approaches

Dimension	Capability-Driven Approach	Process-Driven Approach
Starting question	What must the enterprise be able to do?	How does work flow, and where do problems occur?
Primary assessment units	Business capabilities	End-to-end processes, individual steps, and process variants
Principal decisions	Capabilities to strengthen and investment priorities	Business changes and their impact
Typical artifacts	Capability maps, assessment heatmaps, and priorities	Process hierarchies, current and future process models, and improvement requirements
Useful contexts	Enterprise transformation planning and investment decisions across business units	New ERP implementations, process standardization, and process improvement

This comparison is a practical synthesis of several SAP sources. The approaches are best understood as perspectives that answer different questions, rather than as mutually exclusive formal procedures.

Choose the Starting Point Based on the Transformation Objective

When Setting Enterprise-Wide Investment Priorities

A capability-driven approach is useful when multiple business units or departments submit improvement requests.

Mapping those requests to business capabilities makes it easier to compare their relationship to business strategy and their enterprise-wide impact.

SAP’s EA learning material describes an assessment that begins with the current state:

“This approach starts with the current state and focuses on understanding how well business and technology capabilities perform today.”

The assessment begins by understanding how effectively existing business and technology capabilities operate.

Source: SAP Learning – Articulating the Architecture Vision

Adding strategic importance and target outcomes to this assessment provides a basis for discussing investment priorities.

When Defining the Business Scope and Specific Changes

A process-driven approach is useful for ERP implementation and process standardization.

Organizing the processes in scope and comparing standard processes with business requirements helps define future operations, exception handling, and system requirements.

However, SAP’s statement that this approach is well suited to Greenfield implementations does not mean that it is exclusive to Greenfield projects.

SAP’s transformation guidance also refers to an application-driven approach for system conversions, with an emphasis on applications and interfaces. It is therefore inappropriate to reduce the distinction to “Greenfield means process-driven; Brownfield means capability-driven.”

Practical Example: Responding to Demand Changes at an Automotive Supplier

Consider an automotive supplier with the following business objective:

“Respond to changes in OEM demand, improve delivery performance, and keep inventory under control.”

The following example illustrates how the two approaches can work together.

Step 1: Identify the Capabilities to Strengthen

First, identify the capabilities needed to achieve the objective.

Examples include capturing demand information, supply planning, production planning, inventory visibility, and communicating delivery commitments. Assess each capability’s strategic importance, current state, and gap to the target state.

Before selecting individual products, determine which capability gaps have the greatest impact on the business problem.

Step 2: Analyze the Related Processes

Next, examine the processes associated with the priority capabilities.

One example is the flow from receiving an OEM demand forecast to assessing changes, updating supply and production plans, and communicating delivery commitments.

At each step, ask:

Does the information required for a decision arrive in time?
Are the decision criteria and responsibilities for planning changes clear?
Do manual entry and data transfers cause delays or errors?
Do handoffs between departments or systems create bottlenecks?

This translates an assessment such as “limited responsiveness to demand changes” into specific operational problems and change requirements.

Step 3: Connect the Findings to Application and Data Changes

Once the future process is defined, examine the applications, data, and interfaces required to support it.

Assess the functional fit and lifecycle of existing systems, and identify dependencies between business changes and IT changes.

SAP describes how processes managed in Signavio can be connected with capability and application information managed in LeanIX to support decisions about transformation scope and impact.

Step 4: Reflect Dependencies in the Roadmap

Identifying a capability to strengthen does not guarantee that it can deliver value immediately. The necessary data and integrations must also be in place.

Identify prerequisites—such as data preparation, process changes, and application changes—and reflect them in the implementation sequence.

For this example, the architect should be able to trace the following relationships:

Business objectives → Capabilities → Business processes → Applications and data → Transformation initiatives

In practice, findings from process analysis may also feed back into the capability assessment and lead to revised priorities.

Five Questions Every Enterprise Architect Should Ask

The following questions help connect the two approaches:

Strategy: Which business outcomes and KPIs should improve?
Capabilities: Which capabilities are required, and where are the gaps between current and target states?
Processes: Through which processes are these capabilities exercised, and where are they constrained?
Architecture: Which data, applications, and integrations are involved?
Roadmap: Which initiatives should proceed, in what sequence, and with which dependencies?

Conclusion

A capability-driven approach helps determine which capabilities to strengthen and how to prioritize investment in line with business strategy. A process-driven approach helps analyze operations and specify how business processes and systems should change.

The Enterprise Architect connects these perspectives, establishing a consistent relationship from investment decisions to operational changes and the IT roadmap.

Choosing the starting point according to the transformation objective—and revisiting findings across both perspectives—helps align strategy with execution.

References

Disclaimer

Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.