I used to think my design background was something to leave behind when I became a coach. I was wrong.
For years I kept the two worlds separate. Design was the previous chapter: the training at RISD, fifteen years running a strategy and design firm. Coaching was the new one. I thought becoming a coach meant becoming purely a coach, whatever that meant.
The separation didn't survive the work. In coaching sessions, I kept noticing I was seeing the way designers see. Watching the negative space. Listening for what wasn't being said. Treating a leader's situation the way a designer treats a brief: what exists, what's missing, what wants to be built. At first I resisted the instinct. Eventually I understood that the intersection was where the value lived.
Each discipline, practiced alone, has a limit the other one answers.
Design taught me to see what others miss and to make what doesn't yet exist. But design thinking has a boundary its practitioners rarely name. It can solve problems brilliantly. But it can't transform the problem-solver. It can reimagine systems. But it can't reimagine the person running them.
Coaching works exactly there. Where design asks how could we solve this, coaching asks who do you need to become. Where design creates external solutions, coaching creates internal shifts. For a while I thought I'd left one discipline for a better one. What I'd actually found was the missing half of the first.
One reframe carries most of what the intersection makes possible. Every problem a leader faces exists at their current way of seeing. The options that feel available, the constraints that feel fixed, the strategies that feel realistic: all of it reflects who the leader is today. Better analysis expands the options at the margins. A different leader sees a different set entirely.
This is why some persistent problems don't respond to better solutions. The talent problem that survives every recruiting improvement usually isn't a recruiting problem. It's about becoming someone the best people want to build under. The growth plateau that survives every new tactic usually isn't a tactics problem. It's the ceiling of the identity that created it. In each case the presenting question is how, and the operative question is who, and organizations reliably spend years on the first before anyone raises the second.
The practice I run now is built on holding both at once. The design disciplines do what they've always done: reframe the problem, find what's almost visible at the edges, give direction a form that can actually be built. The coaching disciplines work on the person the direction will require. Neither substitutes for the other. A transformed leader inside an unchanged system hits walls. A redesigned system led by an unchanged leader reverts. I watched both failures for years, from both sides, before understanding they were the same failure.
The most useful habit a leader can take from this is asking the second question. When a problem has survived several competent attempts at solving it, stop asking how to fix it. Ask what it would take for this to no longer be a problem at all. The answer to the first question is usually a plan. The answer to the second is usually a person.