I Sat Through Dozens of Weekly Leadership Meetings.The Same 5 Failures Showed Up Every Single Time.

I’ve spent the last several months deeply embedded in the operations of a multi-company portfoli the kind of setup where one founder runs 40+ entities across ecommerce, healthcare, real estate, and services.

I’ve watched their weekly L10 meetings. I’ve read the transcripts. I’ve seen the scorecards.

And I noticed something that should terrify every operator: the same five execution failures showed up in every single team meeting, week after week, for months.

• Different teams. 

• Different departments.

• Different people.

• Same problems.

Nobody noticed because the meetings kept happening. That’s the dangerous part , the rhythm of a weekly meeting creates the illusion of progress.

You show up, you review numbers, you assign tasks, you say “let’s fix it next week.” Then next week arrives and you’re having the exact same conversation.

Here’s what I saw. And more importantly, here’s what it taught me about why most companies don’t need better goals, they need execution enforcement.

Failure #1: Running Meetings With the Wrong Scorecard

In one e-commerce operation I observed, the team ran their weekly L10 meetings with incorrect KPIs for over a month.

The head of the company said it plainly in the January meeting: “This will be the last level 10 we do where the KPIs are incorrect.” It wasn’t.

The next week, same wrong KPIs. The week after that, same wrong KPIs. They kept postponing the “scorecard reset meeting” first to Saturday, then Tuesday, then “tomorrow at 8 AM,” then the following Saturday.

By mid-February, the founder was still asking for the meeting to redo the scorecard.

Meanwhile, the team kept reviewing numbers that didn’t measure anything meaningful.

They tracked total suspended accounts (98% of all accounts were suspended — 165 out of 168), expired inventory, and appeal submissions.

But nobody flagged the obvious: if 98% of your accounts are dead, your scorecard should be screaming. Instead, the team just read the number and moved on.

What’s actually broken:

There’s no mechanism to enforce that a broken scorecard gets fixed by a deadline.

The “fix the KPIs” task lived in conversation, not in a system. It had no owner, no due date, and no consequence for slipping. So it slipped. Repeatedly.

The deeper problem:

When your measurement system is wrong, every decision downstream is wrong too. You can’t course-correct what you can’t see.

And the longer you run with broken metrics, the more normalized it becomes. Three weeks into bad KPIs, it stops feeling urgent. That’s when damage compounds silently.

Failure #2: Reporting Vanity Metrics While the Business Bleeds

At one point in a February meeting, the team reported $6,000 in “net sales” for the week.

Sounds decent. Then the founder asked a simple question: “What does net sales mean again?

Because when you guys say net, that’s not the same net in my mind.”

Turns out, “net sales” meant total revenue minus platform fees and refunds.

• Not net income.

• Not profit.

• Just revenue with some deductions.

The actual net income for the week? About $900.

The founder’s response was direct: “You could have net sales and have negative income.” He was right.

And the fact that the team had been reporting “net sales” as their primary metric without ever surfacing the actual profit number meant the founder had been making decisions based on a number that told him almost nothing about business health.

What’s actually broken:

The scorecard wasn’t designed to surface what the decision-maker needs. And there was no review process to validate that what gets reported actually drives decisions.

Metrics drifted from “useful” to “comfortable” The team reported what was easy to calculate, not what mattered.

Failure #3: Tasks With No Home

In a completely different team under the same company a medical services operation the founder asked a simple question: where are you tracking the tasks I assign?

Silence. Then honesty.

One team member admitted, “We don’t really have a way to store them.

Normally what I do is when I’m working on one, I’ll just get it done and send it over to you.”

Another pulled up their project management tool. It was full of tasks that had expired months ago.

Nobody had updated it.

The founder already knew the answer before he asked.

He said: “If the task is small, they’ll just get it done right now. But if something comes up, then it disappears and it’s going to fall through the cracks.”

He was describing the exact failure mode of every team that relies on memory and good intentions instead of a system.

Small tasks get done because they’re top of mind. Anything that requires more than 30 minutes of effort or depends on someone else? Gone.

The team’s solution?

A Google Sheet. Pinned to the top of their WhatsApp chat.

I’m not judging that it’s practical.

But here’s what happened: the operations lead volunteered to manually pull tasks from WhatsApp messages, add them to the sheet, assign them, message each person individually, and track deadlines.

One person became the human enforcement layer for the entire team’s task management.

That works until it doesn’t. And it usually stops working when that one person gets busy, takes a day off, or simply forgets.

What’s actually broken:

The company had ClickUp. They had tools. But nobody enforced usage.

