Vague feedback is why good work stalls

Vague feedback feels kind, but it slows everything down.

Feedback stops being useful when it avoids a decision.

Over the past week, nearly every conversation I’ve had has pointed to the same pattern: work that’s technically strong, but isn’t communicated clearly. Not because the work is weak, but because the feedback around it never forces an action.

Direct feedback isn’t harsh. It’s specific. It names what needs to change. And that's what moves work forward.

When feedback stays vague, decisions get deferred in the name of comfort.

Momentum stalls. Work lingers in a state of “almost there.”

Strong designers default to being direct. They decide what doesn’t belong and take action. They remove what dilutes the message. They make fewer things carry more weight.

Solid feedback sharpens focus. It narrows options. It creates forward motion.

High standards feel uncomfortable before they feel obvious. Eventually, they become non-negotiable.

If your work isn’t moving, it’s worth asking:

What decision is being avoided?

Warmly,

David Campana

Founder, Level^Up
Head of UX | Ex-Apple, WeWork, Verizon

PS: If your work technically functions but isn’t moving you forward, reply with the section you’re unsure about. I’ll tell you whether it earns its place.

Unsubscribe · Preferences

Read more from Elevate your skills. Grow your impact.

Why solid experience isn’t enough anymore

There was a time when having solid work was enough. That time is over. Hiring decisions today are made under pressure: more candidates, less time, and far less tolerance for ambiguity. Strong work is still essential.It’s just no longer sufficient. If hiring managers can’t quickly tell: what kind of designer you are what you can be trusted with whether you’re operating at a senior level we move on, even when the work itself is solid. Not because you're unqualified, but because their story...

16 days ago • 1 min read

Strong UX work. Still no interviews? Here’s what to cut.

Strong UX work. Still no interviews? Here’s what to cut. Everyone in my last cohort had strong work.Every single one of them was still stuck. Not because they didn’t know how to write a resume. Not because their case studies were weak. Not because they lacked experience. They were stuck because they hadn’t made a few uncomfortable decisions yet. What kept showing up Across the first two live sessions, the same patterns repeated: Too many artifacts competing for attention Consulting experience...

20 days ago • 1 min read

Why adding more case studies hurts your chances

Why adding more case studies hurts your chances Adding one more case study often feels productive. It feels safe, like you’re increasing your chances. In practice, it does the opposite. More work increases surface area. It introduces noise. It gives reviewers more opportunities to hesitate, compare, and second-guess. Hiring decisions don’t improve with volume; they improve when the clarity of your decisions, trade-offs, and constraints is undeniable. When I review portfolios, resumes, or case...

27 days ago • 1 min read