The framework was never the problem.

The pattern is the same in many places. A leadership team diagnoses slow execution and concludes it needs a better goal framework. OKRs, KPIs, V2MOM, or whatever was published last month. They align on it, roll it out and schedule the review meetings.

Then nothing changes.

The framework was never the problem.

Have a framework. Use it consistently. Then move on.

A goal framework is a good thing. You need something that connects your North Star to individual initiatives and gives everyone a common language. Whether that is OKRs or something else matters much less than the debate suggests. Pick one, use it consistently, and stop discussing it.

But a framework is scaffolding. It does not build the house. If execution is broken, swapping one framework for another is rearranging deck chairs.

Execution was already winning. The gap is widening.

The world moved fast before AI. Now, what used to take a team three months can often be prototyped in days. The bottleneck is less and less capability. It is the organisation’s willingness to move.

You could once compensate for slow execution with a better strategy. That window is closing. When everyone has access to the same tools and the same talent, the company that executes fastest has the advantage.

Speed dies in the decision rights.

If the framework is not the problem, what is? Most often: who is allowed to decide what, and what happens to them when they do.

You can hear it in the phrase “Let me schedule a meeting about that.” Nobody says it because a meeting is needed. They say it because someone once decided on their own, and was corrected in public. That one moment became the culture:

1. Someone acts without checking upward.
2. The CEO finds out and reacts badly. Everyone notices.
3. Next time, it gets checked with the CEO first.
4. The CEO is copied on everything and becomes the bottleneck.
5. The CEO complains that nobody takes ownership.

It looks like an accountability problem. It is a decision rights problem with a fear layer on top.

Most CEOs can draw the decision rights matrix. Very few can watch someone make a call they disagree with, and say nothing.

The fix has two parts. Define which decisions live at which level. Then let those decisions stand, even when you would have decided differently. The first part is a workshop; the second is the hard part. A simple version is enough to start with:

Decision	Decides	Input, before a deadline	Informed
Price changes	Head of commercial	Sales, finance	Everyone, via the price list
Payments below threshold	Finance lead	—	Monthly overview
Initiative scope, within a cycle	Initiative owner	Team	Leadership, at cycle review
New market entry	CEO	Leadership team	Board

Don’t pause. Find the two-way door.

Even with clear decision rights, people hesitate when they are unsure of the consequences. The instinct is to wait: gather more input, think it over, take it to the next meeting.

What is usually needed is not a pause but a reversible move. Most decisions are two-way doors: if you walk through and don’t like what you see, you can walk back. So the question is not whether to do it, but how to do it so you learn without significant damage:

• Test on a smaller group before everyone.
• Roll out gradually, one team or market at a time.
• Make sure there is a quick way to roll back.
• Negotiate the right to cancel a vendor contract during the test period.

Some decisions really are one-way doors and deserve the time. Far fewer than get treated that way.

“Let’s wait and think about it” is the wrong answer. A concern is legitimate; waiting is not a way to address it. Your culture should push people to answer a different question instead:

How can we address my concern and still test this tomorrow?

Put the blinders on.

In Danish we call them skyklapper: the blinders you put on a horse so it looks at the road ahead. Execution needs exactly that.

Watch how a working group dies. A problem shows up and you form a small team: three people, a clear mandate. Someone asks whether finance should be in the room. Legal wants visibility. A market says it is affected too. Soon you are twelve people, and the group has gone from solve this to represent everyone’s interests. Those are opposite missions.

“Have we involved legal?” adds a week. “Has finance approved?” adds a week. Five of those questions and the sprint is dead.

Execution teams need full mandate, including deciding who to involve and who not to. When people complain that they were not consulted on something outside their scope, that is not a process problem. It is a cultural one, and leadership has to address it.

One caveat: regulated businesses cannot bypass compliance. But regulation is not a free pass to move slowly. Clarifying up front who decides, who advises and who must be consulted lets you move fast even there, instead of discovering the rules halfway through.

Business understanding is not optional.

Whoever leads an initiative needs a firm grasp of the unit economics, the customer problem and the operational constraints, and must be senior enough to decide without escalating. If your product owner mostly collects information and brings every issue back to a steering committee, you have built a relay race where you needed a sprint.

That also takes transparency. People cannot make good business decisions without the actual numbers. “This margin data is confidential” is said far more often than there is a real reason for it. If that is how your company works, change it.

Make the framework serve speed, not reporting.

Start with a clear North Star. What are we building, and which numbers are we moving? If the team cannot answer that in one sentence, fix it before anything else.

Then run short, ruthless cycles:

• One to two weeks of planning. Proposals, prioritisation, approval, team set-up.
• Four to six weeks of execution. Heads down. Blinders on.
• One to two weeks of cool-down. Finish properly, and avoid piling up technical and process debt.
• Repeat.

No ninety-day roadmaps that are out of date by week three. No monthly check-ins where people present slides instead of results.