Titelbild: Getting to the Bottom of a Question

Getting to the Bottom of a Question

Project Format · 4–6 Weeks · On Request

What to do when quick answers are not enough – and the question runs deeper than expected?

Some questions cannot be answered in two weeks. Not because they are complicated, but because they are interwoven with structures, dynamics, and dependencies that only become visible upon closer examination. A reorganization that doesn't take hold. A product that fails in the market. A team that doesn't work despite having good people.

An analysis pursues these questions methodically. It examines not only what is happening, but why it is happening – and which levers are actually available. This takes longer than a Sprint. But it delivers insights on which substantive decisions can be made.

What an Analysis Achieves

01

The Structure Behind the Problem

Symptoms are rarely the problem. An analysis uncovers the structures that produce and sustain the problem: decision pathways, communication patterns, dependencies between departments, implicit rules.

02

Multiple Perspectives, One Picture

We speak with the relevant actors – not to collect opinions, but to understand the different descriptions of the situation. What does leadership see? What does the team see? What does the customer see? Only from the composite view does a robust picture emerge.

03

Causes Instead of Correlations

Data shows what is connected. An analysis shows what causes what. We distinguish spurious correlations from actual chains of causation – and identify the points where intervention makes sense.

04

Options for Action with Rationale

The result is not a description of the problem, but a well-reasoned assessment: What are the realistic options for action? What speaks for each? And what would the consequences be? The organization can decide – informed and with open eyes.

How an Analysis Works

Phase 1

Question and Design

Week 1
Kick-off: Jointly sharpen the research question
Define the analytical framework: What do we investigate – and what deliberately not?
Identify data sources and interview partners
Determine methodology: interviews, document analysis, observation, workshops
Phase 2

Investigation and Synthesis

Week 2–4
Systematic data collection: interviews, documents, process observation
Interim analysis: recognize patterns, form and test hypotheses
Feedback loop with the client: share interim findings, adjust focus
Deepen investigation where findings prove central
Phase 3

Synthesis and Recommendation

Week 5–6
Condense findings into a coherent picture
Develop and justify options for action
Make consequences and trade-offs transparent
Final presentation, discussion, and handover
“Those who do not know the cause call the effect coincidence.”
— Werner Heisenberg (attributed)

When Is an Analysis the Right Choice?

A problem keeps recurring – despite various attempts to solve it
The causes lie deeper than the obvious symptoms suggest
An Exploration has delivered hypotheses that need rigorous testing
A substantial decision is pending – reorganization, strategic shift, investment – that needs a solid foundation
Note

An analysis is NOT suitable if fast results are needed. Anyone who needs something tangible in 2–3 weeks is better served by a Sprint.

What Do We Need from You?

A client who wants to hear the results even when they are uncomfortable
Access to the relevant people, documents, and processes
The willingness to give the analysis time – depth requires patience
4–6 weeks in which the topic is not pushed aside
“The problem is not the problem. The problem is your attitude about the problem.”
— Jack Sparrow (attributed)

Practical Information

Duration 4–6 weeks
Scope Interviews, document analysis, observation, synthesis
Format Project-based, on request
Language German (English on request)
Deliverable Analysis report, justified options for action, final presentation
Price On request

Three Formats, One Arc

The three project formats can be used individually – or as a connected arc: The Exploration maps the field. The Sprint makes ideas tangible. The Analysis goes deep.

Which combination makes sense depends on the question. Sometimes a sprint is enough. Sometimes you need an exploration first, then an analysis. And sometimes it is the other way around.

Exploration: Understanding the Starting Point Sprint: Working Quickly and with Focus All formats at a glance

Does Your Question Need More Than a Quick Answer?

Let us find out whether an analysis is the right format.

In 30 minutes, we will clarify the question, the possible scope, and whether the prerequisites for an analysis are in place.

Schedule a conversation (30 min)

Or write directly: falk@vorfeld.studio

Who Conducts the Analysis

Falk Engelmann

Thinks in systems, works with people. For over 18 years, he has been helping teams and organizations understand their own patterns – and intervene where change is actually possible.

Questions about the project format?

falk@vorfeld.studio

Or book a 30-minute conversation directly:

Schedule a conversation (30 min)

Also of interest:

Understanding the Starting Point (Exploration) Strengthening Decision-Making Capability

Conceptual Foundations

Functional Analysis

Not asking "What is going wrong?" but "What function does what is happening serve?" Behavior that appears dysfunctional often has a function within the system. Recognizing this is the first step toward change.

Second-Order Observation

Not just observing what happens – but observing how the organization itself observes. What distinctions does it use? What falls into the blind spot? What can it structurally not see?

Chains of Causation

In organizations, everything is connected to everything – but not equally. An analysis identifies the chains of causation that are actually relevant and distinguishes them from spurious correlations.

Latent Structures

What appears on the org chart is the formal structure. How decisions and communication actually happen beyond that is written nowhere. An analysis makes these informal structures visible – without judging them.

Triangulation

No single perspective is sufficient. Through the systematic combination of different sources – interviews, documents, observation – a picture emerges that is more robust than any single viewpoint.

Intervention Theory

Not every insight leads to a meaningful intervention. A good analysis distinguishes between what can be changed and what the organization must endure – and shows where the leverage is greatest.