The three processes that make a leadership team actually work.
Most leadership teams are held together by calendars and goodwill. These three structured processes replace that with a real operating system — one that spots drift early, keeps goals alive, and installs the rhythm that lets the company compound instead of churn.
Most leadership teams don't fail because of bad people or wrong strategy. They fail because nothing holds the company accountable to itself month after month.
The weekly meeting drifts into status theater. The OKRs live and die in a document no one opens. The planning cycle happens once a year, briefly creates alignment, and then the company goes back to running on whoever shouts loudest. And without a deliberate structure to hold things together — the operating system defaults to the CEO's calendar and a shared sense of vague urgency.
These three processes exist to fix that. Together they cover three distinct jobs: reviewing what's actually happening, keeping goals alive and connected to work, and installing the structural foundation that lets everything else hold. Each one can be run independently. Each one compounds when the others are running too.
A note on adaptability: Every process in Nova is designed to evolve. As your team meets, as your context changes, as you learn what's working — the process adapts with you. These aren't rigid frameworks locked to a playbook. They're living structures your team can adjust as you go.
Monthly Business Review
A monthly leadership meeting built to spot drift before it becomes a quarter-killer — and decide what to do about it. Not status. Not round-robin. Decisions.
Learn more →OKRs & Operating Cadence
A four-week sequence to set company goals, cascade them honestly, and embed a review rhythm that keeps them alive all quarter — not just on launch day.
Learn more →First 90 Days as CoS / COO
Six fifteen-day phases that install the operating system a growing company needs. Replaces "learn and add value" with a structural sequence that actually holds.
Learn more →Spot drift before it
becomes a quarter-killer.
The Monthly Business Review is a 90-minute meeting for the full leadership team. Its job is not status updates. Not round-robin presentations. Not a recap of what already happened. Its one job: spot what's drifting, and decide what to do about it.
Two things. Only two things.
Every leadership meeting eventually collapses into status theater unless someone draws a hard line around what it's for. The MBR has two jobs and no others: surface what's drifting off track, and make the decisions that correct it. Everything else — the catching up, the general updates, the "exciting things happening in our team" — belongs somewhere else.
Silent
Pre-read & annotation
The meeting opens in silence. Everyone re-reads the packet and writes their questions and comments directly into the shared doc. No one talks. This is not optional — it's the move that makes everything else work.
OKR signal walk
Brief pass through each company-level OKR. Not a status update — a signal read. Is this on track, drifting, or stalled? Flag the drifting ones. The drifting ones go into the Issues block.
Metrics review
Three to five leading indicators the team agreed to track. Not a dashboard walk — specific flag-and-discuss. What moved? What didn't? What's the signal behind the number?
Core
Issues that matter
The bulk of the meeting. Two or three issues — the ones that came out of the silent read and the OKR walk — get real airtime. Not "let's discuss." Each one gets a named owner and a decision before moving on. This is where the meeting earns its place.
Action items & log
Every decision made in this meeting gets logged — in the room, before the meeting ends. Owner. Deadline. No "let's follow up." Logged means it happened.
Meeting rating
Before leaving: each person rates the meeting 1–10. Not to be polite — to build the habit of honest process feedback. Over time, this data tells you whether the MBR is actually working.
Each leader: green / yellow / red on each KR they own. One sentence each. No explanation unless red. Reds drop into the issues list.
Walk the input metrics, not just the outputs. The CFO or CoS leads. Anything off-trend gets two minutes — what it means, what to investigate. Anything that needs a real decision drops to the issues list.
Prepare the packet before the meeting
Nova guides the facilitator through building the pre-read packet — OKR status, key metrics, flagged issues — all in one structured document. It goes out to the team 24 hours before the meeting. No pre-read, no participation.
Run the meeting in structured sessions
Nova walks the facilitator and team through each block with time guidance and prompts. The silent reading period is built in — not as a suggestion, but as the structured opening of every session.
Log decisions as they're made
Every decision gets logged before the Issues block closes — with an owner and a deadline. The decision log lives in the shared doc, visible to the whole team after the meeting ends.
Carry forward into next month
Open action items from this MBR automatically surface at the top of next month's pre-read. Nothing falls through. The meeting compounds rather than resets.
The full Monthly
Business Review process.
Pre-read builder, meeting facilitation guide, silent reading block, decision log, and carry-forward tracker — all structured as a multi-session process in Nova's process library.
Goals that stay alive
past launch day.
OKRs die in most companies within three weeks — because they get installed without the rhythm that keeps them relevant. This process builds both: company-level objectives set by the CEO, cascaded honestly through the leadership team, and embedded into a weekly, monthly, and quarterly cadence that actually reviews them.
OKRs without a cadence
are just a list.
The problem isn't the framework — it's the missing infrastructure. OKRs need a working weekly sync, a monthly check, and a quarterly reset to function as a steering mechanism. Without those, they're aspirations that survive the Q1 kickoff and disappear by week three. This process installs both the goals and the rhythm underneath them.
CEO writes three company-level OKRs
Three Objectives. No more. Each with two to three Key Results — each KR a number, not an adjective. "Grow revenue" is not a KR. "Generate $500K in new ARR by end of Q" is. Nova guides the CEO through drafting and pressure-testing each one before they go to the team.
Leadership team cascades with honest friction
Each leader takes the company OKRs and sets their own. Friction is expected and welcome — "we can hit two of these three at current resourcing" is not resistance, it's the most valuable conversation the team can have. OKRs that don't surface real trade-offs are not OKRs. They're theater.
All OKRs visible in a shared space
Every team's OKRs in one place where every other team can see them. Misalignment is easy to fix when it's visible and invisible when it isn't. This week is about surfacing the conflicts before the quarter locks in, not discovering them at the monthly review.
Lock the OKRs and embed in cadence
Finalize and start. The OKR review goes into the weekly sync, the Monthly Business Review, and the quarterly planning cycle — riding on the cadence that already exists, without adding new meetings. This is what makes OKRs compound rather than decay.
OKRs don't review themselves. They need a deliberate set of forums at four time horizons — each with a specific job, each connected to the others. This is the rhythm that keeps the goals alive.
Leadership Sync
Decisions, blockers, and signal. OKR check-in as a standing item. 60–75 minutes. No round-robin status.
Blocker & Progress Check
Cross-functional unblocking between the weekly syncs. Fast, focused, 30 minutes max. No new decisions.
Business Review (MBR)
OKR signal review, metrics, issues that matter. Where drift gets spotted and corrected before it compounds.
Planning & Reset
Retrospective, new OKRs, explicit not-list, cascade plan. Four hours that set the next quarter's direction.
OKRs & Operating
Cadence, fully structured.
The four-week OKR install sequence, company-to-team cascade guide, cadence design templates, and embedded review prompts — all in one multi-session process.
Install the structure that lets the
CEO stop being the operating system.
The first 90 days as a Chief of Staff or COO aren't about learning the company and getting a quick win. They're about installing the structural foundation that lets the company run on systems instead of on one person's brain and calendar. This process gives you the phased playbook to do that — whether you're stepping in fresh or redesigning an organization that's already running.
Indispensable feels like
the goal. It isn't.
The Chiefs of Staff who stay stuck are the ones who become the calendar, the inbox, the translator between every pair of leaders who can't be in a room together. They get praised for it. And then they get trapped by it — because they built themselves into the system instead of building the system that runs without them. This process is about building the operating system. Not becoming it.
01 · Listen
Map reality without committing to anything. 30 conversations, 5 consistent questions, one decision log started.
02 · Install
Fix the most important leadership meeting from the inside. One structural ritual that holds and earns trust.
03 · Cadence
Make the full rhythm of business visible. Remove three to five meetings. Build the four-layer cadence.
04 · Conflict
Navigate the first real cross-functional break through structure — not diplomacy. Log the decision the org accepts.
05 · OKRs
Install company goals now that the foundation can hold them. CEO sets three. Everyone cascades honestly.
06 · Review
Run a full planning cycle. Pre-read, meeting, retro, carry-forward. The operating system compounds or collapses here.
Each phase runs as its own structured session
Nova breaks the 90-day playbook into six distinct sessions — one per phase — each with its own facilitation guide, templates, and clear deliverables. You finish Phase 1 knowing exactly what to carry into Phase 2.
Every template is pre-built and ready to use
The listening tour question set, the decision log (five columns, ready to fill), the weekly sync rebuild template, the OKR install sequence — everything is built in. You run the process, not the admin that usually surrounds it.
Adapt the process as your context changes
No two organizations are the same. As you move through the phases, you and your team can reshape any part of the process inside Nova — adjusting the cadence, the meeting formats, the OKR structure — to fit what's actually true about your company.
The complete First 90 Days
playbook, pre-built.
Six 15-day phases, every template ready, every cadence wired up. Whether you're a new CoS stepping in, or an existing leader redesigning the org — this process gives you the structural sequence that holds.
Three processes.
One compound effect.
Each process works alone. But they compound when they're running together — the 90-day install builds the cadence that the MBR runs inside, and the OKRs give both of them something to steer toward. The team that runs all three builds an operating system that outlasts any single leader, any single quarter, and any single crisis.
Monthly Business Review
Spot drift before it becomes a quarter-killer. 90-minute monthly meeting for the full leadership team.
Get startedOKRs & Operating Cadence
Company goals that stay alive all quarter, embedded in a four-layer review rhythm that compounds over time.
Get startedFirst 90 Days as CoS / COO
Six phased sessions that install the operating system. Not "add value" — install the structure that runs without you.
Get startedReady to install the
operating system?
All three processes are available in Nova's process library — fully structured, with facilitation guides, templates, and multi-session flows that adapt as your team and context evolve.