Urgency Always Has a Voice. Importance Needs a Room.

The Issue that has Outgrown your Problem Solving

What is the issue in your business right now that has moved beyond simple problem solving?

Not the issue a direct report can fix with clearer ownership. Not the problem a manager can solve by asking better questions. I mean the one that crosses departments, exposes competing priorities, and keeps coming back because no single person can resolve it alone.

Maybe it is a growth opportunity the company is not yet built to absorb.

Maybe it is a lost customer, a new contract, a financing decision, a capacity problem, an acquisition conversation, or the sudden absence of a key leadership member for health or fiduciary reasons.

Whatever it is, you can usually feel when an issue has outgrown ordinary problem solving.

It starts becoming the elephant in the room.

That is when founders usually say they want a more effective leadership team.

And they are right to want one.

Because this is where a leadership team either becomes more aerodynamic or starts creating drag.

Urgency Always Has a Voice. Importance Needs a Room.

A good leadership meeting is not another demand on the company’s time. It is where the company trades scattered time and energy for a focused decision-making ritual. It is the room where priorities are inventoried, sequenced, discussed, decided, owned, and reviewed. Where the right issue is uncorked at the right time, instead of poured out across the week until it loses its force.

Urgency always has a voice.

Importance needs a room.

And near the end of this article, I’ll share a short audit a leadership team can use to ask a sharper question: are we becoming more aerodynamic, or are we creating drag?

The Quick Question Habit

I have had to learn this personally.

I am guilty of the “quick question” interruption. For years, I could treat a question as harmless because I needed to get something off my chest. I would hand someone a half-formed thought, interrupt their priority, and, without always realizing it, ask them to hold my uncertainty while still trying to return to the work that mattered before I walked in.

The question was rarely quick. The return trip to focus was even less quick.

What I needed was not always an immediate answer. Sometimes I needed a place to capture the question. Sometimes I needed a shower, a workout, or a walk before the real question appeared. Sometimes I needed to write the issue down, think through the second-order consequences, and bring it to the next meeting where a decision could be clearly defined as the outcome.

I behave differently when I am dealing with law firms on matters billed by the hour. I do not interrupt their workflow every time a thought arrives. I look for written status, collect my questions, and bring them into the planned meeting when a decision is needed.

That discipline should not only exist when the clock is expensive. It should exist because attention is expensive.

John Glon, a coach in my Bloom Growth™ community, shared the example of a founder in a delivery business who had become the go-to person for every question. Clients and team members would swarm him the moment he walked into the office, so his solution was to avoid the office altogether and work from home. Once the leadership team installed a weekly meeting with real accountabilities, the flow changed. Important issues started getting routed into the meeting instead of landing on him all day. He protected his time, re-engaged with the office, and the team’s output picked up.

Scattered Urgency Feels Productive. It Isn’t.

The danger for founders and CEOs is that scattered urgency feels productive. Everyone is talking. Problems are being handled. Decisions appear to be moving. But activity is not the same thing as forward motion, and responsiveness is not the same thing as leadership.

A company can be filled with communication and still be starving for clarity.

This is where the weekly leadership meeting gets misunderstood. The point is not to have another meeting. The point is to protect one room where the right issues are required to appear, where the right people are present (i.e., no distractions), and where the team can make decisions with enough context to keep the same problems from returning next month in different clothes.

When Complexity Changes Shape

This is especially true in companies that have crossed the point where the founder can no longer be the best context for every function. In the $8M to $10M range and above, complexity often changes shape. More people are involved. More departments touch the same issue. More decisions carry second-order consequences. The question is no longer, “Who can solve this problem?” The question becomes, “How does this leadership team improve its decision-making and mutual accountability together?”

Without that room, the company still meets. It just meets everywhere: Slack, texts, doorways, side calls, “quick questions,” and the founder’s head at 3 a.m.

That is not a decision rhythm. It is a reaction loop.

And reaction loops are expensive. They create context switching. They diffuse attention. They make every issue feel equally urgent because there is no trusted place to decide what actually matters. The team may be busy, even exhausted, but the business is not necessarily becoming clearer.

The leadership team becomes less aerodynamic. More drag enters the system.

Two Traps Leaders Fall Into

One pattern I see in founder-led companies is that leaders tend to fall into one of two traps. They either under-drive the operating rhythm because they do not want to seem rigid, or they over-absorb business decisions because they want to protect the outcome.

Both create dependency.

The first allows the meeting rhythm to soften until urgency takes over. The weekly meeting gets moved, shortened, skipped, or treated as optional because everyone is “too busy.” The problem, of course, is that the team is often too busy because there is no strong enough rhythm to organize the work.

