Choosing an operating system is the easy part. Whether you pick EOS, Scaling Up, BOSS or a system of your own, the rollout is where most companies stumble. Here’s a ninety-day plan that works, and the traps to avoid.
Ground rules before you start
- Leadership team first. Don’t roll anything out to the whole company until the leadership team has run it for at least a quarter.
- One tool at a time. Each tool needs a few weeks to become a habit.
- The owner goes first. The owner’s numbers, priorities and issues get the same treatment as everyone else’s.
- Protect the weekly meeting. It’s the heartbeat. Never cancel it; reschedule within the week if you must.
- Pick an internal owner. Usually the integrator or operations leader. Someone has to own the system itself.
Days 1–30: Rhythm and numbers
Week 1: Schedule the weekly leadership meeting — same day, same time, fixed agenda. Start with a simple version: wins, scorecard, priorities, issues, to-dos. See the weekly leadership meeting agenda.
Week 2: Build a rough scorecard. Ten or so weekly numbers, an owner for each, a goal for each. Don’t wait for perfect data. See business scorecard.
Weeks 3–4: Start an issues list. Every issue raised in the week goes on it. In the meeting, solve the top three. See how to solve problems in team meetings.
By day thirty, the team should have run four weekly meetings and be getting used to reviewing numbers and solving issues together.
Days 31–60: Seats and priorities
Week 5–6: Draw the org chart by seats — the Accountability Chart in EOS, the Ownership Chart in BOSS. Define the seats the business needs, list three to five responsibilities for each, then put names in. See small business org chart.
Week 7: Hold the hard conversations the chart reveals: seats with no owner, people in the wrong seat, the owner in too many seats.
Week 8: Set the first quarterly priorities — a handful for the company, one to three per leader, each with one owner and a clear finish line. See quarterly business goals.
Days 61–90: Direction and the first quarterly session
Weeks 9–11: Draft the one-page plan: core values, focus, long-range target, a picture of the next few years and the one-year plan. See strategic planning for small business, company core values and how to write a vision statement.
Week 12–13: Run the first quarterly planning session: review the quarter, score the priorities, reset the issues list, set next quarter’s priorities and confirm the plan. See quarterly planning meeting.
After 90 days: cascade and deepen
- Quarter two: tighten the scorecard, push accountability, start documenting core processes. See process documentation.
- Quarter three: cascade to departments — each department runs its own weekly meeting and scorecard.
- Quarter four: hold the first annual planning session. See annual planning meeting.
What kills rollouts
- The owner overrides the plan. New idea Monday, new priority Tuesday. Ideas go to the issues list instead.
- The meeting slips. One missed week becomes three. Treat it like a customer appointment.
- Numbers become a blame game. The scorecard exists to surface problems early, not to punish people. Off-track numbers become issues to solve.
- Too many priorities. If everything’s a priority, nothing finishes.
- Rolling out to everyone at once. The leadership team needs to model it first.
- Vocabulary without behavior. Using the words without the discipline produces a team that talks about the system instead of running it.
Self-implement or get help?
Self-implementing works when the owner can take hard feedback and someone on the team can facilitate firmly. Outside help earns its keep when the owner is part of the problem, the team avoids conflict, or you want a neutral facilitator for the planning sessions. For EOS specifically, that might be a Professional EOS Implementer; for BOSS, it’s what I do.
Where AI fits in the rollout
AI is useful from week one: building the scorecard report automatically, drafting the meeting agenda from the issues list, sending to-do reminders and summarizing the meeting. In my own companies, an AI chief of staff handles most of that preparation so the human time goes to decisions. See AI for KPIs and meetings.
How you’ll know it’s working
By the end of the first year, healthy rollouts usually show the same signs: the weekly meeting hasn’t been skipped, leaders bring issues instead of hiding them, most quarterly priorities get finished, the scorecard is trusted, and the owner’s calendar has more room for vision and relationships. If those signs aren’t there, go back to the ground rules — one of them is almost always being broken.
Next steps
If you haven’t chosen a system yet, read best business operating system. If you’re ready to install one and want help, request a strategy call.
Questions people ask
How long does it take to implement a business operating system?
The basic tools can be running within a quarter. Making them habits across the leadership team usually takes a year, and cascading them through the whole company takes longer.
Should we self-implement or hire help?
Self-implementing works when the owner is disciplined and someone strong can facilitate. Outside help is valuable when the owner is part of the problem, the team avoids conflict, or you want a neutral facilitator for planning sessions.