“What you did was worth nothing.”

The sentence landed flat, with no attempt to soften the fall. I was sitting in a meeting room years ago, watching a director dismantle six months of a team’s work in about fifteen seconds. Nobody pushed back. Nobody defended the work. The silence that followed wasn’t respect. It was recognition.

Because deep down, nobody in that room could prove otherwise.

I kept turning that scene over for days, without quite knowing why, until I ran into a number that explained the discomfort. A recent study measured the maturity of HR departments across Brazil. Average score: 37 out of 100. Nearly three quarters of the companies stuck in the first two stages of evolution, far from the point where the function sits at the same table as the business, as an equal.

The lowest number in the entire study, the only one that actually stopped me, had nothing to do with process or technology. It was about proof. Just over twenty points, on a question that asked, plainly, whether these departments could demonstrate the return on what they do.

This isn’t about incompetence. It’s about something far more uncomfortable: capable people, producing constantly, unable to back up a “what you did was worth nothing” with an “it was, and here’s how I know.”

I’ve watched that confrontation repeat itself in different rooms, in different shapes, across almost thirty years of studying behavior inside organizations.

I once watched two business partners argue until one shouted, “I don’t want to hear what you did, I want to know what’s left.” That line stayed with me for months. Because it exposes something we avoid: doing and leaving something behind are two different things. Most of us were trained, early on, to take pride in the first without ever asking about the second.

Disrespect, more often than not, isn’t cruelty for its own sake. It’s the raw reaction of someone who senses, without being able to name it, that they’re being fed the appearance of work. And when it happens inside a company, nobody calls it disrespect. They call it “tough feedback,” “a high-performance culture,” “accountability.” The labels change. The wound stays the same.

There’s a calculation we run before any confrontation like that, even without noticing we’re running it.

A quiet risk assessment: if I show everything, I expose my weakness. If I show only part of it, I protect my image but delay the real problem. Most people choose the second option, every time. And that’s how an entire company learns, without meaning to, that surviving a hard question matters more than answering it honestly.

It isn’t resistance to being evaluated. It’s fear of being unmasked.

There’s a real difference between those two things, and almost nobody separates them before making a decision.

The study offered another number that fits right into this. Most HR departments already use artificial intelligence day to day — that figure climbed fast, nearly forty points on the scale. But the ability to connect that technology to an actual business result sat at just over twenty-six.

The tool arrived. The honesty about what to do with it didn’t.

I think about this often when I watch companies chase technology the way someone chases an alibi. “We’re using AI” has become a phrase that shields, that dodges the next hard question, that buys time before someone asks where the result actually is. But an alibi doesn’t solve anything. It only postpones the question that’s still sitting there, unanswered.

I’ll challenge you to remember the last time someone confronted you at work — no gentleness, no softening — asking what, exactly, changed because of you.

If the answer that came to mind was a process, an activity, a meeting wrapped up on time, pay attention: that’s doing. It isn’t leaving something behind.

If the answer was something that kept existing after you left the room — a decision that wouldn’t have happened without you, a problem avoided because someone pushed against the current, a number that only moved because you refused to let it sit — that’s leaving something behind. And it’s rare.

There’s something cruel about this kind of confrontation that nobody likes to say out loud.

Whoever shouts “that was worth nothing” is almost never completely wrong. They’re being blunt, sure. Unfair, sometimes. But the discomfort behind it usually has some grounding: some part of that work really didn’t hold the weight it promised to hold. And instead of admitting that, most people — myself included, in moments I’m not proud of — choose to defend the delivery of the criticism instead of facing its substance.

The argument shifts to tone, to manners, to “you didn’t have to say it like that.” And the original problem, the one that triggered the confrontation in the first place, stays untouched, hidden behind a fight about how the criticism was delivered.

I remember one case specifically, years back, at a firm doing consulting work for the industrial sector. A manager had just presented the results of a talent retention program. Nice numbers, a downward turnover curve on the slide, polite applause.Someone in the back of the room raised a hand and asked something simple: “Are these numbers from before or after last quarter’s mass layoffs?”

Silence. The manager stumbled. The answer, when it finally came, was clearly invented on the spot. The program hadn’t reduced turnover at all — the job market had shrunk, and people stayed because they had nowhere else to go, not because the program worked.

Nobody technically lied. They just chose not to ask the question that would have taken the story apart before telling it in public.

This happens constantly, on a smaller scale, in nearly every results presentation I’ve ever sat through. We learn to build the narrative before checking whether it survives a hostile question. And without noticing, we train a dangerous skill: sounding convincing without ever needing to be correct.

The problem is that skill has an expiration date. It works until someone shows up willing to ask the wrong question at the wrong moment, without asking permission first. And what’s left, then, isn’t the number. It’s the discomfort of being caught twisting reality to fit a comfortable story.

There’s a real difference between convincing and holding up.

Convincing is a short-term performance — it works in a room, in a meeting, in a fifteen-minute pitch. Holding up demands something far more expensive: accepting that the hostile question is coming, sooner or later, and preparing not to escape it, but to stand through it.

Whoever builds a career on convincing lives terrified. They know, somewhere in their gut, that at any moment someone might ask the right question and bring the whole thing down. Whoever builds on holding up sleeps differently — not because they never fail, but because they don’t need to run from their own mistake when someone points at it.