The second trap is quieter. The founder keeps absorbing decisions that the leadership team needs to learn how to make (: Guilty). The founder reviews the deck one more time. Approves the vendor call. Weighs in on the client issue. Resolves the tension between departments. Answers the finance question. Names the priority.

At first, it feels responsible.

Over time, it trains the company to wait.

That is the difference between being useful and becoming the hidden operating system.

The founder does not intend to create dependency. Most founder dependence begins as care. Care for the customer. Care for the standard. Care for the team. Care for the economics. Care for the reputation that took years to build.

But care without transfer of ownership becomes a bottleneck.

The mature move is to build a leadership team capable of carrying more of that care through better rhythm, clearer ownership, and stronger decisions.

Guardrails, Not Preferences

This is where discernment matters.

Some things should be driven with real discipline. A weekly leadership meeting should happen on the same day and at the same time. The meeting should start on time and end on time. The scorecard should be reviewed. Issues should be named clearly. Before an issue is discussed, the desired outcome should be described. Priorities should be connected to annual goals. Decisions should leave the room with an owner and a date. Follow-through should be reviewed. Financial visibility should not arrive so late that the company has already lived the consequences.

Those are not preferences. They are rails.

A founder, CEO, or coach should be willing to drive those rails with conviction. But the content inside those rails belongs to the leadership team.

The CEO should not become the substitute for the team’s judgment. The coach should not become the consultant who makes the client’s business decisions. The leadership team has to learn how to think together, not merely escalate upward with better manners.

That sounds simple until the new routine gets awkward.

If you think a CEO or leadership team can start this kind of rhythm and make it stick like a ritual without snapping back into old habits, you have another thing coming. The first weeks are clumsy. People second-guess the agenda. Someone wants to skip because “this week is unusual.” Someone asks whether the meeting really needs the full time. Someone wants to solve the issue in a side conversation instead of bringing it to the room.

Where the Coach Fits, and Where They Don’t

That is exactly where a coach is needed.

Not forever. But early.

I protect the best practices long enough for the team to feel the value of the ritual. I hold the standard when the room gets uncomfortable. I also notice when the team is drifting into status updates, avoiding the hard issue, or handing the decision back to the founder. A member of the team can facilitate later, but that person is still a participant with divided attention, context switching, personal stakes, and a role to defend.

That is a poor recipe for full participation when the room needs everyone’s best thinking.

The better posture is to let the coach protect the rhythm while the team learns to own the decisions.

Inside that rhythm, the questions become sharper:

• What are we actually deciding?
• What information do we need?
• Who owns the outcome?
• What happens if we do nothing?
• Is this reversible or permanent?
• What signposts will tell us we are on the right road?
• What issue keeps coming back because we have only been treating the symptom?

That last question matters because recurring issues rarely return in the same clothes. Sometimes they look like a missed follow-up. Sometimes they look like a cash squeeze. Sometimes they look like a team member waiting for permission. Sometimes they look like the founder saying, “It is faster if I just do it.”

That reflex, “it’s faster if I just do it,” gets expensive fast.

I know because I have said versions of it myself. Most founders have.

It feels efficient in the moment. It feels like protecting the standard. But repeated often enough, it becomes the reason the company cannot make decisions without the founder.

The Decision Factory

A meeting is not effective because it ended early. It is effective because something important no longer has to come back next month.

John also described a client meeting where the team appeared to move quickly. A client issue surfaced, the team hustled, and the immediate problem was fixed. On the surface, the meeting looked efficient. But the issue came back because no one had asked why it kept happening. The real problem was that the entire client-retention process ran through one person. Once the team saw that, they rebuilt the process so multiple people could triage and support clients instead of letting every issue funnel through a single bottleneck.

A fast meeting can still avoid the hard work. A meeting reimagined as a Decision Factory does the opposite. It turns reality into decisions.

The team looks at the scorecard because numbers reveal where attention belongs. It reviews priorities because priorities are promises against the annual plan. It identifies issues because unresolved tension is where tomorrow’s drag is hiding.

Then, before the team discusses, it names the outcome.

Are we solving? Deciding? Assigning ownership? Removing an obstacle? Choosing between options? Setting a signpost?

Once the desired outcome is clear, the team discusses until the real issue is clear enough to decide.

Then the leadership team decides.

Status gets traded for movement. Repeated conversations get traded for permanent decisions. Founder dependence gets traded for shared ownership.

This is the work of making a leadership team more aerodynamic.

That is the trade.

Is Your Leadership Team Aerodynamic, or Creating Drag? Assess yourselves.

