Stop Blaming the Behavior

When something isn’t working, organizations often focus on the behavior they can see: Work slipped again and the team didn’t deliver what they said they would.

Leadership concludes that the team needs to be more accountable.

Sometimes that’s fair, but accountability can become a convenient explanation for a system problem because behavior rarely exists in isolation. It emerges from the environment people are operating in.

That means a more useful question is often: What conditions are making this outcome likely?

Behavior is often a signal

Compass™ treats behavior primarily as an expression of organizational conditions rather than as an independent target for improvement.

Imagine a team that repeatedly misses commitments.

From the outside, the problem looks straightforward. The team committed to something and they didn’t deliver it.

So the response becomes:

• “We need better accountability.”

• “Teams need to honor their commitments.”

• “We need stronger delivery discipline.”

But what if:

• Priorities routinely change after the commitment is made?

• New urgent work enters and nothing comes out?

• Leaders continue to add work without reconciling what has already been promised?

• Dependencies appear late?

• The team is expected to preserve the original commitment even though the conditions under which it was made no longer exist?

Under those conditions, the missed commitment is real but it may not primarily be an accountability problem.

The organization may be changing the commitment without saying so

A commitment only means something within a set of assumptions.

• We expect this work to remain important.

• We expect roughly this amount of capacity to be available.

• We expect these dependencies to behave a certain way.

• We expect competing work not to displace it.

• We expect the organization to make tradeoffs when those assumptions change.

Then reality changes: A new executive priority arrives. A production issue consumes capacity. Another customer need becomes urgent. A dependency slips.

People are reassigned, the deadline remains the same, and the original commitment is still treated as though nothing happened.

At that point, the organization hasn’t preserved the commitment. It has changed the conditions while preserving the expectation. Those are not the same thing.

Accountability without reconciliation creates bad behavior

When priorities change but commitments don’t, teams eventually adapt.

• They may stop believing commitments are meaningful.

• They may quietly absorb additional work.

• They may work around the process.

• They may overstate what they can accomplish because saying no is more difficult than missing later.

• They may stop surfacing tradeoffs because previous tradeoffs weren’t actually considered.

• They may simply wait to see which priority survives.

Then leadership sees those behaviors and concludes that the organization needs more accountability.

But those behaviors may be learned responses to an environment in which priorities move faster than commitments can be reconciled. The organization is teaching people that the stated plan is temporary while still evaluating them against it.

Accountability still matters

None of this means teams shouldn’t be accountable for commitments. They should. But meaningful accountability requires clarity about what the commitment actually is.

If circumstances materially change, there are choices to make.

• Keep the original commitment and remove something else.

• Change the commitment.

• Add capacity.

• Accept additional risk.

• Change the sequencing.

• Decline the new demand.

There may be other options depending on the situation. What matters is that the tradeoff becomes explicit.

A changing environment doesn’t eliminate accountability. It creates a need to reconcile the commitment .

Without that reconciliation, organizations can accidentally create a system where everything remains a priority, every commitment remains intact, and every new demand is simply added on top. Then they are surprised when people fail to deliver all of it.

This is where conditions matter

The team may be the place where the missed commitment becomes visible but the conditions producing it may exist somewhere else.

• How does new demand enter?

• Who can change priorities?

• What happens to existing commitments when that occurs?

• Does anyone have to make the tradeoff explicit?

• Is capacity visible?

• Are dependencies understood?

• Can teams challenge a new demand without appearing resistant?

• Does leadership distinguish between an unchanged commitment and a commitment whose underlying conditions have materially changed?

Those questions tell us much more than simply asking whether the team delivered on time.

The environment teaches people what commitments mean

Organizations continuously teach people how seriously to take commitments. Not through posters or process definitions but through experience.

• People learn whether a commitment will be protected once it is made.

• They learn whether new work requires an explicit tradeoff.

• They learn whether raising a capacity concern leads to a real decision or simply a reminder to “figure it out.”

• They learn whether priorities actually have an order or whether everything important is effectively number one.

Eventually, behavior adapts to those signals and then the behavior becomes evidence of the conditions the organization has created.

Leadership shapes those conditions

This is where leadership has enormous influence. Leadership does not have to personally manage every commitment, but leaders shape the environment in which commitments are made and changed.

• They determine whether priorities are actually reconciled.

• They influence how demand enters the system.

• They establish whether teams can surface tradeoffs honestly.

• They decide whether capacity is treated as a constraint or an inconvenience.

• They create the expectation that when something meaningful changes, the organization makes a new decision rather than pretending the old one still holds.

That shifts the question from: How do we make teams more accountable for meeting their commitments? to: Are we creating conditions in which commitments can actually remain meaningful?

That’s a much harder question. It’s also usually a much more useful one.

Ask what makes the behavior make sense

When a team repeatedly misses commitments, the temptation is to address the visible behavior immediately.

Before doing that, ask: What would have to be true for this pattern to make sense?

• Maybe the team is overcommitting.

• Maybe estimates are poor.

• Maybe execution discipline really is weak.

Those possibilities shouldn’t be dismissed but neither should the organizational conditions surrounding the commitment.

• Did priorities change?

• Did demand increase?

• Did capacity decrease?

• Did dependencies move?

• Were tradeoffs actually made?

• Was the commitment ever reconciled?

Those questions help distinguish an accountability problem from an environment that continually makes commitments obsolete while continuing to measure people against them.

If the conditions keep changing, asking people to “be more accountable” may not solve the problem. It may simply make them accountable for contradictions the organization itself has not resolved.

Compass™ by StrategiX helps organizations understand the conditions shaping their outcomes—and identify where meaningful improvement is possible.

If that sounds like a conversation worth having in your organization, send me a message.