A fractional COO engagement starts before the COO''s first day. The companies that get the most from their fractional COO are the ones that arrive with a written operational problem statement, clear success criteria, and stakeholder alignment on what "better execution" looks like. This checklist lives on the company side: the setup work needed before the engagement begins so the COO''s time is spent on execution rather than organizational politics. Key pre-engagement work includes defining the one or two operational metrics that matter most, identifying the structural bottlenecks that have resisted resolution, getting leadership alignment on what the COO owns and what they do not own, and establishing the reporting structure before the first meeting. Additional pre-engagement work: prepare a written brief on the company — what it does, its current stage, the strategic priorities for the next 12 months, and the specific operational problems that prompted the engagement. Without this brief, the first meeting becomes a fact-gathering session instead of a strategy alignment meeting. The question to answer before the COO''s first day: what does success look like at 90 days? If you cannot answer this specifically, the engagement will not be structured correctly from the start. Write it down. Circulate it to stakeholders for alignment. Then give it to the COO on day one as the starting point for their engagement. Operational baseline to establish before the first meeting: current team structure and headcount, the three biggest execution bottlenecks, how information flows between teams (Slack, email, Asana, or chaos), and what the existing OKR or goal-setting frameworks are. The COO''s job is to make the machine work — you cannot fix what you have not diagnosed.
A fractional COO engagement starts before the COO's first day. The companies that get the most from their fractional COO are the ones that arrive with a written operational problem statement, clear success criteria, and stakeholder alignment on what "better execution" looks like. This checklist lives on the company's side: the setup work needed before the engagement begins so the COO's time is spent on execution rather than organizational politics. Key pre-engagement work includes defining the one or two operational metrics that matter most, identifying the structural bottlenecks that have resisted resolution, getting leadership alignment on what the COO owns and what they do not, and establishing the reporting structure before the first meeting.
Systems & Access
- Project management tool access (Asana, Linear, Notion, Jira)
- HR and people ops system access (Rippling, Lattice, Workday)
- Financial reporting access (for operational budget tracking)
- Customer support platform access (Zendesk, Intercom)
- Vendor and contract management repository
30-Day Priorities
- Map all cross-functional workflows and identify bottlenecks
- Review org structure and reporting lines
- Interview each department head (30–45 min each)
- Identify top 3 operational fires vs. systemic issues
- Assess current OKR or goal-setting process
60-Day Milestones
- Deliver operational improvement roadmap
- Implement or improve weekly leadership cadence
- Standardize cross-team communication and escalation paths
- Build operational dashboard (headcount, velocity, utilization)
- Identify automation opportunities for manual processes
90-Day Deliverables
- Documented operational playbooks for top 5 recurring processes
- Hiring plan aligned with growth model
- Vendor rationalization recommendations
- Board-ready operational metrics report
- 90-day review and engagement renewal decision
Enter your email and we'll send you a formatted copy right now.