There’s a specific kind of stuck that hits mid-project in complex product work. You’ve had your kickoff. You’ve done your discovery. You know what the feature needs to do. And then you go to draw the next screen and you can’t. Not because the design is hard. Because you genuinely don’t know where things go. You open your design tool. You stare at it. You try a layout. It doesn’t feel right. You try another. Days pass.
That feeling used to mean something very different to me depending on where I was in my career.
The three phases
Junior: protected from it
When I was junior, I was mostly shielded from this. My lead was there to do the heavy lifting on the hard conceptual parts. I’d feel bad about being stuck, ping them, and they’d unblock me. I thought it meant I just wasn’t smart enough yet. What was actually happening was that someone else was holding the complexity I couldn’t hold yet. I never had to face the full weight of it.
Intermediate: the dangerous phase
The intermediate phase is where it gets hard. You’re expected to carry more. The problems are getting bigger and more architectural. You’ve developed enough skill and confidence to take things on yourself — and the expectation is that you will. But you haven’t yet learned that enterprise-scale product problems are often too big for one person’s head. Deep data models, cross-product calculations, permission architectures, edge cases that span multiple systems.
When you hit the stuck place in this phase, the instinct is to push harder. Work it out. Prove you can handle it. That’s the trap. You stay in your own head too long because asking for help feels like admitting you’re not ready for the work.
Senior: recognizing the signal
At some point I stopped treating the stuck place as a failure and started treating it as a signal. It meant I didn’t have enough information to complete the design — not that I wasn’t capable. And often, the information wasn’t there because the problem itself hadn’t been fully worked out. Which meant the design clog was pointing at something real.
The Reframe
The stuck place isn’t a failure of skill. It’s information debt. The design is telling you it needs something the brief didn’t provide. Your job isn’t to push through it alone — it’s to name it and get the right people in the room.
What it actually looked like
I was working on multi-currency support in a complex financial forecasting product. Weeks into the work, I kept circling on the same part of the design. I’d go to draw a screen and realize I didn’t know where something would go — or more accurately, I couldn’t figure out how it would even be shaped. The data model I was designing for didn’t make sense to me at a fundamental level.
Rather than booking time with product and engineering immediately, I stayed in my own head longer than I should have. I kept trying to work it out. My productivity started to slow — not just on this piece, but across the whole project, because the stuck place was a bottleneck I kept walking back to.
When I finally called the whiteboard session, I just named it plainly: I don’t understand this part. Can you show me how it works in the existing UI? Can you draw what you’re thinking?
What came out of that session changed the whole design direction. We were looking at local calculations that needed to flex per scenario — but scenarios had always been treated as a single entity. When we drew it out together, we realized the fix wasn’t a UI problem at all. It was an architecture problem: we needed multi-currency sets on the Admin side that could be applied to scenarios. The way the system fed scenarios needed to change entirely. The clog wasn’t blocking the design — it was pointing at real architectural debt. And it never would have surfaced if I’d kept trying to solve it alone.
Why this is especially true in enterprise
Enterprise products are too big for one designer’s head. That’s not a weakness — it’s the nature of the work. Deep architecture, interconnected calculations, product decisions made years ago that still shape the data model today. When you work in this kind of system, the stuck place is often the edge of what design can resolve on its own.
Single-player superhero designers — the ones who pride themselves on never needing to ask — are a liability in this environment. Not because they lack skill, but because no one person can hold the full complexity. The triad exists for exactly this reason. When design hits a wall that is actually a product or systems problem, the triad needs to jam on it together. Waiting until you’ve already burned days on a dead end is a pattern worth breaking early.
What to do when you’re stuck
Name it out loud
The stuck place loses some of its grip when you say it plainly. “I’ve been circling on this for three days and I think I’m missing something structural.” That sentence is not a confession of failure. It’s a diagnostic. It tells the team where to focus.
Book the session before you think you need it
The sooner you pull the triad in, the cheaper it is. A one-hour whiteboard session early costs far less than a week of circling followed by a direction change after a review. Your instinct will tell you to wait until you have something to show. Ignore it. The point of the session isn’t to present — it’s to draw together until the system makes sense.
Ask the dumb question
The most useful thing I said in that multi-currency session was “I don’t understand this.” Not a polished question. Not a well-framed design problem. Just an honest statement of what I didn’t know. That opened the conversation that unlocked everything else. The expertise is in the room. Your job is to surface the gap clearly enough that it can be filled.
For design managers
If someone on your team has gone quiet about a piece of work for longer than usual, check in. Designers — especially intermediate designers trying to prove themselves — will stay stuck longer than they should before asking for help. A simple “what’s the hardest part right now?” can open it. You’re not rescuing them. You’re normalizing the signal.
The part nobody tells you
When I was more junior, I thought being stuck meant I wasn’t good enough yet. I thought the goal was to get the design done — that done was the measure of success. It drove a lot of unnecessary iteration: trying things, getting them wrong, trying again, never pausing to ask whether I had enough information to try anything useful at all.
What I’ve learned since is that the stuck place is often the most important place in the design process. Not despite the friction — because of it. The clog is where the hardest, most interesting problems live. The ones that require everyone in the room. The ones that, when you finally crack them together, actually move something.
Some of my best design work started with “I don’t know how to draw this.”
Written by Bob Werner. Part of the UX Field Notes series on design leadership and craft.