Imagine you need to build a bridge, but you do not yet know over which river, for whom, or whether the river will even be in the same place when the bridge is finished. That is exactly the situation many SMEs face today: digitalisation, AI, changing customer needs, regulatory requirements. All at once, all uncertain, all urgent.
The classic answer is a project plan: define the goal, divide into phases, set the budget, get going. That works when the goal is clear, the path known, and the environment stable. In uncharted territory, none of those apply.
What "uncharted territory" actually means
Uncharted territory is not simply "harder than usual". It means: the requirements are unknown. Users cannot yet say what they need because they do not know themselves. The technology is in flux, above all AI, which is changing at pace what can be automated, generated and delegated to machines. The goal changes as you move toward it.
In this situation, every project plan becomes self-deception: you plan precisely what you cannot yet know. The result is either failure after great effort, or an outcome that is technically correct but developed past the real needs.
Why classical agility alone is not enough
Agile methods like Scrum or Kanban help deliver quickly and iteratively. They are very good at solving known problems efficiently. But they do not answer the question: *are we solving the right problem?*
Scrum teams can run at high speed in the wrong direction. Without an explicit methodology for problem definition and user-centricity, agility becomes the accelerated execution of wrong assumptions.
Design Thinking: structure for the unstructurable
Design Thinking answers exactly this gap. It is not a creativity method but a discovery method. The core: first understand the person for whom you are developing a solution. Then build, test, learn and repeat.
The five phases, but not linearly
1. Empathize (Understand): Who are the people who experience the problem daily? What do they actually do, not what they say they do? Design Thinking begins with genuine field observation, not assumptions.
2. Define (Frame): What is the actual problem? Not the symptoms, not the first answer to "what bothers you?", but the underlying need. This phase is the most valuable and most underrated step.
3. Ideate (Develop): Only here do solutions enter the picture. And even then: quantity before quality, without self-censorship first. The best solution rarely comes from the first idea.
4. Prototype (Test): Make something tangible: quickly, cheaply, disposably. A mockup, a role-play, a sketch. The goal is not perfection but reaction.
5. Test (Learn): Back to the people. What works? What does not? Which assumptions were wrong? This feedback is the real value, not the solution itself.
These phases are not sequential. You jump back. You question assumptions that were considered settled two phases earlier. That is not a mistake. That is the process.
Why Design Thinking works especially well in uncharted territory
In familiar terrain you can rely on experience. In uncharted territory you cannot, and that is exactly why you need a method that systematically builds knowledge that does not yet exist.
Design Thinking is designed for this. It:
- Delays solutions until the problem is truly understood. That avoids the most common mistake in unknown territory.
- Makes assumptions visible rather than hiding them. Every prototype is an experiment that tests assumptions.
- Allows fast failure at small scale before failing at large scale. A disposable prototype costs hours, not months.
- Involves the right people early and continuously. Those who will use the solution later help shape it.
What this means concretely for SMEs
SMEs have a structural advantage over large organisations: they can move fast. Short decision paths, direct customer proximity, no corporate bureaucracy. Design Thinking multiplies this advantage.
An SME that wants to introduce a new digital service does not need a six-month requirements analysis. It needs three interviews with real customers, an afternoon ideation with the team and a clickable prototype that can be tested next week. In four weeks you learn more than in four months of planning.
This is not wishful thinking. This is the methodology behind most successful digital transformations that actually land.
Design Thinking and AI: a natural connection
AI projects are uncharted territory par excellence. Nobody knows in advance which model solves which task how well, how users respond to AI assistants, or which data basis is truly sufficient.
Design Thinking is the only method that consistently deals with this uncertainty rather than ignoring it. An AI prototype after one week, tested with real users, gives more insight than a detailed specification document after three months.
Conclusion: structure is not the opposite of openness
The greatest misconception about Design Thinking: that it is chaotic, unstructured, only for creatives. The opposite is true. Design Thinking is a rigorous discovery methodology that replaces random decisions with systematic learning.
In uncharted territory, that is the only kind of structure that helps. Not the master plan that reality overtakes month by month, but the method that learns with it.
Butterflies do not build a plan before they pupate. They follow a process that enables fundamental transformation, and in the end, they fly.