Start Here
You have probably seen it.
A capable team. A clear goal. Strong intent from the top. And still, the same problems surface every quarter: delayed decisions, unclear ownership, coordination that costs more than it should.
The instinct is to blame the people, the process, or the tooling.
But the structure was the problem all along.
A note on geography: this site is the thinking (essays, patterns and the books). The portfolio of shipped software lives at ernster.dev. One entry point each.
This site is built around a single idea:
Structure determines outcomes.
Not effort. Not talent. Not intent.
If you’re new
Read this first:
👉 What is Decision Architecture?
This explains the core model in its simplest form.
The model
Organisations behave as systems.
Each system has:
- a structure
- observable signals
- a constrained set of possible actions
That set is the move space: the decisions a leader can actually make from their current position, like the legal moves available to a chess player from a given board state. Structure determines which moves exist.
What this means
Most change fails because it operates inside a broken move space.
It attempts to improve outcomes without changing the structure that produces them.
This is not a failure of people.
It is a property of the system.
How to navigate
👉 If you want the full model: Read the books
👉 If you want reusable components: Explore patterns
👉 If you want the argument in essay form: Selected essays
👉 If you want to see what I ship: The portfolio
This is not advice.
It is a system for reasoning.