The tools became graveyards of expired tasks because there was no system that required people to interact with them. Task management was optional, so it was abandoned.

Failure #4: The CEO Becomes the Bottleneck

This was the most revealing pattern across every meeting I observed.

The founder of this portfolio runs 40+ companies. He should be the least operationally involved person on any team.

His words: “I’m supposed to be the least available person.”

But in reality, he was the most available person on every call. And not by choice by necessity.

His e-commerce team needed him to authorize wire transfers with one-time passwords. They’d message him mid-meeting, asking him to stop whatever he was doing and provide an OTP that expired in five minutes.

He described it bluntly: “You’re basically saying stop intubating the patient, stop talking to the attorney, stop talking to the billionaire, and give me my OTP.”

His medical team needed him to assign tasks because nobody else would.

His ecommerce team needed him to vet sales hires because nobody else understood sales. His operations team needed him to provide identity documents and facial verifications for new accounts.

He was the approval bottleneck, the verification bottleneck, the hiring bottleneck, and the decision bottleneck. All at once. Across multiple companies.

The wire transfer problem eventually got solved with two person authorization at the bank one person initiates, the CEO batch-approves once or twice daily.

But that fix took weeks of meetings to surface because nobody framed it as a process problem. They kept treating it as a “bother the CEO faster” problem.

What’s actually broken:

When systems don’t enforce delegation and process, everything escalates to the founder.

Not because the founder wants it they explicitly don’t but because there’s no mechanism that allows work to flow without their involvement.

Every approval, every verification, every decision becomes a human bottleneck disguised as “being involved.”

Failure #5: The Infinite Tomorrow

Across every team, every meeting, the most dangerous phrase was: “Let’s do that tomorrow.”

The KPI reset was tomorrow.

The inventory liquidation list was “I’ll get it to you.” The projection sheet would be “represented back to you” once the profit bar was added. The sales hire review would happen “when I come back.” The end-of-day reports would start “next Monday.”

The ClickUp tasks would be updated “this week.”

In one meeting, the facilitator, a professional EOS implementer, had to remind the team to send their daily wrap-up reports.

She said it gently: “I don’t want to really tag you every now and then, but just do it before you log off.”

The fact that a facilitator has to ask adults to do a basic accountability practice tells you everything about the enforcement gap. It’s not that people don’t want to do it. It’s that nothing happens when they don’t.

• No system flagged the missed reports.

• No escalation triggered. 

• No consequence materialised.

The task just... floated. And next week, the same reminder was given again.

The founder understood this at a visceral level. He’d been running a private label ecommerce operation for six years and had never seen a dollar of net profit.

Not because the products couldn’t sell, but because the financial reporting was never enforced. Months with zero activity were simply excluded from reports, making everything look better than it was.

Problems persisted for years because nobody surfaced them.

His words: “I can’t solve any problems if I don’t know they exist because nobody’s giving me the information.”

What’s actually broken:

There’s no enforcement mechanism between “we said we’d do it” and “it actually got done.”

OKRs exist on paper. Tasks exist in conversation. Deadlines exist as suggestions.

And the gap between intention and execution grows wider every week, completely invisible until the damage is too big to ignore.

The Pattern Behind the Pattern

Here’s what all five failures have in common: they’re not strategy problems. The teams I observed weren’t confused about what to do. They had goals.

They had KPIs (even if wrong ones). They had weekly meetings with professional facilitation. They even had project management tools.

What they didn’t have was enforcement.

No system that automatically flagged when a scorecard hadn’t been updated in two weeks. No mechanism that escalated when the same task appeared in three consecutive meeting agendas without resolution.

No process that prevented the CEO from becoming a human OTP machine because delegation wasn’t enforced at the system level.

The founder I observed runs  40  companies. He said something in one meeting that stuck with me: “All 40 companies except these two give me dedicated books proper month-by-month financials.”

The two that didn’t?

They were the ones with the most meeting time, the most discussions, and the least execution.

More meetings didn’t fix it. More conversations didn’t fix it. More tools didn’t fix it.

What would fix it is a system that doesn’t let these things slide. One that treats a missed KPI update the same way a bank treats a missed payment with an automatic escalation, a visible flag, and a clear consequence.

That’s why I’m building ShiftFocus OS. 

Not another OKR tracker that lets teams set goals and forget them.

An execution enforcement platform that makes sure what gets said in Monday’s meeting actually gets done by Friday.

Because the meetings aren’t the problem. The silence between them is.

If your weekly meetings sound like the ones in this article same problems, different week that’s not a people problem. That’s a systems problem. And it’s exactly what ShiftFocus was built to solve.