The four processes that elevate leadership and help teams execute with clarity.
Great leadership isn't a personality trait — it's a set of structures, run consistently. These four processes give leaders a real operating system: one that spots drift early, keeps goals and people aligned, and installs the rhythm that lets a team compound instead of just keep up.
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 — and nothing holds each person accountable to their manager, either.
The weekly meeting drifts into status theater. The OKRs live and die in a document no one opens. Managers lose track of what's actually on their reports' plates until it's a crisis. And the operating rhythm of each department — who owns what, how often, to what standard — lives in nobody's head but the person about to leave.
These four processes exist to fix that. Together they cover four distinct jobs: reviewing what's actually happening at the leadership level, keeping company goals alive and connected to work, keeping every individual's priorities and blockers visible to their manager, and documenting the recurring operating rhythm each function runs on. 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.
Get started →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.
Get started →Monthly Priority Meeting
A monthly 1:1 between a manager and direct report to set a source of truth for the month's priorities — and understand the real workload behind them.
Get started →Your Function On One Page
A one-page definition of how each department runs — built once a year, right after annual goals are set, and rarely changes after that.
Get started →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.
"Card issuance API hit 99.95% uptime in May — on track for the Q2 launch KR."
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.
One source of truth for what
each person is actually carrying.
The Monthly Priority Meeting is a recurring 1:1 between a manager and a direct report. Its job: set a shared source of truth for the month's priorities, talk through them together, and make sure the manager actually understands the challenges, distractions, changes, and workload behind the work — not just the task list.
Priorities that live in someone's
head aren't priorities.
Weekly 1:1s drift into status updates. Annual reviews are too slow to catch real drift. The Monthly Priority Meeting sits in between — frequent enough to catch a person before they're underwater, infrequent enough that it doesn't become another status ritual. It exists to answer one question honestly every month: what is this person actually carrying, and does their manager know?
MY RADAR?
Capture what's urgent, first
Before priorities, before planning — what's on fire right now? Naming the urgent thing first clears it off the table so the rest of the conversation isn't competing with it.
Set the month's priorities together
Three to six concrete deliverables, each with a clear status. Not a wishlist — a source of truth both people agree to. When something's blocked, it's named as blocked, not quietly absorbed.
Ask what's on their radar — and what's draining them
This is where the manager actually understands the person's workload — the incident calls, the audits, the context-switching that never makes it onto a roadmap but absolutely affects capacity.
Name what to get started
One or two things worth starting before next month's meeting — captured now, while the conversation is fresh, instead of left for someone to remember later.
The Monthly Priority
Meeting, fully structured.
A guided template for managers and direct reports — urgent items, prioritized deliverables with status, radar and distraction capture, and a running notes log across every month.
If it takes more than a page,
it isn't a strategy yet — it's a to-do list with ambition.
Your Function On One Page is built once a year, right after the company sets its annual goals. It defines the choices each department is making, what they're explicitly saying no to, and the recurring processes, disciplines, and habits the function runs on — with a minimum success path that brings clarity, speed, and autonomy. Once it's set, it rarely changes.
A document nobody reads
protects nothing.
Most departments operate on tribal knowledge — the recurring rituals, the unwritten standards, the processes that exist only in the head of whoever's been there longest. Your Function On One Page forces that knowledge onto a single page, twice: the strategic choices the function is making this year, and the ongoing operating rhythm that makes those choices scalable beyond any one person in the room.
The strategic frame — three boxes
The choices we're making (who we serve first, where we bet, what gets our best people and time). What we're saying no to (the scope and requests we've decided not to do, on purpose). The one capability we build once — the throughline every team needs, built once, sharper each time it's used.
The ongoing work — minimum scalable processes
For every recurring, cross-team ritual the function owns: name it, set a cadence, define the minimum process, and say what "good" looks like — so it runs without the function lead in the room.
| PROCESS | CADENCE | MINIMUM PROCESS | OWNER |
|---|---|---|---|
| Ledger reconciliation review | Weekly | Diff → flag → assign → close within 48h | Platform lead |
| Fraud rule review | Bi-weekly | Pull false-positive rate → tune → ship | Risk eng lead |
| Vendor compliance audit prep | Quarterly | Doc pull → legal review → sign-off | Priya S. |
Build it right after annual goals are set
The page only makes sense once company-level priorities exist — it's the function's translation of those priorities into choices, trade-offs, and one capability worth building once.
Name every recurring, cross-team ritual
Nova prompts each function lead to list the processes their team runs on an ongoing basis — review cycles, audits, planning rituals — and define the minimum version of each that still works at scale.
Revisit only when it breaks
Unlike the other three processes, this one isn't designed to be reworked monthly. Once the function's choices and operating rhythm are documented, they typically hold for the year — revisited only if the team's mandate fundamentally shifts.
Your Function On One Page,
fully structured.
The three-box strategic frame plus the ongoing-work table — guided prompts for every department, built once a year and ready to revisit whenever the team's mandate changes.
Stepping into Chief of Staff
or COO? Start here.
This one isn't part of the core four — it's a process built for a specific moment: starting in a CoS or COO role, leading a business transformation, or implementing real change in how a company operates. It draws on the same four processes above, but sequences them as a 90-day install rather than ongoing rituals.
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. Six fifteen-day phases — whether you're stepping in fresh or redesigning an organization that's already running.
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.
Four processes.
One compound effect.
Each process works alone. But they compound when they're running together — the MBR catches drift at the leadership level, the OKRs give the company something to steer toward, the priority meeting catches drift at the individual level, and the one-pager keeps each function's operating rhythm legible to anyone who joins it. The team that runs all four 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 startedMonthly Priority Meeting
A monthly 1:1 source of truth for priorities — and the workload, distractions, and changes behind them.
Get startedYour Function On One Page
The strategic frame and ongoing operating rhythm for each department — built once a year, after annual goals.
Get startedReady to install the
operating system?
All four 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.