Sep 8, 2026

Don't Start With Accountability. Start With Curiosity.

Accountability matters, but applying it before understanding what changed can harden the wrong diagnosis and make the real problem harder to solve.

A manager listening attentively to an employee during a quiet one-on-one conversation

A manager reaches the end of their patience.

The employee has missed another commitment. Communication has become inconsistent. Work that once moved without intervention now requires repeated follow-up.

The next step seems obvious:

“We need to hold them accountable.”

That may be true. But accountability is not a diagnosis. It is a response—and responses work best when they are aimed at the right problem.

When a previously reliable employee changes, beginning with accountability can make the situation look decisive while leaving the most important question unanswered: What changed?

Accountability and curiosity are not opposites

Curiosity can sound too soft for a serious performance problem. Managers may worry that asking more questions will communicate that expectations are optional or give the employee room to make excuses.

But good diagnostic questions do not remove responsibility. They clarify what the employee is responsible for and what may be preventing the expected behavior.

There is a difference between saying, “It is fine that this did not get done,” and asking, “This used to get done reliably. What is different now?”

The first lowers the standard. The second tries to explain the gap.

Accountability still has a place. Curiosity helps ensure that it is applied to the actual failure rather than the most visible symptom.

A clear standard can still produce the wrong conversation

Imagine an employee who has managed client handoffs successfully for two years. Over the last two months, deadlines have started slipping and other teams no longer know when work will arrive.

The manager prepares a direct conversation: handoffs must happen on time, communication needs to improve, and another miss will have consequences.

Those expectations may be entirely reasonable.

But suppose the employee’s role changed three months earlier. They now need approval from two leaders before completing each handoff. Those leaders regularly give conflicting direction, and neither owns the final decision.

The employee still has responsibility. They may need to escalate conflicts earlier or communicate delays more clearly. But “be more accountable for deadlines” is incomplete if the operating process no longer allows them to control those deadlines.

Without curiosity, the conversation treats the employee as the only variable. The standard is clear, but the diagnosis is not.

Premature accountability hardens the first story

Once a conversation is framed around accountability, both sides tend to defend a position.

The manager presents the evidence that the employee is falling short. The employee explains the conditions making the work difficult. The manager hears excuses. The employee hears a conclusion that was reached before the conversation began.

That dynamic makes new information harder to absorb.

If the employee says priorities keep changing, it can sound like blame-shifting. If they describe unclear authority, it can sound like resistance. If they mention workload, it can sound like an inability to prioritize.

Some explanations really are avoidance. But you cannot tell which ones are avoidance merely because they appear during an accountability conversation.

When the first goal is to understand, you can test an explanation. When the first goal is to correct, every explanation risks being treated as a defense.

Ask questions that create evidence

Curiosity is useful only when it moves the situation toward clarity. A vague “How are things going?” may produce a vague “Fine.”

Ask about the change you can observe and the sequence around it:

  • “You handled this independently last quarter. Where does the process slow down now?”
  • “Which part of the work became harder first?”
  • “What decision can you no longer make that you could make before?”
  • “When priorities conflict, whose direction are you using?”
  • “What have you tried, and where does it stop working?”
  • “What part of this is within your control that you have not addressed?”

The last question matters. Diagnostic curiosity should examine the environment and the employee’s response to it. Otherwise, it can become a search for reasons the standard should not apply.

Good questions reveal both kinds of information: what changed around the employee and what the employee did after it changed.

Name the shared facts before deciding what they mean

Many difficult conversations become unproductive because the manager and employee are arguing over interpretation before agreeing on the pattern.

Start with what both sides can examine.

The handoffs were previously on time. The approval process changed in June. Delays began in July. The employee raised the conflict twice but did not clearly tell downstream teams that dates were at risk. The two leaders continued giving incompatible direction.

That picture does not eliminate accountability. It distributes it more accurately.

Leadership may need to clarify decision authority. The employee may need to escalate sooner and communicate risk instead of waiting for resolution. The manager may need to stop measuring a deadline as if one person still controls the whole process.

Now the accountability conversation can be specific. It can address behavior the employee can change while also fixing conditions that keep reproducing the problem.

Curiosity needs a stopping point

Understanding more does not mean investigating forever.

Sometimes the role is workable, expectations are clear, support is available, and the employee continues missing reasonable commitments. Sometimes the employee understands the problem but does not change their behavior. Sometimes a previously strong fit has genuinely deteriorated.

Curiosity should lead toward a credible hypothesis and a testable next step.

You might clarify authority, reset scope, repair one working relationship, or define a more concrete expectation. Then observe what changes. If the obstacle is removed and the behavior remains, that is stronger evidence about the employee’s part in the problem.

The purpose is not to postpone a hard decision. It is to make the decision on better information.

Better diagnosis creates stronger accountability

Weak accountability relies on broad demands:

Take ownership. Communicate better. Show more urgency. Step up.

Strong accountability can say what needs to change, why it matters, what conditions have been clarified, what support is available, and what the employee now controls.

That precision is difficult to reach if the manager begins with a verdict.

When a good employee goes off track, start by reconstructing the change. Ask what happened before the visible decline. Separate structural friction from the employee’s response. Decide which explanation fits the sequence, then set expectations around the part that actually needs to change.

Curiosity does not weaken accountability.

It keeps accountability from solving the wrong problem.

That is the diagnostic discipline TeamClarity is built to support: understand the situation clearly enough that the next move is both fair and effective.

TeamClarity

Have a real case? Submit it.

If this pattern feels familiar in a real employee situation, the TeamClarity preview now includes an early-access case submission section you can use to share what changed.

Share This Essay