Before Blaming the Person, Check the Conditions

Reader’s Moment: Maybe you have been inside something called a team that did not feel like one.

The word was there.

The meetings were there.

The shared pressure was definitely there.

But the structure underneath it was thin. Information moved poorly. Authority sat somewhere else. Expectations changed without warning. Trust was assumed instead of built. People were told to collaborate, but the reward system quietly trained them to protect themselves.

Then, when the work started to wobble, someone pointed at the people inside the mess and said, “The team failed.”

That is too easy.

One of the useful lessons from Organizational Behaviour is that people do not perform in empty space. They perform inside conditions. Inside systems. Inside roles. Inside norms. Inside reward structures. Inside communication patterns. Inside the gap between what an organization says it values and what it actually tolerates, rewards, punishes, or ignores.

That matters on the ledge.

Because collapse is often treated as a personal event. You broke down. You failed. You could not handle it. You should have communicated better. You should have been more resilient. You should have carried more.

Sometimes there is truth in personal responsibility. We still have to look at our choices. We still have to repair what is ours to repair. We still have to ask whether we communicated clearly, acted honestly, or missed a warning light.

But responsibility is not the same thing as accepting every verdict handed down by a broken structure.

A better question is this:

What conditions made failure more likely?

That question does not excuse everything. It sharpens the diagnosis.

If a team is highly interdependent, then communication is not decoration. It is infrastructure. If one person’s work becomes another person’s starting point, then handoffs matter. If one department makes promises another department must fulfill, then authority, responsibility, and resources need to meet in the same room.

If they do not, blame will travel downstream.

That is one of the oldest patterns in pressure systems. Responsibility slides toward the people closest to the work. Authority stays higher up. Credit rises. Blame spreads sideways. The people carrying the actual load are left trying to solve problems they did not create, with tools they were not given, under standards they did not design.

Then the organization calls that teamwork.

It is not.

Real teamwork can handle reality. It can handle someone saying, “This deadline does not match the resources.” It can handle someone saying, “The process is failing.” It can handle someone saying, “We are being asked to self-direct without real authority.” It can handle disagreement without turning every concern into disloyalty.

Decorative teamwork cannot do that.

Decorative teamwork wants the feeling of unity without the discipline of structure. It wants the language of collaboration without the cost of clarity. It wants people to be flexible, loyal, positive, and available, but it does not always want to examine whether the system is making success possible.

That is where the warning lights begin.

When people stop raising problems because honesty is punished, that is a warning light.

When the reliable person becomes the dumping ground, that is a warning light.

When “team player” means “absorb more without asking questions,” that is a warning light.

When the stated value is wellness but the real norm is constant availability, that is a warning light.

When a body gets sick and the first response is moral judgment instead of practical adjustment, that is a warning light.

Standing on the Ledge keeps coming back to the same principle: evidence before shame.

So before deciding that a person failed, check the conditions.

Was the goal clear?

Did the person have the authority to affect the outcome?

Was information shared early enough to matter?

Were the norms healthy, or were people trained into silence?

Was trust real under pressure, or only assumed while things were easy?

Was the team built for the work, or was the word “team” pasted over a bad design?

Those questions do not make accountability weaker. They make it cleaner.

Because the point is not to avoid responsibility. The point is to put responsibility where it belongs.

Sometimes the next clean move is personal repair.

Sometimes it is a better conversation.

Sometimes it is a boundary.

Sometimes it is a redesign.

Sometimes it is finally admitting that the system was asking human beings to operate like shock absorbers for problems no one wanted to name.

A team is not healthy because it uses team language.

A team is healthy when its structure lets people tell the truth, carry the work, repair mistakes, and remain human under pressure.

That is the bridge from the learning journal back to the ledge.

Check the conditions.

Name the pattern.

Repair what is yours.

Stop accepting shame for bad architecture.

Godspeed.