The No-Homework CEO Operating Model
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 7
- Confidence
- —
Ravi's model for founder time rests on a trade: by withdrawing from problem-identification and problem-solving, the founder accepts that parts of the business run twenty to thirty percent worse than they would with his involvement, and bets that concentrating on his highest-output work more than covers the loss. The mechanism has three parts — hire thought leaders who bring their own ideas rather than order-takers, speak less in meetings so the team's own thinking has room to develop, and route the founder's remaining input through a single operations lead or chief of staff. When the founder is involved, it is in a condensed session where the team brings the problem and the KPIs, he supplies a solution, and he leaves with no homework.
Origin
Extracted from Deep Dive with Ali Abdaal
How to run it
- 1
Name your zone of genius and defend it
Ravi's is creating content, creating products and creating hype and culture. Everything else — coaching calls, support, billing, question-answering — is delegated, even inside his own membership.
Pro tip Design work so one output serves two: turn a well-performing video into a class, or pull a class into a video.
- 2
Hire thought leaders, not executors
Pay more for people who bring ideas to the table instead of waiting for answers. Ravi's example of the reverse is video editors who gave zero input; his counter-example is an editor who proposed a shared brand style guide unprompted.
Pro tip A company's growth is limited by the cumulative knowledge of the people inside it — every seat can add to that total.
Watch out A company where only two or three people think is carrying what enterprise calls key man risk.
- 3
Spend fewer chips in meetings
Ali's framing from Multipliers is that a leader is a poker player with a finite number of chips, spending some each time they speak. Ravi does not run his Friday team leader meetings — he sits quietly and contributes only when asked or when it is genuinely valuable.
Pro tip Ravi's own annual peer feedback goal was simply to speak less in meetings.
Watch out If you talk the whole time, the room stops thinking; when you go quiet, silence may follow for weeks.
- 4
Let wrong solutions run
When the team proposes a solution Ravi believes is wrong, he now lets them execute it so they learn from the mistake. He is candid that this is the part he struggles with most.
Watch out Solving the problem yourself each time limits and handicaps the team's development.
- 5
Route input through one person
Follow the Rob Dyrdek pattern of coaching a single chief of staff or general manager, who then works with department heads. Instead of dealing with departments, you deal with one person a few times a week.
Pro tip When you notice a problem, direct it through that person rather than messaging the team member directly.
- 6
Insist on solutions, not problems, being brought to you
The target state is the general manager arriving with the issue, the cause, the solution already implemented, and a request for feedback — rather than a problem for the founder to diagnose.
Pro tip High-level CEOs Ravi has spoken with rarely identify or solve problems themselves; they are informed and asked for feedback.
- 7
Concentrate involvement into a quarterly session
Once a quarter, the general manager presents a problem area with KPIs, the founder and product lead work the solution in one sitting, and the team executes without further founder involvement. You leave with no homework.
Pro tip Four condensed sessions a year can move the business more than continuous shallow involvement.
Watch out If you end up doing the research and the follow-up conversations, the leverage disappears.
In the wild
Ravi hired a director of operations who had run three-hundred-plus person teams at CrossFit and Nike. The day after onboarding, the new director sat in on the regular marketing meeting. Afterwards Ravi asked for critical feedback and was told bluntly that the amount he had talked during the meeting was shocking. Ravi's instinct was that of course he should talk — he is the face of the brand and the marketer. The feedback landed anyway, and speaking less in meetings became his number one personal goal from that year's annual review.
→ A shift from founder-as-answer-machine toward a team expected to generate its own solutions.
Ali described becoming more disciplined about directing issues through Angus, his general manager, rather than messaging a team member directly when he notices something odd — such as the support inbox receiving three hundred emails a week. Ravi's improvement on that was for Angus to arrive with the number, the cause, the solution already implemented, and a request for feedback. Ali also noted Angus telling him he had played too many chips in a recent content meeting, the exact behaviour the model is designed to reduce.
→ Fewer founder interventions and a general manager who arrives with answers rather than questions.
Common mistakes
Solving every problem you can see
Ravi is explicit that the more he takes over, identifies problems and solves them, the more he limits and handicaps the team. Visible competence from the founder produces invisible dependence in everyone else.
Hiring cheap executors to save money
A team of order-takers concentrates all thinking in two or three people, which is key man risk. Paying more for people who contribute ideas raises the company's total knowledge and therefore its ceiling.
Refusing to accept degraded output
Withdrawal means things run worse in the short term. Ravi, self-described as somewhat OCD about details, had to accept imperfection to reach the numbers he wanted.
From the transcript
“But the way I like to say it is you have no homework.”
“the more I take over, the more I identify problems, and the more I solve problems, ironically enough, the more I'm limiting and handicapping the…”
“if you spend a little bit more money and find somebody who's truly a thought leader, meaning that they bring their own ideas to the…”
From the episode
$25m CEO Coaches me on How to Grow our Business - Ravi Abuvala: Scaling with Systems
Ravi Abuvala: Scaling with Systems