StratoAtlas maps methodologies not as a catalog, but as a system.
Each method operates at a specific system level, performs a particular
type of action, and behaves differently depending on the perspective
from which it is observed.
Without these coordinates, methods appear interchangeable.
With them, their limits become visible.
The design and product field contains hundreds of methodologies.
Most of them describe their internal logic well.
Few describe how they relate to one another.
StratoAtlas approaches the landscape from the outside —
by mapping where methods operate in the system
and what kind of action they perform.
Problems appear similar on the surface, but live at different depths of the system. A method that works at one level may be invisible, irrelevant, or harmful at another.
Methods do different kinds of work inside a system. Some help us understand what is happening. Others generate possibilities, orient choices, resolve contradictions, or improve what already exists.
Understanding the system and identifying its actual structure. What is really happening and why.
Producing new ideas, approaches, or conceptual directions. Expanding the solution space.
Choosing between competing options and focusing effort on what matters most.
Resolving concrete problems or contradictions within the system. Finding the mechanism, not the workaround.
Improving an existing system through refinement and iteration. Getting better at doing what is already defined.
Methods are usually described from a single perspective — their intended use. StratoAtlas observes each method from four perspectives. A method that works well from one angle may create illusions or damage from another.
The system level and action type where this method is most commonly introduced. Where practitioners naturally start when they reach for it.
The conditions under which this method genuinely moves the system. Not where it is used — where it actually works.
The zone where applying the method produces visible artifacts and a sense of progress — while the underlying problem remains untouched.
Applied at the wrong system level, the method strengthens exactly what it was intended to resolve. More effort produces more damage.
Not every method belongs to every environment. StratoAtlas marks the origin and native context of each method — because a method developed for manufacturing behaves differently when applied to digital product systems.
Created for digital product environments. These methods assume digital constraints, iteration cycles, and user feedback loops.
Originally developed in other fields — manufacturing, engineering, psychology — but usable in product systems with translation.
Methods designed to operate across disciplines. Their power comes from independence from any single domain's assumptions.
While mapping methodologies, one particular zone stood out.
The zone around architectural contradictions.
The lowest methodological density on the entire map.
Not because the problems there are rare —
because the field has not yet developed adequate tools for them.
TRIZ resolves contradictions. It finds the inventive principle that satisfies both requirements simultaneously. The contradiction disappears.
Some contradictions should not be resolved. They drive the system. CDSA focuses on identifying, maintaining, and creating productive contradictions at the architectural level.
CDSA — Contradiction-Driven Systems Architecture — grew from this observation. Not as a new framework invented to fill a gap, but as the next question in the same investigation.
A parallel line of investigation concerns trialogue — a configuration of human + AI + AI that makes the positional level operationally accessible. Trialogue is not mapped as a methodology on the StratoAtlas map. It is a research configuration: a practice for reaching the level where frames become visible as frames.
Learn more in the research section →The map becomes a diagnostic tool when used with these coordinates in mind.
Start with the level where the problem appears. What system depth is this problem actually at?
Identify the type of action required. Do you need to understand, generate, prioritise, resolve, or optimise?
Observe the method from multiple perspectives. Where is its maximum impact? Where does it create illusion?