The Identity Crisis Hiding Behind "I Want to Be More Strategic"
Every mid-level designer says they want to "think more strategically." But what most of them actually mean is: give me better borrowed frameworks. Real strategic thinking requires something most people avoid — the willingness to not know. This issue is about the difference between collecting maps and learning to walk in the dark.

Every designer I have coached in the last two years has said some version of the same thing. "I want to be more strategic." They say it in portfolio reviews. They say it in 1:1s with their managers. They write it in their career development goals.
When I ask what they mean, the answers sound identical. They want frameworks. They want mental models. They want a vocabulary that makes them sound like the people in the room who seem to know what they are doing. They want a map.
The problem is not that they lack maps. Most mid-level designers have read more strategy books than their PMs have. They can name five prioritization frameworks. They have bookmarked the RICE model, the Kano model, the Jobs-to-be-Done canvas. They have collected more maps than they will ever use.
And they are not one step closer to strategic thinking.
The anxiety underneath the ambition
There is a construct in psychology called intolerance of ambiguity. It was first described by Else Frenkel-Brunswik in the 1940s and later refined by researchers like Arie Kruglanski, who studied what he called the need for cognitive closure. The pattern is consistent. People with high need for closure experience genuine discomfort in situations where the answer is not clear, where the information is incomplete, where the right path forward cannot be determined from the available data.
Their coping response is predictable. They reach for structure. Any structure. A framework, a template, a process document, a best practice. The specific structure matters less than the feeling it provides. The feeling of knowing. The feeling of having a plan.
Designers are especially susceptible to this because design education trains them to follow a process. There is a research phase. There is an ideation phase. There is a testing phase. Each one has a deliverable. Each deliverable signals that you are making progress. The entire structure exists to convert ambiguity into certainty, one artifact at a time.
This works when you are executing. It collapses when you are supposed to be thinking.
Strategic thinking is not the application of the right framework to the right problem. It is the ability to sit in a problem that does not have a framework yet, to tolerate the discomfort of not knowing, and to form a point of view from incomplete information before anyone tells you what the answer should be.
That is not a knowledge gap. It is a psychological capacity. And no amount of framework-collecting will build it.
Maps versus terrain
The distinction matters because it changes what you practice.
A designer who believes strategic thinking is a knowledge problem will keep collecting. More books. More courses. More frameworks pinned to their wall. Every new model provides a brief hit of certainty. It feels like progress. It is not. It is a more sophisticated version of the same avoidance.
A designer who understands strategic thinking as a tolerance problem will practice something different. They will put themselves in situations where there is no map. They will write a point of view before reading what other people think. They will walk into a meeting with a perspective that might be wrong and say it anyway. They will sit with a problem for thirty minutes without opening Google or reaching for a canvas.
This is uncomfortable. That is the point. The discomfort is the training. You are not learning a new framework. You are expanding your capacity to function without one.
The designers who actually get called strategic — the ones PMs trust with problem framing, the ones who get pulled into roadmap conversations — are not the ones with the most models memorized. They are the ones who can look at an ambiguous situation and say "here is what I think is happening, here is why, and here is what I would do about it" before anyone hands them a template.
One move
Pick a problem you are currently working on. Before you look at any research, any competitor analysis, any framework — write one paragraph stating what you believe the right direction is and why. No sources. No scaffolding. Just your judgment, applied to incomplete information.
Read it back. Does it say something? Or does it say nothing in the language of something?
If you cannot write that paragraph without reaching for a framework first, the issue is not that you need more strategy. It is that you have been using strategy as a way to avoid the one thing strategic thinking actually requires: the willingness to be wrong.

