ANDREA FLORESCUSTRATEGY. SYSTEMS. EXECUTION.
FREE GUIDE + WORKBOOK · THE FRACTIONAL COO PLAYBOOK

Build what a COO would build. Before you hire one.

Most founder-led businesses don't need another strategy. They need the work to move without waiting on you. This playbook walks you through the 16 steps I'd put in place first, and the workbook gets you to decisions, not just notes.

  • Free
  • 32-page fillable PDF
  • Follow-up emails and newsletter are optional
Cover of The Fractional COO Playbook workbook by Andrea Florescu: sixteen steps and a 90-day operating plan
WHY THIS EXISTS

The strategy is usually fine. The work just keeps waiting on you.

Decisions take too long. Priorities change every week. Important work depends on someone's memory. That isn't a strategy problem. It's an operating problem, and it has a structure you can build.

These sixteen steps are that structure, in order: decide what to fix, give each outcome an owner, set a weekly rhythm, turn priorities into commitments, take yourself out of the approval path, and know whether it's working.

THE WORKBOOK · FREE FILLABLE PDF

Make the decisions, not just the notes.

The guide below explains each step. The workbook gives you a worksheet for every one of them, a 90-day roadmap, three templates and a ten-point operating score.

  1. Enter your email. Leave the optional boxes unticked if you only want the workbook.
  2. Confirm your address in the short email that arrives.
  3. The workbook opens right away, and a copy follows by email.

Free. Follow-up emails and the newsletter are optional and unticked by default. Unsubscribe anytime. Working solo? The Solo Business Freedom Test™ is a better fit. See the Privacy Policy.

PART I · STEPS 01–03

Decide what to fix first

Start with the constraint that costs the most and define what better looks like.

Step 1: Find the constraint

Ask what is limiting the business most right now: direction, capacity, execution, people, process or cash flow.

You'll see a little of all six. The first 90 days still go to one, because a fix spread across six problems doesn't move any of them.

Example. Demand is strong, but delivery only works when you and two senior people work evenings. That's a capacity constraint, not a sales one.

Common mistake. Documenting every process first. Start with the constraint that costs the most.

Step 2: Name the outcome

Replace “we need better operations” with a result you can check: what improves, how it's measured, by when, and who owns it.

A vague goal can't be delegated. A measured one can.

Example. Reduce client onboarding from 10 business days to 5 by March 31, owned by the account lead.

Common mistake. Listing activities (meetings, documents, tools) instead of the result they're meant to produce.

Step 3: Choose your stage

Decide which condition your operation is in today: stabilize, build or scale. These describe the business, not a type of engagement.

Each stage needs different work. Stabilizing means fixing what's breaking. Building means systems for the next stage. Scaling means growth with less founder dependence.

Example. Missed commitments and weekly fire drills point to stabilize, even if revenue is growing fast.

Common mistake. Trying to do all three at once. Pick one and expand once the foundation is working.

PART II · STEPS 04–06

Build the operating foundation

Write down who owns what, who decides, and how work moves.

Step 4: Draw the one-page operating picture

Put the business on one page: model and customer, revenue range, services, top three goals, team, biggest constraint, five key metrics, decisions still on your desk, and risks.

Decisions get easier when everyone is looking at the same picture.

Example. A founder who writes “every proposal over $10,000” under decisions still with me has just found her first delegation candidate.

Common mistake. Turning it into a business plan. One page is the point.

Step 5: Give every outcome one owner

For each outcome, name the owner, the contributors, the approver if one is needed, and who only needs to be informed.

When everyone is responsible, work moves until it needs a decision. Then it waits for the one person who always decides.

Example. Client onboarding: owned by the account lead, approved by the operations lead, escalated when capacity runs short.

Common mistake. A responsibility chart nobody uses. Review ownership in the weekly meeting and change it when the business changes.

Step 6: Map one critical workflow

Pick one workflow that touches revenue, customers, cash or risk. Record its trigger, steps, owner, handoffs, standard, failure point and metric.

Most breakdowns happen at handoffs, where work moves from one person to the next and nobody owns the gap.

Example. Invoice to payment: the trigger is job completion, the failure point is invoices waiting on a manager's review.

Common mistake. Writing the ideal version. Map how it runs today, then fix it.

PART III · STEPS 07–08

Set a weekly rhythm

Meetings decide. Dashboards inform.

Step 7: Set the meeting rhythm

Run three meetings: a weekly leadership meeting (45 to 60 minutes), a team check-in (20 to 30 minutes) and a monthly business review (60 to 90 minutes).

Each one has a different job. The weekly meeting decides. The check-in clears blockers. The monthly review looks at money, customers, quality, capacity and risk.

Example. A weekly agenda: metrics, priority progress, issues and decisions, owners and deadlines, next week's focus.

Common mistake. The round-robin status update. Status belongs in the dashboard.

Step 8: Build a small dashboard

Track five to eight numbers. For each, agree on what it means, where it comes from, who owns it, how often it's updated, its target range and what happens when it drifts.

A number with no agreed response is just information.

Example. On-time completion below 90% two weeks running triggers a capacity and scope review.

Common mistake. Measuring everything. Thirty numbers create noise; eight create decisions.

PART IV · STEPS 09–11

Turn priorities into commitments

A quarter's plan only works when it becomes something specific someone will finish this week.

Step 9: Choose quarterly priorities

Limit the quarter to three to five priorities, each with a result, an owner, a measure, a deadline, milestones, risks and a first next action.

More than five priorities means none of them gets protected time.

Example. Weak: “improve marketing.” Strong: 20 qualified opportunities from two repeatable channels by September 30, under $500 each.

