The navigator encounters the system from inside it. Friction is not theoretical there. A beautiful design can still be frustrating. A coherent strategy can fall apart in use. A feature can work and still feel heavy in the hand.
The director works at another scale. They step outside the immediate experience long enough to see relationships the navigator cannot: sequence, context, boundaries, emphasis, consequence. They turn what happens locally into a structure that can be shaped deliberately.
The two roles want different things.
The director wants coherence across the whole.
The navigator wants momentum through the next moment.
The director asks: Where are we going, and why does this belong?
The navigator asks: Can I do what I need to do from here?
Neither question is sufficient.
The director’s edge is not doing more of the work. It is knowing what to ask for. The broader their knowledge, the more possibilities they can see—and the better their questions become.
But questions eventually meet the floor.
Stay only on the balcony and the system becomes elegant but lifeless. Stay only on the floor and every local irritation can become the whole problem.
There is another reason to keep returning to the navigator’s position: people do things with systems that their designers never anticipated. They find shortcuts, workarounds, exploits, and new uses. They reveal possibilities that cannot be discovered from the diagram because they emerge only through use.
So the relationship is not director over navigator.
It is a loop:
Navigate → notice → step out → reframe → reshape → navigate again.
They descend until they can feel the friction.
They ascend until they can see what the friction means.
Then they change the frame and go back down.