Design What You Do. Do What You Design.

There is a rule in scuba diving that never changes regardless of how experienced you become. Plan your dive. Dive your plan.

Justin's instructor said it on day one and it has stayed. Not because scuba diving and design work are obviously connected, but because the principle underneath them is the same: the value of a plan depends entirely on your commitment to following it.

‍

Design What You Do

This is the planning phase. Not just writing a brief or roughing out a concept. It means thinking through every decision before it is made, mapping the logic of an experience, and doing the hard work of understanding what you are actually trying to solve before you touch a tool.

In the wayfinding design process, this phase is everything. A hospital wayfinding system that has not been properly planned will fail patients at the moments they are most disoriented. A kiosk not designed from the user's perspective will be ignored. The planning is not administrative. It is design work.

After 30 years in digital wayfinding, the single most consistent pattern in projects that succeed is that the design phase was given the time it needed. Projects that cut planning short always pay for it later.

‍

Do What You Design

Execution fidelity. Following through on the designed plan with discipline, even when shortcuts appear, even when timelines compress, even when stakeholders push for scope changes mid-build.

This is not rigidity. It is respect for the thinking that went into the plan. Deviating from a considered design without a considered reason introduces decisions that were not tested, not mapped, and not understood. That is where wayfinding systems develop inconsistencies. Where the experience breaks down. Where users get lost.

Doing what you design also creates something valuable beyond the project itself: a clear bridge between design iterations. When planning and execution are aligned, you can trace exactly why each decision was made. That makes the next project sharper. It makes reviews honest. It gives other designers a thread to follow.

‍

Why the Gap Between Plan and Execution Matters

The distance between what was designed and what was built is where most project failures live. Not in bad ideas, not in weak briefs, but in the drift that happens between design intent and delivery.

Closing that gap requires discipline on both sides. A plan that is too rigid to accommodate real-world insight during delivery is not a plan, it is a cage. But execution that wanders freely from the design is not agile, it is undisciplined. The skill is knowing the difference.

‍

Simplicity Is the System

The full principle is not complicated. Design what you do. Do what you design. Review the gap between the two, learn from it, and apply it to the next iteration.

That cycle, done consistently over time, is what builds confidence and capability in any design team. It makes goals attainable. It makes the work enjoyable. And it produces outcomes you can stand behind because you can account for every decision that produced them.

This is not a technique with a branded name. It is a discipline. And it applies whether you are designing a kiosk for a hospital, a wayfinding system for a shopping centre, or planning your next dive.

‍