Common mistake. Confusing urgency with importance. Protect the priorities with clear escalation rules.

Step 10: Turn them into weekly commitments

Write each commitment in one sentence: by [date], [owner] will complete [deliverable], measured by [evidence].

A quarterly priority is too big to manage directly. A weekly commitment can be checked on Friday.

Example. By Friday, the operations lead will publish the onboarding checklist and test it with two new clients.

Common mistake. “Work on the checklist.” If you can't verify it, it isn't a commitment.

Step 11: Keep one issues and decisions log

Keep every open issue and pending decision in one shared list with impact, owner, due date, status and the decision made.

Important topics stop getting lost between meetings, and the escalation path becomes visible.

Example. Routine issues are solved at the lowest sensible level. Major risk, budget, customer or strategy decisions go to the designated approver or backup.

Common mistake. Decisions living in chat threads and inboxes where nobody can find them next month.

PART V · STEPS 12–13

Take yourself out of the approval path

Turn repeated judgment calls into rules your team can use.

Step 12: Log your decisions for two weeks

For ten working days, write down every decision that needed you. Then sort each into keep, delegate, set a rule, or stop.

Most of what lands on your desk isn't hard. It's just never been decided once, so it gets decided again every time.

Example. Discounts: team members approve up to 10%, a functional leader up to 20%, and anything above goes to a designated approver or their backup.

Common mistake. Delegating the task but keeping the decision. If your team has to ask permission for every decision, you've just given them the work.

If you've taken The Founder Dependency Test™ or the Day 3 Fix Finder, you've already seen this pattern. This is where you act on it.

Step 13: Write decision principles and rules

Write five principles your team can apply without asking, then turn your most repeated decisions into threshold rules.

Principles handle the judgment calls rules can't predict. Rules handle the ones that repeat.

Example. Protect customer trust before short-term revenue. Prefer reversible decisions when information is incomplete. Escalate early when a commitment is at risk.

Common mistake. Principles nobody sees. They only work if they're visible, discussed and applied the same way every time.

PART VI · STEPS 14–16

Know it's working

Measure where you start, watch the early signals, and review every month.

Step 14: Capture a baseline

Before you change anything, record today's numbers: cycle time, rework, missed deadlines, complaints, founder approval hours, collection time, margin and open issues.

Without a baseline, improvement is a matter of opinion.

Example. Founder approval hours: 9 a week today. That number is what you'll check at day 90.

Common mistake. Starting the changes first and trying to remember where you began.

Step 15: Pair results with early signals

Match each lagging result (revenue, profit, retention, complaints) with a leading signal (pipeline, blockers, approval wait time, commitment completion).

Lagging numbers tell you what happened. Leading numbers let you step in sooner.

Example. Retention is the result. Unresolved client issues older than 48 hours is the signal you can act on this week.

Common mistake. Watching only revenue and finding out about problems a quarter late.

Step 16: Run a monthly improvement review

Once a month, ask what improved, what deteriorated, which process caused friction, which decision was delayed, what to stop and what to standardize. Then pick one improvement and one owner.

A long list of fixes becomes its own execution problem.

Example. This month: standardize the onboarding checklist the team tested in Step 10.

Common mistake. Choosing five improvements and finishing none.

Every step has a worksheet waiting in the workbook.

Get the workbook ↑
YOUR FIRST 90 DAYS

A practical 90-day roadmap.

Days 1–30

Diagnose and stabilize

  • Interview the owner and key team members
  • Identify the primary constraint
  • Document the operating picture
  • Confirm the top quarterly priorities
  • Start the weekly leadership meeting
  • Pick five to eight dashboard metrics
  • Create the issues and decisions log
  • Fix one high-impact bottleneck
Days 31–60

Build and delegate

  • Map the most important workflows
  • Clarify ownership and decision rights
  • Define operating standards
  • Delegate recurring owner decisions
  • Launch weekly commitment tracking
  • Test one improved workflow
  • Review early performance data
Days 61–90

Scale and institutionalize

  • Refine the dashboard
  • Standardize what worked
  • Train process owners
  • Review capacity and role design
  • Set next quarter's priorities
  • Measure founder time recovered
  • Document the next improvements
SEVEN MISTAKES

What gets in the way.

  1. Hiring for activity instead of outcomes.Define the business result first.
  2. Adding tools before fixing ownership.Technology is rarely the problem. Clarity is.
  3. Measuring everything.Track the few numbers that change decisions.
  4. Keeping yourself as the default approver.If every decision comes back, nothing was delegated.
  5. Documenting processes nobody follows.Test them with the people who do the work.
  6. Trying to change everything at once.Fix the constraint with the biggest impact first.
  7. Confusing urgency with importance.Protect priorities with clear escalation rules.
WHEN YOU WANT HELP

You've done the thinking. Choose how to run it.

Plenty of businesses run this playbook on their own. If you'd rather not, there are three ways to work together, depending on the problem in front of you.

QUESTIONS

Before you start.

Can I do this without a COO?

Yes. The playbook is written so an owner can run it with their team. Most businesses start with Steps 1 to 4 and a weekly meeting before they consider outside help.

How long does it take?

The first sitting takes 60 to 90 minutes. After that, 30 minutes a week for the meeting, commitments and log, and one monthly review. The roadmap covers the first 90 days.

Where do I start if everything feels urgent?

With Step 1. Name the one constraint that costs the most, then give it one owner and one measurable outcome. Urgency usually drops once that's decided.

What's the difference between this and hiring a fractional COO?

This guide shows how to build the operating system. A fractional COO provides ongoing operating leadership to run it within authority you agree on. Some businesses need that; many don't.