Transformation Discovery Compass
A navigation instrument for transformation under uncertainty.
No framework. No maturity model.
But decision architecture within the system.
Why Transformation Fails at Decisions
Transformation is treated like a project: analysis, plan, execution. But dynamic systems do not follow linear logic. What appears as a strategy-execution gap is often a decision gap.
Organizations respond to complexity with activity. Programs, formats, initiatives — without clarifying which tension actually needs to be addressed. Agility without architecture creates speed without direction.
Tensions remain unnamed. Priorities compete without an ordering principle. Leadership teams defer — not out of weakness, but because no architecture exists that enables decisions.
Behavior follows context, and decisions change the context. Under uncertainty, however, the right answer cannot be calculated in advance. That is why the Compass does not look for the right answer, but for the decision behind the most effective experiment.
Map or compass
A map assumes the terrain is known. In transformation it rarely is: markets, technology and the organization itself change while you are on the move.
How we understand the Compass
- 1
The needle is the WHY.
At the center is the problem that really needs solving. It sets the direction, not a target picture.
- 2
The five fields show what slows you down.
They are not a maturity grid but the places where decisions get stuck.
- 3
The canvas shows where you stand today.
It is not a document to file away. When the situation changes, fill it in again.
The instrument
Six dimensions, one canvas
At the center is the WHY, the problem that really matters, and how urgent it is. The occasion for a transformation is not yet its WHY. The five fields around it show where decisions get blocked. Together they form the six perspectives of the Compass. Select any field; the “Guiding questions” view shows how the canvas is used in a workshop.
Select a field to see recognition signals, interplay and a typical pattern.
How you recognize it
Questions for working with the canvas
In depth
The dimensions in detail
For each dimension: how to recognize it, which questions to work with, what it interacts with, and which situations and insights relate to it.
WHY
Problem and urgency
The starting point of every transformation. What problems or tensions drive us? Collective problem clarity instead of individual opinions.
How you recognize it
- We don't share a common picture of which value-creating problem we're actually solving.
- Everyone nods at the vision, but each person means something different.
- We don't know what happens if we change nothing.
Guiding questions
- Which value-relevant problem are we solving?
- What happens if we change nothing?
Typical pattern "Everyone in the room nods at 'digitalization', but each person means something different."
Dynamic-Resilient Organization
Stability and agility
Balance between stability and agility. Structures that work while creating room for the new.
How you recognize it
- Constant friction between day-to-day operations and change.
- Some structures are too rigid, others too unstable, nobody distinguishes.
- We don't differentiate between red and blue value creation.
Guiding questions
- Where do we need stability, where agility?
- Which structures slow change down in daily operations?
Typical pattern "We introduced agile teams, but the approval processes remain the same."
High-Impact Teams
Ability, willingness, permission
Cross-functional teams with end-to-end responsibility. Ability, willingness, permission: all three must come together.
How you recognize it
- Teams are supposed to own end-to-end responsibility, but aren't allowed to decide.
- There's a lack of ability, willingness or permission, often all three at once.
- Psychological safety is missing, but nobody talks about it.
Guiding questions
- What do teams lack: ability, will or permission?
- Which decisions may teams make on their own?
Typical pattern "The teams are set up cross-functionally, but they still can't decide anything."
Systemic Leadership
From control to enablement
From control to shaping the framework conditions. Leadership measures effectiveness by how well teams can work.
How you recognize it
- Decisions are made where hierarchy sits, not where the expertise lives.
- Leaders decide too much and enable too little.
- Leadership effectiveness is measured by control, not by team success.
Guiding questions
- Where are decisions made, and where is the knowledge?
- What does leadership enable rather than control?
Typical pattern "We talk about empowerment, but every decision over €5,000 has to go through three hierarchy levels."
Adaptive Innovation
From initiative to capability
From occasional initiative to continuous capability. Iterative, incremental, and feedback-driven.
How you recognize it
- Innovation is more accident than capability for us.
- Testing an idea takes longer than developing it.
- We learn from failures, but not from experiments.
Guiding questions
- How quickly can an idea be tested?
- Who decides whether an experiment continues?
Typical pattern "Our innovation process has more stage-gates than our production process."
Responsive Strategy
From plan to operating system
From plan to strategic operating system. Continuous orientation process with hypotheses instead of certainties.
How you recognize it
- Our strategy is rarely adapted to changing conditions.
- Strategy is a document, not a living process.
- We formulate certainties instead of testable hypotheses.
Guiding questions
- Which assumptions does our strategy rest on?
- How do we notice early that they no longer hold?
Typical pattern "Our 5-year strategy is outdated after 6 months, but nobody dares say it out loud."
The Lever Lies Between the Fields
The weakest field is rarely the lever. What matters is the mechanism that keeps the blockage in place, and the decision that changes it. The Compass shows between which fields this mechanism sits.
A field is rarely weak on its own. Teams that do not make progress are often waiting for something decided elsewhere: approvals, budget, a priority. Investing only in the teams treats the symptom. This is what distinguishes a decision tool from a maturity model.
How to read the matrix: row by row. A dot means the field on the left strongly affects the field above. The colour is that of the acting field.
Seven tension axes
Between the six fields there are fifteen possible connections. These seven come up again and again in our mandates.
- Strategy ↔ OrganizationThe strategy demands something new, the structure rewards the existing.
- Leadership ↔ TeamsResponsibility has been handed over, decision rights have not.
- Innovation ↔ OrganizationExperiments have to pass through processes built for business as usual.
- WHY ↔ StrategyWithout a shared problem, the strategy makes no choice.
- Leadership ↔ OrganizationDecision rights and knowledge sit in different places. Customer knowledge reaches the top smoothed over or too late.
- Teams ↔ OrganizationEvery team owns its part; nobody owns the customer problem in between.
- Leadership ↔ InnovationFailure has consequences, missing innovation does not.
In practice
Working with the canvas
A Compass workshop follows three steps. The template is available as an A3 print for the room.
- 1
Start with the WHY
Capture the problem in one sentence before filling in the fields. Without a shared WHY, everyone collects observations about a different problem.
- 2
Collect observations
Use sticky notes in each field, one concrete observation per note, split into current state, helpful and hindering.
- 3
Draw the interplay
Mark connections between fields and look for the mechanism that keeps the blockage in place. This yields two or three candidate questions.
Two examples: completed compasses
Two companies, two problem statements, two entirely different patterns. This is what the Compass looks like after a workshop, and how observations turn into a decision question.
Example A · Machinery, family-owned, 1,400 employees, global leader in a niche
The success trap
How the problem was first described“We need to become more digital and need more innovation.”
01WHY
Symptoms
- Symptom: Margins with new customers have fallen for six quarters.
- Symptom: A start-up offers our core customers machine output as a subscription.
- Symptom: In the leadership team: “Our customers want quality, not a subscription.”
- Why do we not act, although we know?Because the core business earns enough every year.
- Why is that reason enough?Because every alternative is measured against machine revenue, and loses.
There is only one logic of success. A second business has no yardstick it could ever meet.
02Dynamic-Resilient Organization
- part of the pattern: Every initiative goes through the same stage-gate process, experiments included.
- Service is a department of sales, not a business of its own.
- Production is rightly tuned for zero defects.
03High-Impact Teams
- The best engineers spend 100 percent of their time on orders.
- One team built a digital service on the side, without a mandate.
- Sales and engineering only talk once an order is in.
04Systemic Leadership
- New ideas land with the owner personally and are decided there.
- Everyone agrees something must happen. Just not what.
- Mistakes in new ventures are judged as harshly as in series production.
05Adaptive Innovation
- part of the pattern: Five innovation projects, each with a five-year business case.
- None has been tested with a paying customer so far.
- part of the pattern: The subscription pilot was stopped after nine months: “revenue too small.”
06Responsive Strategy
- Strategy 2030 describes growth in the core. Service gets one sentence.
- part of the pattern: Budgets are set annually; shifting them during the year is not foreseen.
- Nobody can say which signal would trigger a change of course.
The pattern
The new is measured by the yardsticks of the old
Business cases, stage-gates and annual budgets are right for the core business. Applied to the new, every experiment loses to machine revenue before it could learn anything. The company is not too slow; it is still too successful for its own renewal.
The field of impact
Strategy, innovation and organization interlock: without its own success logic in the plan, there is no budget during the year and no room in the structure.
The decision question
Which business gets its own success logic, funded in tranches against evidence rather than the annual plan?
Not the lever: another innovation project
Example B · Insurance, corporate division with 2,800 employees, in the second year of an agile transformation
Agile on paper
How the problem was first described“Our teams need to become more agile. The methods have not settled in yet.”
01WHY
Symptoms
- Symptom: A new product feature still takes eleven months to reach customers.
- Symptom: At the staff forum: “We are sprinting into a traffic jam.”
- Symptom: Transformation success is measured by the number of agile teams.
- Why does it take so long?Because finished work waits for approvals and budget.
- Why does it wait?Because priority and money are decided where they were decided before the transformation.
The transformation changed how people work, but not who decides.
02Dynamic-Resilient Organization
- part of the pattern: Budgets are allocated annually per project, not per team.
- The line organization is unchanged; agility sits on top as a matrix.
- part of the pattern: Nobody decides which initiatives take priority across all teams.
03High-Impact Teams
- part of the pattern: Teams deliver every two weeks. Then the work waits for approvals.
- A team needs sign-off from four departments for a single change.
- Retrospectives happen. The topics have been the same for months.
04Systemic Leadership
- Division heads still steer through status reports and traffic lights.
- part of the pattern: Every initiative above 50,000 euros goes to the board.
- Leaders were trained. Their targets stayed the same.
05Adaptive Innovation
- The innovation lab shows strong prototypes. None has reached the core business.
- Customer feedback only arrives after release.
- Tests with real customers need individual legal approval.
06Responsive Strategy
- The strategy has twelve priorities, all equally important.
- OKRs were introduced. Goals are still handed down from the top.
- Transformation goals sit next to business goals, not inside them.
The pattern
Agility in the team, Taylorism in the system
The teams work fast; the system around them does not. Approvals, project budgets and the lack of prioritization across teams hold up every delivery. More Scrum only makes the jam more visible, and those who see it lose faith in the transformation.
The field of impact
Leadership, organization and teams hinge on the same decision rights: as long as priority and budget are decided at the top, teams wait, however well they work.
The decision question
Which decisions move from the board to a joint portfolio forum, and which go straight to the teams?
Not the lever: more Scrum training
Constructed examples based on typical workshop situations, not real companies. In a workshop each field usually collects eight to twelve notes.
The path
From canvas to decision
Discover, decide, anchor. Each step has a matching format. Where you start depends on how clear the situation already is.
- 01
Discover
What is really going on. Make tensions visible and clarify the real decision question before acting.
- Self-Check5 to 10 minutes, free
- Compact Workshopone day
- Blindspot Reportoutside perspective, in writing
- 02
Decide
Which decision changes the most. Weigh options against evidence and make the one decision instead of launching a program.
- Intensive Workshopone to two days
- 03
Anchor
What has to change in structure, budget, roles and committees so the decision holds and does not disappear with the next annual plan.
- Compass Engagementthree to twelve months
Then the next cycle begins. Transformation is not a project with a final boss but a rhythm: a decision round with a mandate looks at the situation with the Compass every six to eight weeks, reviews the last decisions and makes the next one. That is exactly what the Compass Engagement is.
The book (in German) · out late 2026 Die eine Entscheidung The path from canvas to decision is the subject of the book: 31 impulses for leadership teams, with the Compass, the twelve patterns and working templates. About the book Research
Empirically studied
Two master theses at HTW Dresden have examined the Self-Check based on the Compass, independently of each other and with different versions. The first asked whether it makes readiness for transformation visible, the second which of the twelve patterns appear and how the dimensions relate.
- 2
- master theses at HTW Dresden
- 40
- questionnaires on an earlier version
- 31
- self-checks with interview, 26 companies
- 12
- patterns checked in interviews
Study 1 · earlier version · scale 0–10 · n = 40
Study 2 · current version · scale 1–5 · n = 31
Four findings
- 1
The will is there, the organization is stuck
In both studies, teams, WHY and innovation are rated highest and the dynamic-resilient organization lowest. In the second study, nobody rates WHY or teams red. A low score for the organization can mean too little structure or too much.
- 2
Two patterns shape the picture
The most frequent were the strategy-execution gap (16 of 31) and blind-spot leadership (15 of 31). Five of the six strongest patterns involve the organization. Whether a pattern is really present only became clear in the interview.
- 3
In the second study, leadership and organization are hardly related
Both are often weak at the same time there (r = 0.20). Stronger leadership does not solve a structural problem by itself. With 31 cases, this is an indication, not a causal claim.
- 4
Where you sit determines what you see
In the first study, eight participants noted that their answers depended on their own area. In the second, leadership scores within one company ranged from 2 to 5. Both recommend completing the self-check as a team.
What the studies do not claim
Both studies rest on self-assessments from small, non-representative samples, in the second mostly from the operational level. They show correlations, not causes, and are no benchmark. The first thesis was written in cooperation with Pink Elephants and supervised by Alexander Sattler, who developed the Compass; for the second he was the second examiner. The first study examined an earlier version of the self-check (18 questions, scale 0–10), the second today’s version.
Take the Self-Check yourself → Full text of the first master thesis (HTW Dresden, German) ↗