Let's get to know each other.
The first step is clarity: an initial conversation.
Schedule an initial conversation
How decisions are made in your company
Decision Architecture
Structure, leadership, culture, and products emerge from decisions made and decisions not made. Decision Architecture clarifies how decisions come about, so that your next pivotal decision holds.
Schedule an initial conversationOn this page
For decisions with long-term impact
Many decisions fail not because of wrong options, but because it was never clear what was really being decided. Decision Architecture means not speeding decisions up, but clarifying the space for decisions.
I guide people and organizations in situations where decisions create long-term commitments. Financial, structural, human, or systemic.
The focus is not on the right solution, but on the decision space itself: Which options are real? Which assumptions are at work? What consequences emerge over time?
Seeing the whole
Making interactions and side effects visible. Grasping complexity, structuring decision spaces.
Responsibility & humanity
Responsibility begins before the decision. I help you make that distinction and shape it deliberately.
Systemic clarity
Understanding connections before organizations, roles, or products are irreversibly locked in.
The most expensive mistakes don’t happen in execution.
Expensive consequences arise when decisions are made before it is clear what is really being decided. I structure this space so that your next pivotal decision holds.
What sets Decision Architecture apart from the other service lines
Decisions are everywhere: in the organization, in products, in leadership. The other service lines look at what is decided and whether it holds. Only Decision Architecture looks at how decisions are made. That’s why it sits at the top, and that’s why it often ends up affecting several areas.
Organization
Structure & governance before major decisions
When structural decisions shape organizations for the long term. The Organization service line examines how the organization is built and how it runs.
Products & services
Product and service decisions
When products and services need to be examined from the customer’s and the system’s perspective. The Products & services service line examines the impact they have.
Leadership
Decisions with responsibility and liability
When decisions are directly tied to responsibility, power, and personal liability. The Leadership service line examines how leadership works as a system.
Decision Architecture is relevant for:
- Executives with real decision-making responsibility
- Business owners facing binding pivotal decisions
- Organizations facing structural or strategic commitments
- Product and service owners with long-term impact
- Situations where decisions are hard to reverse
Not suited for:
- quick opinion polls
- pure efficiency and cost optimization
- facts already settled in advance
- after-the-fact legitimization of decisions already made
Not like this
Three patterns I often see, and what holds instead.
Not like this
Three options on one slide
Executive management chooses between A, B, and C. Nobody has checked whether that is even the right question.
Instead: first clarify what really needs to be decided.
Not like this
Decided, but never lived
The decision is in the minutes. In day-to-day work, it is rolled back piece by piece, without anyone deciding to do so.
Instead: define follow-up decisions and thresholds in advance.
Not like this
The expert report decides
A consultant recommends, executive management follows. If it goes wrong, it was the recommendation’s fault.
Instead: responsibility stays with those who bear the consequences.
What I bring to Decision Architecture
- Executive MBA (SMBS Salzburg) and Director’s Program for management and supervisory board members
- Stakeholder management and decision processes in large corporations and high-growth companies
- Complexity management and decision-making capability
- Experience with high-stakes decisions in uncertain and politically charged situations
- A mirror without an agenda: no internal loyalties, no interests of my own
Guiding principles
Decision Architecture is a prerequisite, not an add-on
Organizations are the result of decisions made
Products reflect the logic behind decisions
Leadership is a consequence of good decisions
Development begins with clarity, not with programs
An example of this way of thinking: Decision Architecture: Real estate use case.
Decision Architecture
The path in three stages
Before that: the initial conversation. Clarity on whether to continue, and with what.
- Stage 1 · ClarifyDecision AuditWhat really needs to be decided
- Stage 2 · DecideDecision LabA sound decision, played through before it's made
- Stage 3 · Follow throughDecision guidanceFollow-up decisions that fit together
