01
Start with the business question
Architecture earns its place when it makes a consequential business decision clearer—not when it begins with a product catalogue.
Enterprise architecture · SAP transformation
Turning enterprise complexity into coherent direction.
I connect business ambition, operating models and technology choices—so transformation becomes a set of deliberate decisions, not a collection of projects.
Architecture is the line of sight fromstrategy to execution.
Business strategy→Capabilities→Processes→Applications→Data→Integration→Technology→Execution
01
About
A decision discipline
Enterprise architecture should help leaders see the organisation as one system.
My focus is the space between strategy and delivery: translating ambition into the capabilities, processes, platforms, data and governance needed to move an enterprise forward.
In SAP transformation, that means looking beyond the programme itself—clarifying what must be standardised, where differentiation creates value, and which decisions will shape the organisation for years.
02
Perspective
How I frame the work
Clarity before complexity.
02
Design the whole system
Strategy, operating model, processes, data and technology must move as one connected system, with deliberate boundaries and ownership.
03
Make the direction executable
A target architecture matters only when leaders can sequence decisions, manage trade-offs and turn it into a credible transformation path.
03
Executive lens
The questions that matter
Architecture becomes valuable when it improves the quality and timing of decisions.
Which capabilities will matter most in three to five years?
What should be standardised globally—and what should remain differentiated?
Which choices must we make now to avoid expensive constraints later?
Continue the conversation