The Bar No One Can See

There's a phrase that comes up in a lot of product organizations. You hear it in performance reviews, in hiring conversations, in the hallway after someone leaves. "We have a high bar."

It sounds like a standard. It sounds like rigor. But in practice, when nobody can describe what that bar actually looks like, it's not a standard. It's a shield. It protects leadership from having to do the harder work of developing people, giving honest feedback, and building clear paths for growth.

I've seen this pattern play out more than once. And I've talked to enough designers, PMs, and ICs at other companies to know it's not unique to any one place.

The pattern

It goes like this. A company hires someone into a role. That person does the work, ships results, builds things that didn't exist before. They ask about growth. The feedback they get back is vague. "You're doing well, but we have a high bar." Or "you're close, but not quite there yet." No rubric. No specifics. No development plan.

Then a few months later, leadership posts a job listing for a role above them. Not alongside them. Above them. External hire, higher title, higher pay. The person who built the foundation watches someone new walk in on top of it.

The message is hard to miss. Your work was good enough to build on, but you weren't good enough to lead it.

Why this hits designers harder

Engineering has had career ladders for years. Junior, mid, senior, staff, principal. The expectations at each level are documented. You can look at a rubric and understand what "senior" means in terms of scope, autonomy, and impact. It's not perfect, but it exists.

Design ladders exist on paper at a lot of companies. But in practice, they're rarely used. Promotions happen when someone threatens to leave, not when they've earned it through documented criteria. "Senior designer" means something different at every company, and most of them can't tell you what it means at theirs.

For solo designers, this is even worse. When you're the only designer, there's nobody at the next level to model. There's no design manager advocating for your growth in rooms you're not in. Your work gets absorbed into the product narrative. When things ship well, it's "the new UI." When things are blocked, it's "the designer needs to be more assertive about scope."

The cost of vague feedback

Vague feedback feels safe to give. It avoids confrontation. It lets a manager say "I told them" without having to say anything specific. But it creates a slow erosion of trust that's hard to reverse.

When someone hears "high bar" three reviews in a row without a single concrete example of what meeting that bar looks like, they stop believing growth is possible at that company. They don't always leave immediately. They disengage first. They stop volunteering for the hard problems. They stop sharing ideas in meetings. They start interviewing quietly. And when they finally leave, leadership is surprised.

I've watched this happen to PMs, engineers, and designers. Good people who shipped good work. They didn't leave because they couldn't meet the bar. They left because nobody would show them where it was.

Hiring over your team

There's a difference between hiring senior people to expand capacity and hiring senior people to replace the growth path of your existing team.

The first one sounds like: "We're bringing in someone with deep experience in X to complement what we already have. Here's how the roles will work together."

The second one sounds like: silence, followed by a job posting, followed by "we'll figure out the reporting structure later."

When a company hires externally at a senior level without first having an honest conversation with the people already doing the work, it communicates something very specific. It says: we'd rather pay market rate for someone new than invest in you.

The people who stay notice. They do the math. They see that the external hire is coming in at a title and comp that they were told they weren't ready for. And they start to wonder if the "high bar" was ever real, or if it was just a way to hold them in place until a replacement arrived.

What good leadership actually looks like

I've had managers who did this well. It's not complicated, but it does require effort.

They told me exactly what "the next level" looked like. Not in vague terms, but in specific behaviors and outcomes. "At this level, we expect you to lead cross-functional initiatives end to end." "At this level, you should be influencing the roadmap, not just executing on it." Clear. Concrete. Something I could work toward.

They gave feedback that was specific enough to act on. Not "be more strategic" but "in that meeting, you presented three options without a recommendation. At the next level, you'd come in with a point of view and defend it."

They advocated in rooms I wasn't in. I didn't always know it was happening, but the results showed up. A stretch project. A seat at a table I hadn't been invited to before. A raise that came without a threat to leave.

That's what developing people looks like. It's not glamorous. It doesn't scale the way hiring does. But it builds teams that stay, and staying teams compound their impact over time.

The real cost

When a company loses someone they could have developed, they don't just lose a headcount. They lose institutional knowledge, relationships with customers and stakeholders, context about why decisions were made, and the trust of everyone who watched it happen.

The people who remain see the pattern. They adjust their expectations. They stop assuming the company is invested in their growth. They start treating the job as a transaction, not a career. And eventually, they leave too. Not all at once. Slowly. The best ones first, because they have the most options.

Replacing a single employee costs between 50% and 200% of their annual salary, depending on the role. That's before you account for the productivity dip, the ramp time, and the organizational memory that walks out the door. The math on "hire over" versus "develop from within" is not close.

What designers should demand

If your company can't answer these questions, that's information.

What does the next level look like for my role, specifically? Not "more impact" or "broader scope." What behaviors, what outcomes, what artifacts?

When was the last time someone on this team was promoted internally into a senior role? If the answer is never, or if the answer requires thinking about it for too long, that tells you something about whether the path exists or just looks good on a slide.

What's the plan for my growth over the next six months? Not the company's plan. My plan. With milestones and check-ins and someone accountable for following through.

You deserve clear answers. If you're not getting them, it's not because you haven't earned them. It's because the system was never built to give them.

The bar is real. It should be visible.

Having a high bar is a good thing. Expecting excellence is a good thing. But a bar that nobody can see isn't a standard. It's a trapdoor. People walk over it every day thinking they're on solid ground, until one day the floor drops.

If you're a leader, make the bar visible. Write it down. Share it. Reference it in every review. Update it when the company changes. Give people a real shot at clearing it.

If you're a designer or PM or IC working under invisible expectations, know that the problem isn't your performance. The problem is a system that benefits from keeping you uncertain. Your leverage is your clarity about your own value, and your willingness to go somewhere that sees it.