"Why does step three exist at all?"
I was three years into my career. The brief was clear: redesign the onboarding step where users drop off. I'd diagnosed it, sketched the solution, was ready to present.
My manager asked that one question. I didn't have an answer.
We went upstream. Found the business rule that had created step three. Once we understood it, the solution was obvious. We didn't redesign the step. We removed the constraint that required it.
That was my first real encounter with systems thinking. Not a framework — a perspective I had to be forced into.
What it actually is
Not a methodology. Not a workshop. Not a diagram type.
Systems thinking is the habit of looking for the structure underneath the surface. Not just what is happening — but why is it arranged this way, and what would change if the arrangement changed.
In design terms: the difference between redesigning a button and asking why the button needs to exist. Between fixing a flow and asking what business logic created the friction. Between designing for the current constraint and asking whether the constraint itself should be redesigned.
This gets concrete fast. You're in a design review. Someone proposes a solution that will definitely fix the immediate problem and definitely cause three downstream problems nobody has modelled. Systems thinking is what lets you see that before you ship.
The Figma trap
The tools we use shape the questions we ask.
Figma is extraordinary for spatial thinking, component thinking, state thinking. What it's not built for: causal thinking. Upstream thinking. Relationship thinking.
When you open a file, you're already one level of abstraction removed from the problem. The frame is defined. The scope is implied. The solution space has been pre-shaped by whoever wrote the brief.
Systems thinking happens before you open Figma. It's the work of understanding why you're opening it at all — what the brief is optimising for, and whether it's asking the right question.
Most teams skip this. Not because they're lazy. Because the process doesn't create space for it. The sprint starts Monday. The brief is in the ticket. There's a review on Friday. The pressure is on output, and output lives in Figma.
Why it's a survival skill now
The design industry is compressing. Less headcount. More output expected from fewer people. AI tools doing in minutes what used to take days.
In this environment — what does a senior designer actually provide?
Not execution speed. AI changed that. Not component-level craft. Junior designers with good taste and good tools can get close enough on most surfaces.
What a senior designer provides is the judgment to solve the right problem. To look at a brief and recognise when it's addressing a symptom. To build something that holds up when the product scales, the team changes, the market shifts.
That judgment is systems thinking. Not learnable from a framework — learnable from doing the work, making the mistakes, and asking why enough times that the upstream questions become reflexive.
How I've built the habit
Map before designing. Before significant work, I draw the system — not the interface, but the relationships. Actors. Goals. Where they conflict. What creates the friction I'm being asked to solve.
First principles over analogies. "This is like the onboarding on Product X" is tempting. But copying the pattern imports its constraints. First principles forces the question: do those constraints actually apply here?
Five whys past comfort. Most briefs have three layers of assumed constraint above the stated problem. The interesting design decisions live at the bottom of those assumptions.
Ship and watch. No upstream thinking replaces watching the system behave in the real world. The model is always incomplete. The point is to have one, test it, and update it faster than the team that doesn't.
The skill that's made me a better designer isn't Figma proficiency or research craft or visual execution — though I care about all of those.
It's the ability to zoom out until I can see the shape of the system. Then zoom back in to the right place to intervene.
That's not optional anymore. It's the job.