accountability – Grandpa Bob Encouraging Leadership

We’ve all heard it, and many of us have said it.

A decision comes up. It sits right in front of someone. It falls within their role and their authority. And the response comes almost automatically.

“Let me check with my boss.”

Sometimes that’s wise. Alignment matters. Context matters.

That’s not the situation we’re thinking about here.

We’re thinking about the reflex. The lazy habit. The moment a leader has the ball and immediately hands it back up the chain.

“I’ll get back to you.”

“Let me confirm before we move…”

Ownership just left the room.

One instance feels harmless. But a regular occurrence starts to define the culture.

Decisions begin to climb instead of moving forward. Time stretches. Energy fades. Momentum slips away, one small deferral at a time.

Every time a leader defers a decision that belongs to them, the team hears something unspoken.

“I have the title. But I’m still waiting for permission to lead.”

There are reasons this shows up. A leader may have learned that their decisions will be second-guessed. A leader may want to avoid risk. In some cases, the habit settles in because it feels efficient in the moment.

It never is.

Leadership is not a forwarding function. Leadership is a decision function. When decisions don’t happen where they should, everything slows down.

Consider a different kind of decision environment.

Naval destroyers move through the Pacific at night. Visibility is limited. The stakes are high. Decisions carry immediate consequences.

Arleigh Burke commanded Destroyer Squadron 23 during World War II. He pushed his ships to full speed when it mattered, earning the nickname “31-knot Burke.”

He once said, “The difference between a good officer and a great officer is ten seconds.”

Ten seconds.

In that environment, ten seconds could determine who struck first and who absorbed the hit. There was no version of that moment where a commander paused to seek permission for a decision that was already theirs to make.

Burke’s point wasn’t about speed alone. It hinged on readiness.

A ten-second decision is formed long before the moment arrives. It’s shaped through preparation, and thinking clearly about what matters and what doesn’t. When the moment comes, the leader recognizes it and moves.

Most of us aren’t making decisions in the middle of a night battle at sea. We’re making decisions in conference rooms, over email, in conversations with our teams, and in small moments where direction is needed.

A customer is waiting. A team needs clarity. Our decision will either create movement or stall it.

In those moments, the difference comes down to a single response.

“Let me check.”

“Here’s what we’re going to do.”

The gap between these two responses is only ten seconds. But what fills that gap, or fails to, defines the kind of leader you are.

The leaders who move in those moments aren’t guessing. They’re drawing on work they’ve already done. They’ve thought through the tradeoffs. Formed principles that guide their decisions. They understand the scope of their responsibility. They trust their preparation and their judgment.

Because of that, they don’t need to look upward for every answer. They don’t need to defer decisions that belong within their role.

They lead.

Create unnecessary delays, and uncertainty spreads. Energy drains. People begin to fill the gaps with their own assumptions.

A leader who steps forward brings clarity into the room.

The next time that familiar reflex shows up, pause for a moment and ask a better question.

Is this mine to decide?

If it is, then decide. Step forward. Move.

The distance between good and great leadership rarely shows up in dramatic events. It shows up in small decisions, repeated over time, where someone chooses to act, or chooses to wait.

Burke’s destroyers didn’t win the night by waiting for permission. They won it by being ready when the moment came.

That moment is already yours.

Ten seconds. Make them count.

Photo by Hayrunnisa Görgülü on Unsplash

A fumble changes everything.

One second the play is moving. The runner has the ball. The blockers are engaged. The drive has life. Then suddenly the ball hits the ground, bodies are diving, momentum has shifted, and what was yours a moment ago is theirs.

A fumble tests everyone.

The one who dropped the ball.

The coach.

The team.

For the player who fumbled, the moment is immediate and personal. He cost his team field position, momentum, or more. He’ll think about that play long after the whistle.

His pain rarely comes from the mistake alone. It also comes from the exposure. He was carrying something important, and now everyone can see that he mishandled it.

He comes to the sideline knowing what he did.

He doesn’t need it explained. He doesn’t need the replay. He felt the ball leave his hands. He already knows what it cost.

What he doesn’t know is what comes next.

That depends largely on who’s standing on the sideline with him.

A weak coach sees only the mistake. A careless coach brushes past it. But a strong coach understands something both miss. This player, in this moment, is deciding, maybe without knowing it, whether he can still trust himself.

Correction matters. Accountability matters. But there’s a difference between a coach who corrects and a coach who restores. One addresses what happened. The other addresses what happens next.

Real leadership does both.

It says, “Yes, that mattered. Yes, you need to learn from it. And yes, you’re still capable of more than this moment.”

Correction is the easy part. The rest is belief.

People rise to the level of belief placed in them after they’ve failed. That’s one of the most dependable things about human beings. A good coach knows this. A great one acts on it.

What about the team?

They saw it.

That fumble belongs to everyone now.

Do they quietly create distance from the one who dropped the ball? Do they look away? Do they let frustration show in ways that make him feel more alone?

Or does someone move toward him?

Not to fix it. Not to instruct. Just to be close enough that he knows he hasn’t been cut loose.

Great teams are built by people who know what to do when somebody fumbles. That knowledge is built over time. Through the kind of culture a team creates long before the ball hits the ground.

That’s true in every organization, every family, every group trying to do meaningful things together.

Eventually someone will drop the ball. Someone will let something important get away. Someone will have a moment they wish they could take back.

Failure doesn’t create a team’s culture. It exposes it.

A lot of people carry the weight of old fumbles.

A business decision that went wrong.

A missed opportunity.

A sentence that should have stayed unspoken.

A responsibility handled poorly.

A relationship moment they wish they could take back.

That weight is real. The costs were real. The embarrassment was real. There’s no use pretending otherwise.

But the fumble doesn’t have to be the end of the story.

Sometimes the growth that follows a mistake runs deeper than anything that came before it. Failure exposes what needs to be seen. A weakness, a blind spot, a lapse in discipline. It creates a moment that can be used, or wasted.

That moment rarely turns on the person who fumbled. It depends on what they find when they look up.

The leader who steps in with exactly the right mix of truth and trust. The teammate who moves toward them instead of away. The voice that says you’re still capable of more than this moment.

What looks like the end of the drive is sometimes the moment the real game begins.

Photo by Tim Mossholder on Unsplash