Operating notes
How to install a weekly operating cadence in 30 days.
A team with meetings is not a team with a cadence. Here is the difference, and how to build the second one in a month.
9 min read · By Everton Paula · Ler em português →
Walk into most growth-stage companies and you will find a full calendar. Standups, syncs, one-on-ones, an all-hands, a planning session that runs long. The calendar is not the problem. The problem is that none of it adds up to a cadence.
A cadence is a fixed weekly rhythm where every meeting has a named owner, a named input, and a named output, and where the meetings connect to each other. A commitment made on Monday is checked on Friday. A number that moved the wrong way on Friday becomes the problem worked on Wednesday. Without that connective tissue, meetings are just places where people report status and nobody is on the hook for anything between them.
When a founder tells me the team is busy but nothing is shipping, this is almost always the gap. The plan exists. The people exist. The operating rhythm that turns the plan into shipped work was never built. Here is how to build it.
The three-meeting week
A working cadence needs three meetings, and most teams need to delete a handful of others to make room. Three, not seven. Each one does a different job.
Monday: the commitment meeting
Thirty minutes. Each operating lead states the one to three things they will ship this week and the number each one moves. Not a status update on last week. A commitment for this week, said out loud, in front of peers. The output is a short written list of commitments with names against them. That list is the contract for the week.
Mid-week: the problem meeting
Sixty minutes, Wednesday. This meeting does not exist to share information. It exists to solve the one or two problems blocking the week's commitments. The input is the list of blockers raised since Monday. The output is a decision on each, with an owner and a date. If nothing is blocked, the meeting is cancelled that week. A problem meeting with no problems is a tell that people are not committing to anything hard enough to get stuck.
Friday: the wrap
Thirty minutes. Each lead reports what shipped, what slipped, and what is blocked going into next week. Shipped against the Monday commitment, in plain terms. The output is a one-paragraph written wrap that the founder or the board sponsor reads over the weekend. Slipped commitments roll into Monday with an explanation, not a shrug.
The scorecard underneath
A cadence runs on numbers, not opinions. Before the three meetings mean anything, each operating function needs one scorecard with a small set of metrics, and every metric needs exactly one owner. Not a committee. One name.
The discipline that matters here is restraint. A scorecard with thirty metrics is a dashboard, and dashboards get watched, not run. Pick the four or five numbers per function that the team would actually change behavior over. Map each to the person who can move it. When a number on the Friday wrap is off, there is no question about who owns the fix, because the scorecard already named them.
The scorecard is also what keeps the founder out of the meetings. Once each number has an owner and the owner reports it in the rhythm, the founder does not need to be the person chasing it. That is the entire point. The cadence exists to get the founder off the daily decision tree, not to give the founder a better seat at it.
The 30-day install
You do not roll this out all at once, and you do not pause the business to plan it. You install it live, over four weeks, and you expect the first two to be rough.
Week 1: run it badly on purpose
Stand up all three meetings the first week, before the scorecards are clean, before the format is right. The first Monday commitment meeting will be vague. The first Wednesday will surface the wrong problems. Run them anyway. You learn more from one clumsy real cycle than from a month of planning the perfect one.
Week 2: fix the scorecard
By the second week you know which numbers people actually reach for and which ones nobody can produce. Cut the metrics no owner can pull. Add the one or two everyone kept asking for. Assign every remaining number a single owner. The scorecard stops being aspirational and starts being the thing the meetings run from.
Week 3: tighten the handoffs
Now make the meetings connect. Monday commitments should appear by name in the Friday wrap. Wednesday decisions should close out blockers raised on Monday. If a commitment never gets checked, the loop is broken and the cadence leaks. Week three is where you seal the leaks.
Week 4: step back
By the fourth week, the operating leads should run all three meetings without the founder in the room. That is the test. If the rhythm only works when the founder chairs it, you have not installed a cadence, you have installed a dependency. Week four is when you find out which one you built.
The three ways it fails
Most cadence installs fail in one of three predictable ways, and all three are avoidable if you name them up front.
Cadence theater. The meetings happen, the format looks right, but no commitment ever has a real consequence for missing. People learn that the wrap is a performance, and the rhythm becomes a weekly tax with no output. The fix is to let one missed commitment be an honest, named conversation in the next Monday. Once the team sees the loop has teeth, the theater stops.
The meeting nobody preps for. A cadence runs on inputs prepared before the meeting, not generated in it. When people show up to assemble the scorecard live, the meeting balloons and the decisions get worse. The input has to be ready before the room opens. Protect that and the meetings stay short.
The scorecard nobody owns. A number with two owners has no owner. The moment a metric is shared, both people assume the other has it, and it drifts until it shows up broken on a Friday. One name per number, every time, even when the honest answer is that the right owner has not been hired yet.
Why this is the first thing we build
At Plenor, the weekly operating cadence is usually the first system installed in an engagement, because almost nothing else holds without it. The metric tree needs a place to be reviewed. The vendor scorecard needs a room where its numbers get acted on. The 30-60-90 plan needs a rhythm that checks it. The cadence is the frame the rest of the operating engine hangs on.
It is also the system that most directly does the job the founder hired for, which is to stop being the bottleneck on every cross-functional decision. A founder who installs a real cadence gets their week back. That is worth more than any single fix it produces.