Where urgency is winning

1. Which urgent issues are actually recurring issues we have not solved permanently?
2. Where are we allowing urgency to dictate the agenda instead of protecting time for what matters most?

Where meetings are underperforming

1. Are our weekly meetings creating decisions, or mostly collecting updates?
2. What issue did we discuss last month that still has not changed?

Where the CEO is absorbing

1. Which decisions still wait for the CEO before they move?
2. Where is the CEO’s memory, judgment, or approval acting as the process?

Where leaders create drag

1. Where am I solving so quickly that no one else has to think?
2. Where am I protecting the standard in a way that prevents ownership from transferring?

The pattern matters more than any single answer.

If most answers point to recurring issues, repeated conversations, decisions waiting on the CEO, and meetings that collect updates more than create movement, the team is creating drag.

If the answers point to clear outcomes, real decisions, named owners, visible follow-through, and issues that stop recurring, the team is becoming more aerodynamic.

These questions are not meant to shame anyone. They are meant to locate drag.

Every leadership team has some. The question is whether the team has the discipline to see it, name it, and reduce it before another quarter becomes a repeat of the last one.

When the Meeting Starts to Drift

The point is not to make meetings sacred. The point is to make importance visible.

Urgency will always have a voice. It will knock, ping, interrupt, escalate, and demand the floor. The test of a leadership team is not whether urgency disappears. It is whether the team has a room strong enough to keep urgency from scattering across the company.

When the seas get rough, do not scatter.

Return to the room.

That is the reminder.

The Drift Remedy

Here is the simple version:

3 Moves

Name the outcome before the discussion begins. Are we solving, deciding, assigning ownership, removing an obstacle, choosing between options, or setting a signpost? If the team does not know the desired outcome, the discussion will wander until the loudest urgency wins.

Move the issue into the room. Do not let the real meeting happen in Slack, texts, hallway conversations, side calls, or the founder’s head at 3 a.m. Capture the issue. Bring it to the weekly leadership meeting. Let the right people see it together.

Leave with owner, date, and decision. A discussion that ends without ownership is just a shared observation. A useful meeting turns reality into movement.

2 Traps

Under-driving the rhythm. This happens when the CEO or leadership team does not want to seem rigid. The meeting gets moved, shortened, skipped, softened, or treated as optional because “this week is unusual.” Then urgency quietly becomes the operating system again.

Over-absorbing the decision. This happens when the CEO protects the outcome by becoming the shortcut. The founder reviews, approves, rescues, clarifies, decides, and carries the tension. It feels helpful in the moment. Repeated often enough, it trains the company to wait.

1 Rule

Be rigid about the room. Do not absorb the decision.

The room, rhythm, scorecard, issue list, outcomes, owners, dates, and follow-through need discipline. Those are the rails. But the leadership team still has to do the thinking. The CEO cannot remain the place where every unresolved issue goes to be rescued.

That is why a coach is so valuable in the early reps. Not forever. But long enough to protect the best practices when the new rhythm feels awkward, slow, overly structured, or easy to abandon. A coach keeps the room from snapping back into old habits while the team learns to make better decisions inside it.

That is the work.

Focused judgment replaces scattered urgency. Status becomes movement. Repeated conversations become permanent decisions. Founder dependence becomes shared ownership.

That is how a leadership team becomes more aerodynamic.

A rigid and thorough weekly meeting rhythm gives the team evidence. Over 13 weeks, the leadership team should be able to look back and see what was achieved in the quarter that actually propelled the company toward its annual goals. Not what was discussed. Not what was busy. What moved.

Which priorities advanced? Which decisions held? Which recurring issues stopped recurring? Which responsibilities moved out of the founder’s head and into the team? Which conversations became clearer because they finally had a room?

That is the value being traded for the team’s time.

As the Clarity Sommelier, I listen for that trade. If the value of the meeting is described only as “good,” that is not enough. Good is too vague. A leadership team should be able to say the meeting made the company clearer, calmer where it had been reactive, faster where it mattered, and more capable of deciding without everything routing back through the same person.

That is the standard.

This thinking was sharpened by Katie Oliva ’s recent article on leaders becoming absorbers instead of drivers, and by a Bloom Growth coaching-community conversation about urgency, meeting discipline, and the discernment required to know when to drive the operating rhythm and when to let the leadership team own the decision. Special thanks to John Glon for sharing field examples that helped make the pattern more concrete.

If your team cannot look back over 13 weeks and see which decisions moved the company toward its annual goals, the meeting rhythm is not yet a Decision Factory.

It is still a calendar event.