Learning Stewardship in a Culture of Urgency

Some organizations are built to move fast because they have to.

Restaurants are a perfect example.

A guest is unhappy.
A ticket is late.
A server needs help.
A table is waiting.

The restaurant environment rewards leaders who can see a problem, make a decision, and take action. In many ways, successful restaurant organizations are built around what I would call a command context.

And that’s not a criticism.

Command cultures operate with urgency. They reinforce accountability. They teach leaders to step toward problems instead of away from them.

In the early stages of growth, command cultures can be a tremendous advantage. But growth changes the leadership context.

A single restaurant succeeds by executing today.
A growing franchise must execute today while also building for tomorrow, which requires a second leadership context: stewardship.

Command asks: “What is happening, and what do we need to do right now?”

Stewardship asks: “Where are we headed, and what do we need to build?”

Both matter. But they require different instincts.

In a command context, speed is often the right response: Decide & Act.

In a stewardship context, speed can become the problem. Leaders have to slow down long enough to think, develop people, strengthen systems, and build capability before the next emergency arrives.

This is where many growing organizations struggle.
Not because leaders don’t care.
Not because leaders aren’t working hard.
But because they keep applying command instincts to stewardship problems.

A server calling out sick may require command.
A weak leadership pipeline does not.

A late ticket may require command.
A broken ticketing system does not.

A guest complaint may require command.
A company preparing for scale does not.

Stewardship requires leaders to resist the urge to react. It asks them to step out of the fire long enough to ask why the fires keep starting. That work rarely feels as urgent as solving today’s problem. That work is less visible. It is less dramatic. It may not produce results for months or years.

The leader who saves the day becomes a hero.
The leader who prevents the emergency may go unnoticed.

Yet as organizations grow, prevention becomes the work.

Restaurants will always operate in both contexts. Guests experience the brand in real time, which means command contexts will never disappear. At the same time, growth creates stewardship contexts that require leaders to develop people, strengthen systems, and build future capability.

The challenge is not choosing between command and stewardship.

The challenge is recognizing which context you are in.

When the dining room is full and service is breaking down, you are facing an operational problem (a command context).

But when the organization needs to develop leaders, strengthen systems, and prepare for growth, you are facing a capability challenge (a stewardship context).

The danger is staying in command mode because it feels productive, familiar, and rewarded.

The irony is that the skills that helped build the business can eventually limit its growth.

The leader who cannot step out of the command context eventually becomes the bottleneck the organization must grow beyond.

Great organizations learn to do both.

They preserve the urgency that made them successful while building the capability that allows success to scale. Because eventually, the measure of leadership is not how often you save the day. It’s how rarely the day needs saving.

---

Learning Stewardship in a Culture of Urgency was originally published in Horizon Performance on Medium, where people are continuing the conversation by highlighting and responding to this story.