She Said She Wasn't Sure She Could. I Was the One Who Hadn't Done My Job.

At the company I work for, we were two days from a release when a defect turned up in final testing. It had a workaround, and normally that would have been enough under our own policy to let it ship. But this one would hit every user, every time they opened a new patient encounter, many times a day, and whatever we did, we would need a hotfix immediately after anyway. The QA manager came to me and said she was concerned.

I asked her why she had not just held the release herself. She said she was not sure she could. Not that she disagreed with holding it. Not that she was uncertain about the defect. She was not sure the decision was hers to make.

I was frustrated, and it was not at her. It was at myself, because nothing about her job description was unclear. The defect met every criterion for holding a release under our own policy. What she was missing was not judgment. It was an explicit answer to whether that judgment was hers to act on, and I had never given her one.

Conventional wisdom here is usually some version of: when someone hesitates or second-guesses a call, build their confidence. Reassure them, tell them they are capable, coach them through the doubt. Almost every leader who has ever heard someone say "I wasn't sure" has reached for reassurance first, because it is the fastest thing available and it feels like the job. It is also the move that would have missed entirely what was actually wrong here.

A confidence problem and a scope problem produce the exact same sentence: "I wasn't sure." Reassurance treats that sentence as evidence of self-doubt, and if the real gap is authority, reassurance does nothing to close it. She might have nodded along and felt better in the moment, and the next boundary-adjacent call would have produced the same hesitation, because the actual undecided variable, whether the decision was hers, was never resolved. It was only soothed over.

There is a pattern I call The Drought: a person, or a whole team, who has learned that guessing without explicit permission gets punished, so nothing moves until permission is unmistakable. Not laziness. Starvation. Nobody had told her the decision was hers, so she treated the silence the way anyone standing in a drought treats an empty sky, as a no until proven otherwise.

From the outside, that recurring hesitation reads as a confidence problem that reassurance failed to fix, so a leader reaches for more of the same: more encouragement, more pep talks. The real fix never gets built. The cost compounds quietly: decisions that should resolve at her level keep escalating to mine instead, at the worst possible moments, like two days before a release. The riskier version does not escalate at all. A defect that should hold a release ships anyway, because someone assumed the call was not theirs to make and never asked.

The leaders who get this right are not the ones with more encouraging things to say. They stopped treating "I wasn't sure" as an invitation to reassure, and started treating it as a question that needed an actual answer.

The fix was not reassurance, and it was not a private grant of authority to her either. It was a documented decision matrix visible to everyone around the decision, so when she made a call and told the room, nobody was surprised it was hers to make. Reassurance is the easier move: it takes five minutes, it feels like leadership, and it costs nothing to say out loud. Writing down who owns what, and making sure everyone she would have to answer to had actually read it, was slower and a lot less satisfying in the moment.

The Drought is not beaten by one person handing down permission in private. It is beaten by explicit, distributed decision rights that make the rain predictable for everyone standing in the field, not just the one person who happened to ask.

Once that matrix existed, something changed that reassurance never could have. She knew that anyone she would have to explain her decision to had already read the same document saying it was hers to make. That is what I mean by Invisible Leadership in reverse: private reassurance is invisible, it happens between two people and builds nothing anyone else can see. A shared, visible answer to whose call it is builds trust the whole room can act on, not just the one person who heard it.

Think of the last person who told you they were not sure about a call. What did you give them: encouragement, or an actual answer to whose decision it was, one that everyone around them would recognize too? If you cannot say for certain they would get the same answer from three other people in the room, you gave them the first one.

Quiet Confidence has more on why invisible effort, reassurance given privately, never builds what visible clarity does: http://TheQuietConfidenceBook.com