Saying Nothing Is Still a Decision

A deadline for a deliverable slips by a few days. A document comes back close, yet not quite what was asked for. A team member starts skipping the parts of a project that they feel are optional, even if they weren’t. In each case, a manager has to weigh saying something against keeping quiet. Often, they choose the second option, telling themselves they’re being patient or that it’s not worth the friction over something small.

Avoiding accountability can appear deceptively calm or compassionate. It’s accepting the deliverable after the deadline without comment. It’s the manager editing the document into shape after it’s submitted, instead of explaining what needs to change and handing it back. It’s praising the parts of a project that went well while turning a blind eye to the parts that didn’t, hoping that it self-corrects.

Letting things slide feels like neutrality, yet it’s anything but. Each of these choices is understandable in the moment. However, stacked up over time, they teach a team that the stated standard and the enforced standard are two different things, and teams tend to calibrate to whichever standard is actually enforced. Staying quiet is itself a decision, and it’s one that the whole team ends up living with.

What does holding the bar mean?

Many people are familiar with the concept of “setting the bar,” which is defining expectations and what success looks like before the work begins. Holding the bar is the less famous second step. It means clearly naming what should and should not be accepted, approved, or allowed to drift. The key is to identify it early enough that it’s still a small conversation instead of a large one. It’s not about being tough or hard to please. The standard itself has to be defined, realistic and meaningful. When the standard is clearly defined, the manager’s job is to adhere to it, not wait to privately notice when it’s been missed.

Rarely do managers skip this step because they lack standards. It’s often because they view being “direct” and “harsh” as the same thing. Useful accountability is direct, not harsh: it names the specific gap between the expectation and the outcome, restates the standard in plain terms, and leaves the relationship intact or sometimes even stronger because the other person now knows exactly where they stand.

Find the gap before naming it

Before raising an issue, it’s crucial to be specific about where the gap lives. A general sense that “something’s off” leads to a vague, hard-to-receive conversation. Running the situation through the six facets of accountability below identifies something concrete enough to actually name.

Outcome: Did this move what matters? Is the conversation about a miss on an outcome or a miss on the process?

Behavior: Did the way the work got done strengthen or weaken the system around it? How did it impact trust, the process, or how the next person picks this up?

Prioritization: Which tasks are being chosen? Is something else being set aside to make room for it?

Learning: What’s known now that changes the decision? Does that change what should happen next?

Alignment: Is this aligned to strategy, priorities, and decisions needed? Or has a decision already been made and not communicated?

Ownership: Who owns the recommendation? What’s the next move from here?

Running through these questions takes only a few minutes and can change the entire discussion. A gap in outcome calls for a different opening line than a gap in prioritization, and naming the right one is what makes the conversation feel respectful instead of a complaint.

When kindness isn’t always kind

Knowing the framework doesn’t automatically make the conversation easier to start. That part is internal. Radical Candor author Kim Scott has a name for the instinct many managers act on instead: ruinous empathy. It’s caring about someone’s feelings in the moment so much that the information they actually need gets withheld. It appears as kindness while costing the other person the chance to fix something while it’s still minor.

A few mindset shifts can make it easier to work through, such as:

Treat silence as a choice with a cost, not a neutral option. Saying nothing doesn’t alleviate the gap. It simply moves the cost to someone else, like a teammate covering the difference, or a person having to unlearn a bigger version of the habit down the line.

Notice the gap between the dreaded conversation and the actual one. Most accountability conversations end up smoother than the version envisioned beforehand. Pay attention to that difference after the fact and note one best practice that makes the next one easier to start.

Practice the distinction between direct and harsh. It helps to say the sentence out loud alone beforehand and notice whether it sounds like an accusation or a plain statement of fact. Focus on the words and the tone. Most direct feedback, said once out loud, sounds far more matter-of-fact than it felt internally.

Remember what silence costs the other person. Withholding a correction isn’t protection from a hard moment. All it does is delay the conversation and usually makes the problem worse. Addressing a gap early is one of the more respectful things a manager can do.

Holding the bar can feel like the opposite of caring about the relationship. However, holding someone accountable in a timely manner with clear feedback and follow-through can actually be the clearest sign of it.

When have you struggled to hold the bar with a team member? What’s the best way that you have been held accountable in the past? 

Leave a comment below, send us an email, or follow us on LinkedIn.