Skill Gapping.

There is a gap that haunts every growing designer. You look at a layout and you know it works. You can feel the hierarchy pulling your eye, sense the spacing creating rhythm, recognize that the color choices are doing something right. But when someone asks you to explain why it works, the words fall apart. You reach for “it just feels balanced” or “the whitespace is nice” — and you know, even as you say it, that you’re not actually explaining anything.

For years I thought that gap was proof I didn’t really know what I was doing. That the good designers — the ones whose work I studied late at night, the ones giving talks at conferences, the ones hired into Staff positions at companies I admired — had somehow skipped the gap entirely. They didn’t feel it. They just knew.

I was wrong about that. Not a little wrong. Completely, structurally wrong. The gap never goes away. It just moves. The designers whose work I admired weren’t gap-free — they had gotten good at one specific thing: seeing the gap clearly, naming what was missing, and closing it deliberately. I started calling that move Skill Gapping, and it has been the single most important skill of my career.

What Skill Gapping is.

Skill Gapping is getting good at evaluating your work against a frame of reference, and treating the distance between the two as actionable information. It has three moves:

1. 01
   See the gap.

   Hold your current work up against a specific reference point — a piece of work you admire, a competency rubric, a staff designer’s portfolio, the framing of a peer you think is a level ahead. Let yourself feel the difference. Don’t flinch from it.

2. 02
   Name what’s missing.

   The gap is never “I need to get better.” That’s not a diagnosis; it’s the starting condition. The gap is always specific: I can’t articulate design rationale under pressure. I don’t know how to structure a case study around outcome metrics. I don’t know what “scope” means when a hiring manager says the candidate needs more of it. Vague gaps stay open forever. Named gaps can be closed.

3. 03
   Close it deliberately.

   Not through generic practice. Through the single most targeted action that would close this named gap. If the gap is articulation, that’s explaining your work out loud to a peer every week. If it’s scope, it’s volunteering for the unglamorous cross-team project nobody wants. The closer is always specific and usually uncomfortable.

That’s the whole framework. Three moves, repeated forever. The gap never stops appearing — as you grow, the reference point moves with you. The senior designer’s gap is different from the junior designer’s gap, but the move is the same.

The reframe: taste has outpaced skill.

Here’s the part that took me years to see: the reason the gap hurts is because your taste has developed faster than your skill. If your taste hadn’t improved, you wouldn’t be able to see the gap in the first place. You’d be happy with your work. The fact that it bothers you — that you can feel there’s something better you haven’t reached yet — is proof that the bar you’re measuring against has moved up.

That’s not impostor syndrome. Or rather: that is what people call impostor syndrome, but the common framing has it backwards. Impostor syndrome isn’t evidence that you’re secretly not a real designer. It’s evidence that your taste has outpaced your skill. That’s the opposite of a weakness. It’s the precondition for growth.

Impostor syndrome is evidence that your taste has outpaced your skill. That gap is the most productive place to be.

I spent the first two years of my career trying to eliminate the feeling. I studied more, practiced more, consumed every article and tutorial I could find. The feeling never went away. It got worse, because the more I learned, the higher the reference moved. It wasn’t until I started treating the gap as the object of study — rather than something to overcome — that things started to change. I stopped trying to feel like I belonged and started asking a more useful question: what’s the specific gap I’m looking at right now, and what is the shortest path to closing it?

Not every gap needs to close now.

A common failure mode, once you start seeing gaps, is trying to close all of them at once. That’s how people burn out. It’s also how careers stall, because you end up shallow-studying five things instead of deeply closing one.

The complement to Skill Gapping is selective black-boxing. Some gaps are worth closing now. Others can stay closed — treated as inputs and outputs you use but don’t need to understand internally — until you have the bandwidth or the direct need to open them. When I started at Nike working on the Figma Library Sync plugin, I could have tried to close the gap between “designer who uses TypeScript” and “engineer who writes deep Figma plugin API patterns” in the first month. I didn’t. I black-boxed the parts of the plugin API I didn’t need to ship the first release, shipped it, then came back and opened the box with a concrete reason.

Black-boxing isn’t avoidance. It’s triage. The question isn’t should I close this gap? — it’s is this the gap I should close first?

What Skill Gapping is not.

It’s not “just practice more.” Practice without diagnosis closes only one kind of gap — the practice gap itself. If your gap is knowledge, or articulation, or understanding of a system, drilling the craft harder doesn’t help. You have to name the gap before you can close it.

It’s not years-of-experience as a proxy for readiness. I’ve seen designers with four years of experience who wait for direction on every project, and designers eighteen months in who proactively identify problems and rally their team around a plan. The difference is not time served. It’s how they orient to their work — whether they’re habitually looking for gaps and closing them, or habitually looking away.

And it’s not visual polish as a substitute for reasoning. A portfolio full of immaculate Dribbble shots with no case study behind them is evidence that the designer closed one gap (visual craft) while leaving the larger gap (problem-solving) untouched. Hiring managers aren’t hiring your taste. They’re hiring your ability to diagnose and close the rightgaps on their team’s problems.

How this connects to everything else.

Skill Gapping is the root framework on this site. The other frameworks plug into it:

• [Feynman Technique]

  The closing mechanism for articulation gaps. If you can’t explain a concept simply, the gap in your understanding is exactly where the explanation breaks down. Read the method →

• [Design Impact Framework]

  Skill Gapping sits at the “You” level of the Impact Reach Ladder. You cannot expand your impact to Team, Product, or Org scope if you haven’t first diagnosed and closed the gaps in your own craft and communication. Read the framework →

• [4-Layer Component Model]

  Skill Gapping applied to design-system literacy: before you can contribute to a system, diagnose whether you’re thinking at the Primitive layer when the problem demands a Composer. That mismatch is a gap. Read the guide →

• [Structured Paths]

  Every career path on paths.design is a sequence of named gaps with prescribed closers. You can’t follow a path until you’ve diagnosed which gap that path closes for you. Browse the paths →

How to practice it, starting today.

Pick one piece of work you’re currently doing. A project at work, a portfolio case study, a feature you’re designing. Now find a reference point — a senior-level version of that same kind of work. A case study from a designer whose scope you want to be operating at. A rubric for the next level of your ladder. The portfolio of someone you want to be mistaken for three years from now.

Hold your work against it. Don’t judge. Just observe. What is the most specific difference you can name? Not “theirs is better” — a pointer. Theirs opens with the business problem, mine opens with the solution. Theirs shows what they rejected, mine only shows what they shipped. Theirs uses numbers, mine uses adjectives.

That’s a named gap. Now write down the smallest thing you could do this week to close it. Not the biggest thing. The smallest. One step. Then do it.

That’s Skill Gapping. It’s not complicated. It’s just unusual, because most of us were taught to hide our gaps and perform competence instead. If you can learn to do the opposite — to treat the gap as the most useful diagnostic information you’ll get all year — the rest of your career starts to look different.

Your taste has outpaced your skill. That’s the good news. Now go close the gap.