I’ve noticed this difference plays out in job interviews too, oddly enough. The candidate who’s spent years convincing tells a flawless story — every project a triumph, every number trending up, no scar tissue anywhere in the narrative. It sounds great for about ten minutes. Then you ask one specific question about what went wrong, and the story cracks, because it was never built to hold weight, only to look good moving forward. The candidate who’s spent years holding up tells a messier story, full of things that didn’t work, and somehow that messier story is the one you trust.

Maybe the reason so many companies stay stuck at low maturity isn’t a lack of strategy, or a lack of tools. Maybe it’s this same personal cowardice, repeated at organizational scale: choosing to argue about the delivery of a confrontation instead of answering its content.

That would explain why structure alone doesn’t fix anything. The study found that medium and large companies scored slightly higher than small ones — but no size bracket, not even the most resourced, crossed the halfway mark. Money buys tools. It doesn’t buy the courage to answer “yes, that was worth nothing, and I’m going to change it” without running for an excuse first.

I keep picturing the HR professional reading a study like this and feeling their chest tighten, as if being confronted without being in the room. I understand that tightness. It rarely comes from incompetence — it comes from working inside a system that rewards visible activity and hasn’t yet learned to reward whoever can hold up proof.

There’s a real unfairness in that, and hardly anyone names it: people are asked for strategy, then judged on a short-term report. Asked for long-range vision, then punished for walking into a meeting without a polished number to show. In that environment, learning to defend yourself before learning to prove your worth isn’t a character flaw. It’s trained survival.

Only trained survival, over time, becomes identity. And a person stops noticing when they’re hiding something — because hiding has become reflex, not choice.

I think, sometimes, about how early that reflex gets installed. Nobody’s born hiding an uncomfortable piece of data before a presentation. That’s learned — usually the first time someone got punished, disproportionately hard, for bringing an incomplete truth or a bad result forward with honesty.

After that, the body learns before the mind does. The next time there’s a chance to expose something fragile, something tightens inside, before any conscious thought even forms. And the person chooses to protect, not because they decided to, but because their body decided for them, years earlier, in a scene they might not even remember.

That’s why so many smart people keep falling into the same trap, even while knowing, rationally, that transparency tends to pay off in the long run. It isn’t a lack of understanding. It’s a mechanism older than any corporate training program, and no lecture on “data culture” switches it off by itself.

I want to draw a distinction I think is essential, and that almost never comes up in this kind of conversation.

There’s the organization that punishes the mistake. And there’s the organization that punishes the exposure of the mistake. Those are entirely different things, though they’re usually treated as the same one.

The first, punishing the mistake itself, teaches something at least, even if harshly. The second, punishing whoever had the nerve to show the problem, teaches exactly the opposite of what it claims to teach. It teaches people to hide better, to dress things up more skillfully, to build an increasingly convincing front over a problem that never actually gets solved, only disguised.

Most companies I know swear they belong to the first group. Most, in practice, belong to the second — and the proof sits right there in that dismal capacity to demonstrate return. When an environment punishes whoever exposes fragility, the rational response from anyone inside it is to learn never to expose fragility again. And that’s how information stops moving, even while the reports keep looking flawless, month after month.

This brings me back to that meeting room from the beginning, all those years ago. At the time, I thought the problem was the director’s harshness. Looking back now, I understand the real problem was different: nobody in that room had prepared to answer the real question hiding behind the rudeness. Everyone had prepared to survive the tone. Nobody had prepared to hold up the substance.

This isn’t exclusive to big companies, or to any particular market. It’s a pattern that runs through therapy offices, schools, families, any place with an imbalance of power and a fear of disappointing someone. People learn to read the temperature of the room before they learn to trust their own work. And when confronted, they spend more energy calculating the social risk than reviewing whether what they did can actually hold the weight of the question.

Maybe that’s why this data point feels more about courage to me than about management. It isn’t a question of methodology, or which system of metrics a company adopts. It’s about whether, culturally, that environment allows someone to say “this didn’t work” without that sentence becoming a symbolic death sentence.

As long as honesty stays riskier than performance, there will keep being brilliant people hiding what they know behind a polished report. And no technology, however advanced, fixes that — because technology measures whatever you hand it to measure. Hand it makeup, and it hands you back makeup with a nice chart attached.

I wanted to close with some tidy sentence that ties all this together. I won’t.

Because a tidy sentence is exactly the kind of thing we use to dodge the next confrontation — including this one, with you, right now, finishing this read.

So it stays just as a question, with no cushioning, no gentle lead-in:

If someone looked you in the eye right now and said “what you did was worth nothing” — would you have a solid answer, or a ready-made excuse?

Sit with that for a second before you scroll away. Most of us already know which one we’d reach for first.

If that question landed somewhere real, there’s a lot more of this kind of conversation waiting for you at the Coaching & Você blog, at marcellodesouza.com.br.

#HRmaturity #StrategicHR #OrganizationalCulture #ConsciousLeadership #PeopleManagement #OrganizationalDevelopment #marcellodesouza #marcellodesouzaoficial #coachingevoce

Marcello de Souza | Coaching & Você marcellodesouza.com.br © All rights reserved