Does the work your team executes support the business you want to own?
Your company can finish its quarterly priorities and hold productive meetings while growth consumes the cash you hoped to distribute. The operating work needs a clear connection to the ownership outcome.
The iBD Ownership OS starts with your goals and develops company strategy and the financial plan with the CEO and functional leaders. Your business operating system carries that agreed work into responsibilities, measures, meetings and follow-through. Results return to ownership review and inform the next decision.
Keep useful practices and repair the missing connection
A business operating system is the repeatable way the company coordinates work. You may use EOS, Scaling Up, another framework or your own established practices. Different approaches have different methods; a name or software subscription does not establish that the company uses them well.
Keep an effective existing system. If it also contains vision, strategy or financial tools, reconcile those records with the same agreed company plan and periods. Maintaining two conflicting growth or spending plans creates work for everyone who must interpret them.
Consider a hypothetical commitment: sales wants to promise Friday installation, operations has capacity on Tuesday, and finance needs to review the payment terms. A reliable practice makes those checks part of the commitment, identifies who may approve an exception and communicates the agreed decision to everyone affected.
Follow responsibility beyond the title
A person needs to know the result they maintain, who depends on it, what information they need and the decisions they may make. “Operations Manager” alone does not explain who approves a delivery-date change.
The CEO integrates the company plan. The CRO develops supported customer and revenue commitments. The COO manages delivery, capacity and margins. The CFO maintains financial information and connects the assumptions to the numbers. Define the departmental work beneath those responsibilities and where an unresolved issue goes.
One person may hold several roles, including you. Participation in an operating meeting follows the responsibility you actually hold. You do not have to leave every management role or hire three executives to complete this milestone.
Connect measures, commitments and review
Use the maintained revenue forecast, financial package, line margins and operating KPIs. State their definitions, periods and limitations. A current operating estimate can be useful without being a closed financial result.
A commitment needs an outcome, responsible person, decision authority, due date and evidence of completion. Keep the action date separate from the date its effect can be evaluated. Use the company’s existing task and meeting records.
Weekly reviews return to earlier commitments, examine meaningful changes, decide within the team’s authority and assign a specific next step where more evidence is needed. Necessary safety, quality, customer and risk controls remain alongside improvement work. Urgent issues use immediate escalation.
A supported decision to continue counts. At the next review, check what happened and whether the explanation still holds. Completing the meeting agenda alone does not show that the response worked.
Use one plan across the full rhythm
| Rhythm | What it connects |
|---|---|
| Annual | Ownership direction and accepted risk → supported revenue, delivery and financial proposals → the adopted company plan and budget. |
| Quarterly | Review results and the constraint → agree the next Game Plan → translate it into feasible departmental commitments. |
| Weekly | Review measures, coordinate work, resolve issues and check earlier actions. |
| Monthly | Bring revenue, finance and operations evidence to the CEO, then review the integrated company position with ownership. |
The four monthly company conversations are CRO with CEO, CFO with CEO, COO with CEO, then owner with CEO. Schedule them around usable reports and the close. The community’s Tuesday sessions support your practice; attending one does not replace your own company’s review.
The iBD annual process begins with ownership direction and first-pass proposals, then develops the detailed budget through Q4 toward December 15 approval. Use your company’s fiscal year and actual calendar explicitly. Keep the approved budget as the comparison and maintain a current forecast when expectations change.
If the supported plan cannot produce your goals, make the trade-off visible. Reinvestment, distributions and new capacity may compete for the same cash. Resolve that choice before asking the team to execute inconsistent assumptions. Keep private ownership information with the appropriate audience; the team needs the resulting company direction and authority.
Start with one real commitment
Choose a current priority or recent customer commitment. Gather the plan, responsibilities, dashboard and review records. Trace it from agreement through the handoffs, decision and later result check.
If several links are weak, repair the one preventing dependable execution first. Unclear authority may need resolution before another meeting helps. Unreliable source data may need repair before the team can trust a new dashboard. Sequence the work around normal delivery and the team’s capacity.
| Tool | When it helps |
|---|---|
| OS Selection Decision Matrix | Compare keeping, repairing or changing the operating approach when that decision is unresolved. |
| OS Implementation Roadmap | Agree responsibilities, review handoffs, practical repairs and who maintains the practice. |
| iBD-OS Integration Worksheet | Follow the company plan through departmental work and return actual results to ownership review. |
The COO Monthly Review preparation supports the operations conversation within that same system. Keep suitable current records instead of duplicating the team’s work in every template.
What completion looks like
The seven capabilities require demonstrated use, including four consecutive actual weekly reviews, one closed monthly review and one completed quarterly planning or review decision. Show the annual-planning connection and next dates; do not invent an annual cycle that has not occurred. A vacation test is not part of this milestone’s approved requirements.
Open the seven completion requirements
1. An agreed operating approach
The team can explain which practices it uses and why.
Sufficient evidence: An agreed approach, current instructions and explanation from the people who use them. Keeping an effective existing system counts.
Ask together: Which operating practices have we agreed to use, and which recent example shows why they fit?
2. Responsibility, authority and handoffs
People know the result they own, their decision limits and where unresolved work goes.
Sufficient evidence: Current role and handoff records, with a real example of accepted responsibility and appropriate escalation. One person may hold multiple roles.
Ask together: Who accepts this handoff, what may they decide, and where does a decision outside that authority go?
3. Maintained information
Revenue, finance and operations use measures with clear definitions, sources and periods.
Sufficient evidence: The actual records and reporting version used in reviews. Explain material limitations. Reuse M14–M17 work and the financial package.
Ask together: Can we reproduce the information used in a review, with its definition, source and reporting period?
4. Connected priorities and commitments
Operating work follows the agreed company plan, with responsibility, completion evidence and review dates.
Sufficient evidence: Trace a current priority into departmental work. Keep necessary customer, quality and risk controls alongside improvement projects.
Ask together: Which company commitment does this work serve, who is responsible, and how will completion be checked?
5. A connected review rhythm
Weekly execution and monthly, quarterly and annual reviews have clear purposes and decision handoffs.
Sufficient evidence: The actual meeting records and next calendar. Show the four monthly company reviews and how ownership direction reaches the team.
Ask together: What decision moves from each review to the next, and where does ownership direction return to execution?
6. Actual use and follow-through
The company uses the practice repeatedly and checks what happened after a decision.
Sufficient evidence: Four consecutive actual weekly reviews, one closed monthly review and a completed quarterly decision. Show a response or supported continuation and a later check.
Ask together: What did we decide with the facts available at the time, and what did the later review show?
7. Continuing maintenance
The authorized team can find and maintain the current practice.
Sufficient evidence: Name the maintainer and backup, confirm appropriate access, and state the next review and triggers for change.
Ask together: Who maintains these records, who is the confirmed backup, and what would prompt an earlier review?
Review the milestone-specific 0–3 score and evidence test
0. Not Started. You have not begun examining or establishing a connected operating practice.
1. Learning. You can explain what the operating system does and how it connects to ownership direction, but the company’s practice is not substantially built.
2. In Progress. Useful responsibilities, measures, meetings or planning practices exist, but one or more required capabilities or actual-use evidence remains incomplete.
3. Installed. All seven capabilities are supported by current company records and demonstrated use, including four consecutive actual weekly reviews, one closed monthly review and one completed quarterly planning or review decision. The team can follow an actual commitment from the agreed company plan through responsibility, review, decision and follow-through, and explain how results inform ownership review.
Verification: Follow a real commitment through the company plan, responsible roles, source measures, operating decision and later result check. Inspect the four weekly reviews, the closed monthly review and the quarterly decision. Show how the annual planning process and next dates connect to this practice. Suitable existing records count when they prove the required capabilities. An annual cycle that has not happened is not invented as evidence.
Use suitable existing work. Record each requirement as complete, incomplete or not reviewed, with its evidence and date. You choose the saved score; keep owner, peer, coach and AI assessments separate. Missing access remains unreviewed rather than automatically zero. Preserve earlier reviews and name the next action, responsible person and review date.
Maintain the connection as the company changes
Keep direction in The Plan, financial evidence in The Numbers, responsibilities and operating instructions in Your Leadership Team, and dated decisions in The Rhythm. Your operational software can remain where the team works, linked from the Playbook.
Name the maintainer and backup and confirm that the authorized people can use the current records. Revisit affected work after a material role change, unreliable data, failed handoffs or a changed operating model. A missed target may coexist with an installed practice that notices it, responds and checks the result.
Module 7: Leadership Team develops the functions, staffing and people responsible for this work. You can use that guidance while building the operating practice. Completing Module 6 does not automatically complete leadership or your later operator transition.
Explore how planning becomes execution
- 481. The Private Equity Operating System, with Nick Bradley: connect governance, leadership and operating reviews; choose the practices that fit your business.
- 436. Integrating Strategy, Execution, and Financial Clarity, with Shannon Susko: examine the work between longer ambitions and quarterly commitments.
- Business Operating System: revisit how the company practice connects to ownership direction.
Choose your next step
Review the wider system. The Ownership Assessment helps you consider this work beside your ownership goals and the other milestones. Choose a useful priority from the evidence you have.
Connect the work with support. The 90-Day Boardroom Blueprint brings ownership direction, the financial foundation and decisions into a first usable Playbook. You can explore that support directly; the Assessment is not a purchase prerequisite.
← M17: Operational KPIs · Module 6 · Module 7: Leadership Team →