Abstraction
Abstraction is the act of filtering out unnecessary detail to surface what truly matters.
It’s the core cognitive tool behind everything Positive Constraint does. Without it, problems stay complex. With it, they become solvable.
The idea
Every problem domain has two layers:
- Surface detail — the industry jargon, the org charts, the technology stack, the market dynamics, the competitor names. These are real, but they’re also noise.
- Underlying structure — the tensions, the trade-offs, the irreducible truths. These are the core constraints.
Abstraction is the move from layer 1 to layer 2.
Why it’s hard
Abstraction requires a kind of productive distance. You need to get close enough to a problem to understand it, then step back far enough to see its shape. Most people who are close to a problem can’t do this — they’re too embedded in the surface detail.
This is one reason an outside perspective helps. Not because the outsider knows more, but because they’re forced to abstract from the start.
In practice
The Mapping Constraints phase of every engagement is fundamentally an exercise in abstraction. We gather information, interview stakeholders, research the market — and then we let go of the details to ask: what is this problem, really?
The answer is almost always simpler than it first appeared.
Related ideas
- Core Constraints — what abstraction reveals
- Positive Constraint — what you build when you’ve found them
- About Omer — how abstraction became a personal philosophy