Some of the best designers I’ve ever worked with were nearly invisible.
Not because they weren’t contributing. They were contributing enormously. Quietly, consistently, without any particular need for recognition. The work was always good. The thinking was always sound. The team depended on them in ways that only became obvious when they were absent.
They were also, consistently, the people who weren’t getting promoted. Who weren’t being tapped for the high-visibility projects. Who weren’t in the conversation when leadership was thinking about who to develop or stretch.
This is the quiet competence problem, and it’s one of the more persistent failures of design leadership.
It happens because most organisations, even the ones with good intentions around equity and development, default to a visibility bias when making decisions about talent. The people who speak in meetings, who present their work with confidence, who advocate for themselves clearly and frequently, disproportionately get the opportunities. The people who let the work speak for itself, who are uncomfortable with self-promotion, or who come from professional cultures where quiet diligence is the norm, get overlooked.
The outcome, if you let it compound over time, is that your team’s most visible members aren’t necessarily your most capable ones. You’re developing and promoting based on social confidence rather than design quality. And you’re quietly communicating to the less visible members of your team that the rules of advancement aren’t quite what the official story says.
As a design leader, this is your problem to fix.
The first step is getting honest about your own visibility bias. I’ve had to sit with the realisation that I underestimated people on my team because they didn’t advocate for themselves in the ways I unconsciously expected. The mental model I had of them was built more on their presence in meetings than on the quality of their work. That’s a leadership failure, even if it’s a common one.
The fix starts with changing how you gather evidence of contribution. If you’re relying primarily on what you observe in group settings, you’re working with a biased sample. The quiet, competent people are doing the majority of their best work outside those settings. In the work itself. In the thinking they bring to a review. In the way they approach a difficult problem without making a performance of it.
You have to go to where the work is. Not wait for it to be presented to you.
This means regular, specific engagement with individual work. Not just check-ins. Actually looking at what someone has built and asking questions about the thinking behind it. You’ll often find that the person you thought was a solid mid-level contributor has been making strategic decisions in their design work that you had no idea about. They just weren’t narrating it to you.
The second step is creating structural opportunities for quiet contributors to become visible without requiring them to change who they are. Not forcing them to present in ways that don’t suit them. Not coaching them to self-promote. That’s asking them to pay a social tax that their louder peers don’t have to pay.
Instead: rotate who presents work in design reviews. Create formats where the depth of thinking gets surfaced naturally rather than through performance. Give credit publicly and specifically when good work happens quietly. Make it known, by how you operate, that you notice the work rather than just the presentation of it.
The third step is having honest conversations about what advancement actually requires in your organisation. Sometimes the quiet competence problem isn’t just about recognition. It’s about the reality that moving up in many organisations genuinely requires a degree of visibility and self-advocacy that some designers aren’t comfortable with. If that’s true, tell people. Let them make informed decisions about whether they want to develop those muscles or whether they’d rather go deep in the work at a level that doesn’t require them.
Both are legitimate choices. Pretending the visibility requirement doesn’t exist, while continuing to apply it, is how you lose the trust of the people working hardest on your team.
Design teams are full of people who became designers because they wanted to make things that work for people, not because they wanted to perform competence in leadership reviews. Protecting the space for that orientation, while helping people develop the skills to navigate the organisational realities, is some of the most important work a design leader can do.
The quiet people are usually the ones with the most to say. Finding ways to hear it is on you.
