Leaders rarely lack ambition. They lack a week that matches the ambition. Strategy lives in a deck; the calendar is still a pile of exceptions. Ninety days is long enough to change the week and short enough that nobody can hide behind a transformation programme.
We use ninety days as a design constraint, not a slogan. In that window you can diagnose what is actually stalling growth, install a cadence, run it three or four times, and see whether it holds when we are not in the chair. Anything shorter is a workshop. Anything much longer becomes a project with a name and no owners.
If the operating system cannot survive a month without us, it is not an operating system. It is a visit.
What we mean by an operating system
Not software. Not a new OKR tool. An operating system is the smallest set of rituals, rights and numbers that keep quality high while volume rises.
- A weekly focus meeting with an agenda short enough that people show up prepared.
- A monthly review that looks at levers, not a tour of every dashboard.
- A quarterly reset that is allowed to kill work, not only add it.
- Decision rights: who decides, who is consulted, which topics are no longer a group sport.
- A scoreboard of a few numbers the whole team can see without a data team in the room.
That is the whole machine. Teams add more because more feels like control. More is how the calendar fills with meetings that re-decide last month.
The ninety-day shape
Days 1–21 are diagnosis. We sit in the real meetings, read the funnel as it is, and map how work actually moves — not how the org chart says it moves. The output is a one-page picture of the bottleneck: conversion, pricing, focus, or a team that cannot decide.
Days 22–45 are design. We write the cadence, the scoreboard and the rights with the people who will run them. If a ritual cannot be explained in a paragraph, it will not survive August.
Days 46–90 are live fire. We run the new week with you. We cut the meetings that do not earn their time. We watch where the team quietly reverts, and we fix the design rather than blaming “culture”.
On day 90 the test is simple: can the team run the next cycle without us in the room? If the answer is no, we have built a dependency. That is a failure of Momentum, not a reason to stay forever.
What we refuse to install
Frameworks that need a priest. Traffic-light packs nobody reads. A second strategy meeting disguised as “alignment”. Tools bought to postpone a conversation about owners.
We also refuse the opposite failure: a beautiful 90-day plan with no operating rhythm behind it. Direction without Momentum is a document. Momentum without Direction is a very efficient way to do the wrong work. They belong together; they are not the same job.
How you will know it is working
The first sign is not a revenue spike. It is the meeting that ends early because the decision was already owned. It is a quarter that does not start from zero. It is a hire who can be useful in week two because the work is written down.
Later, the numbers move — because effort is finally tied to a lever. That is the compounding you can feel in the calendar before you see it in the board pack.
If your team is living in exceptions, start the ninety days. Bring the messy week, not a polished brief. We will help you leave with a sequence you can run on Monday.