Leadership and the operating system · Answered by Golden Section from more than 400 B2B software companies observed
Hold executives to outcomes inside a system rather than to your attention. Give each leader a seat with three to five written outcomes, a few weekly numbers with a target beside each, and no more than three to five quarterly priorities, each with a definition of done agreed before the quarter starts. Then read those in a fixed 90-minute weekly meeting where on-track or off-track is the whole report, and the remaining hour goes to solving the top issues. Micromanaging is what fills the gap when none of this exists. Pick one operating framework, install it whole, run it in a tool such as Ninety.io, and give someone other than you the job of running the rhythm. Start by asking each leader to name the company's three priorities this quarter and their owners.
Inspect the outcomes every week and leave the method to the owner. Step into the work only when a number stays off-track past its agreed date, and then through the issues list or the consequence ladder, not around the leader.
| Metric | Value | What it means | Source |
|---|---|---|---|
| Weekly scorecard | 5 to 15 numbers | leading measures, each with one owner and a targetif populating it takes one person more than an hour on Monday, it is the wrong scorecard | Golden Section playbookExecution Operating System |
| Quarterly priorities | 3 to 5 for the company; no more than 3 to 5 per person | things the company will finish this quarter, each with an owner, a date and a definition of donea list of twelve priorities is a list of none | Golden Section playbookExecution Operating System |
| Priority completion target | 80% | share of quarterly priorities finished on timetwo quarters below it points to a capacity conversation, not a speech about accountability | Golden Section playbookExecution Operating System |
| Weekly leadership meeting | 90 minutes: 30 reporting, 60 solving | fixed agenda, same day and time every weekjudge a framework after four quarters; two quarters is the installation | Golden Section playbookExecution Operating System |
Founders micromanage when they cannot see whether the work is on track any other way. Without a scorecard, the only instrument is asking; without written priorities, every request feels urgent; without an issues list, the same four problems resurface every week. Experienced executives often find this structure juvenile, because they ran teams inside someone else's system and never had to build one. Thirty people outside the leadership meeting still cannot read the founder's head.
The framework matters less than the parts. The Execution Operating System play installs them in one go: seats, scorecard, quarterly priorities, the meeting rhythm and an issues discipline, and recommends Ninety.io to run them, with the weekly meeting held inside the tool. The KPI dashboard supplies the weekly numbers, and the KPI and strategic meetings play keeps minutes and action items, which become evidence of a managed company when a buyer asks. When a leader keeps missing, the consequence ladder moves it out of the meeting and onto a dated plan. The founder's job is to submit to the system in public, because a founder who cannot be measured teaches everyone that measurement is for other people.
This company is invented. A founder at $5M in annual revenue checks in on each of five leaders daily and still feels surprised at month end. Asked for the quarter's three priorities, the five leaders give eleven different answers. The team picks one operating framework, sets it up in Ninety.io, runs a two-day launch session and comes out with an accountability chart, a scorecard of 12 weekly numbers and four company priorities with written definitions of done. The COO owns the rhythm. The founder stops the daily check-ins and reads the scorecard on Monday instead. By the third quarter the team completes 75% of its priorities and has cut the list from five to four to make room.
A leader new to the seat, or one on a written improvement plan, warrants closer contact for a defined period, and that is coaching rather than micromanagement if both sides know the end date. And a company of eight people needs only three parts of this now: a weekly meeting with a fixed agenda, five numbers with owners and targets, and three priorities a quarter.
From the Golden Section mistakes list, each paired with the play that prevents it.
Without an operating system, the only accountability tool left is the founder's attention, which is what micromanagement is.
Stepping into a leader's process after handing it over tells the whole team that the leader's authority is optional.
When the same issues come up week after week, the meeting is reporting rather than solving.
Accountability needs one owner per outcome; ambiguity about roles makes every miss a negotiation.
In the order we would run them. Each is on its own page, most with a free Excel template.
Installs seats, scorecard, priorities, the weekly meeting and the issues list as one system.
Supplies the weekly numbers with owners and acceptable ranges.
Sets the meeting roles and minutes that make accountability visible and auditable.
Handles persistent misses through dated, written steps instead of founder intervention.
Executive plays The operating system, dashboard, meeting and performance plays that replace founder attention with structure.
Same day, same time, 90 minutes, fixed agenda. Spend the first 30 minutes on the scorecard and priorities, read as on-track or off-track only, plus headlines and last week's to-dos; spend the last 60 working the issues list from the top. Close by capturing to-dos, the message to cascade and a rating for the meeting.
Three to five for the company and no more than three to five per person, each with one owner, a due date inside the quarter and a definition of done written before the quarter starts. Write down what is explicitly deferred and tell the company. If you finish fewer than 80% for two quarters, you are setting too many or the wrong ones.
As a goal-setting method inside an operating system, not as the system itself. OKRs make ambition specific and align a product team well, but they say nothing about who owns each seat, which meeting reads the numbers or how issues get solved. Adopt them only if you are also building those parts. Which operating framework you choose matters less than running one consistently.
Usually because nothing converts it into what a named person does this week. Strategy becomes execution through seats with owners, a weekly scorecard, a short list of quarterly priorities and a meeting that solves issues. When rollouts stall, check the calendar first: the founder stopped attending, a quarterly session was postponed, or the system never reached the teams below the leadership team.
Put one name on every outcome that matters and make the result visible weekly. Two names on a seat is zero owners. Then follow through the same way every time a number stays red, using the issues list first and a written consequence ladder if it persists.
We recommend Ninety.io for most companies. It holds the one-page plan, the accountability chart, the weekly scorecard, quarterly priorities, the issues list and to-dos, and runs the weekly meeting inside the tool against a timed agenda, which is the feature that matters. It supports several frameworks, so the choice of framework and the choice of tool are separate decisions.
Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-10-22. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.