Ask her what she did for ten years and she'll tell you her title. Ask her what she actually did, underneath the title, and she'll say something like 'I just kept everyone on the same page' or 'I was just the person people came to when something was falling apart.' Just. That word is doing an enormous amount of quiet damage.
Whatever came after 'just' in that sentence is almost always the actual skill — the real, specific, rare thing she did better than the people around her, so consistently that it stopped registering as a skill at all and started registering as just who she is. You don't call your own native language a skill either. That doesn't mean it isn't one.
The things you call 'just' are usually the things you've done so long and so well that you forgot anyone else finds them hard.
There's a cultural layer to this too, worth naming plainly: a lot of Black women were raised to treat quiet competence as the safest kind — do the work, don't make noise about it, let the results speak. Results rarely speak as loudly as the person willing to name them out loud. That isn't a character flaw to fix. It's a habit worth examining, because the workplace rewarding silence and the workplace rewarding the work are almost never the same workplace.
Why the real skill goes unnamed
Skills that get named clearly on a resume tend to be the ones that were taught explicitly, in a class, with a certificate at the end. The skills that actually run most workplaces — reading a room before it falls apart, translating between two departments that don't trust each other, holding a project together through three changes of leadership — were never taught in a class. Nobody handed you a syllabus for them. You built them by doing the job, under pressure, for years, which is exactly why they feel less like 'skills' and more like 'just how I am.'
I hear this constantly in career-transition conversations. A woman will describe, in exhaustive detail, a genuinely rare capability — she can walk into a chaotic situation, figure out what actually matters in the first ten minutes, and get five different people rowing in the same direction without anyone feeling steamrolled — and then close the story with 'but that's not really a skill, that's just me.' It is a skill. It's one a lot of companies would pay real money for and can't find, precisely because it doesn't show up as a line item on anyone's resume.
Picture the actual interview it costs her: she's asked what she brings to the role, and she answers with her title and a list of tools, because that's what feels like a legitimate answer. The interviewer nods, unremarkable, moves on. What never gets said is the thing that actually made her valuable for a decade — that she was the person leadership quietly routed every cross-team fire to, because she was the only one who could calm a room and still get the deliverable out on time. That sentence would have changed the interview. It never got said, because it had lived under 'just' for so long she didn't think to bring it.
The cost of calling it 'just'
When you can't name a skill, you can't sell it, and you definitely can't ask to be paid for it — you can only hope someone else notices it eventually and rewards it on their own timeline, which is exactly the arrangement that left a lot of women underpaid and under-recognized at the job they just left. Downplaying the skill doesn't make you humble. It makes you invisible in exactly the conversation — the interview, the pitch, the negotiation — where being visible actually matters.
It also quietly narrows what you think you're qualified to do next. If the thing that made you invaluable for a decade doesn't count as a real skill in your own accounting, you end up applying only for roles that look like your old title, instead of the wider range of roles that actually need exactly what you do. The skill was never the limitation. The name for it was.
Nobody hires 'just being organized.' They hire the person who can walk into chaos and make it legible. Those are the same person. Only one of them gets paid for it.
This pattern shows up especially hard after a layoff or a forced transition, because the identity that used to carry the skill's weight — the title, the team, the office — is suddenly gone, and what's left feels like just a person with vague, unlabeled capabilities instead of a professional with a name for what she does. That feeling is real. It is also not accurate. The skill didn't leave with the job. Only the context that used to name it for you did.
How to actually name it
Start with the sentence that starts with 'just' and finish it, then delete the word entirely and read what's left. 'I just kept everyone on the same page' becomes 'I built and maintained the communication structure that kept three teams aligned through two reorganizations.' Same fact. Completely different weight. The skill didn't change. The sentence finally caught up to what it actually was.
Then ask what would have happened if you hadn't done that thing — not hypothetically, but specifically, based on what you watched happen when it went missing even briefly. If the honest answer is 'things would have fallen apart,' write that down too. That's not exaggeration. That's evidence, and evidence is exactly what belongs on a resume instead of a modest guess at your own value.
I watch this shift happen fastest when someone does this exercise with another person instead of alone in their own head, because it's much easier to spot the minimized skill in someone else's story than in your own — ask a friend what she thinks you're actually good at, and pay close attention to whatever she says that starts to sound suspiciously like something you'd have called 'just' about yourself.
The real question
So here's the one worth sitting with: what's the sentence in your own story that starts with 'just'? Read it back once without the word in it, and notice what it actually says when it's finally allowed to say the whole thing.
You didn't spend a decade doing something unremarkable and calling it a job. You spent a decade doing something specific and rare, and calling it nothing, because nobody ever handed you the language to call it anything else. That language exists. It's worth learning to use it about yourself.
Want help naming what you actually built, in language that gets you paid for it? Start here: Discover