Your First 90 Days as a Tech Scale-Up COO: What to Prioritize

Start With the Mandate, Not the Org Chart

As a new COO at a tech scale-up, you may inherit everything that does not fit neatly elsewhere: hiring friction, missed commitments, customer escalations, and a founder who is still approving too much. Your first priority is not to take ownership of all of it. It is to establish where your leadership will make the biggest difference.

Use the first 30 days to understand and align, days 31–60 to test focused improvements, and days 61–90 to make effective practices repeatable. Treat that sequence as a guide, not a reason to postpone urgent action.

Days 1–10: Agree on What You Are There to Change

COO roles vary significantly. One company needs a commercial operator; another needs someone to connect product delivery, finance, and people operations. An undefined mandate can turn you into the company’s default problem-solver without giving you the authority to solve underlying issues.

Create a one-page working agreement with the CEO covering:

• Business priorities: Which two or three outcomes matter most this quarter?
• Scope: Which functions and cross-functional processes do you own?
• Decision rights: What can you decide, what requires consultation, and what stays with the CEO or board?
• Success measures: What observable changes would make the first 90 days valuable?
• Working relationship: How will you handle disagreements and prevent conflicting instructions?

Ask directly: “What do you want to stop doing because I am here?” Then communicate the agreed boundaries to the leadership team. Private alignment will not help if everyone else still routes decisions to the founder.

Days 1–30: Diagnose How the Business Actually Operates

Listen broadly, but make the listening structured. Meet functional leaders, frontline employees, and selected customers alongside the relevant account owners. Ask where commitments break down, which decisions stall, and what work repeatedly needs rescuing.

Trace a few real workflows from beginning to end: a sale through onboarding, a customer issue through resolution, and a product commitment through release. Look for unclear handoffs, conflicting incentives, capacity constraints, and decisions without owners.

Review the information behind leadership discussions. Depending on the business model, this may include cash runway, forecast reliability, retention, implementation time, service reliability, and hiring commitments. Check definitions and data quality before treating dashboards as facts.

By day 30, produce a short diagnosis:

1. The company’s most important near-term outcomes.
2. The two or three constraints putting those outcomes at risk.
3. The evidence supporting your assessment and what remains uncertain.
4. The issues you recommend leaving alone for now.

If you uncover an urgent cash, security, legal, or customer-continuity risk, involve the responsible experts immediately rather than waiting for the diagnosis phase to end.

Days 31–60: Choose Fewer Improvements and Assign Real Ownership

Avoid launching a company-wide transformation to demonstrate momentum. Prioritize work by business impact, urgency, dependencies, and the team’s capacity to absorb change.

Choose one or two improvements that address a meaningful constraint. For example, if signed customers wait too long to launch, improving the sales-to-implementation handoff may matter more than replacing the project-management tool.

For each improvement, define:

• One accountable owner.
• A baseline and a measurable outcome.
• The decisions that owner can make independently.
• Dependencies and explicit trade-offs.
• A review date and conditions for changing course.

Pilot the change with a bounded team or workflow where practical. Get input from the people doing the work before standardizing it. Your role is to make ownership effective, not to become the permanent escalation point for every detail.

Days 61–90: Build a Rhythm That Supports Decisions

Keep the operating rhythm lightweight. Improve existing meetings before adding new ones.

A weekly execution review should focus on exceptions: what is off track, why it matters, who owns the response, and which decision is needed. Routine updates can usually happen asynchronously. Keep a small set of shared measures with clear definitions and named owners.

Maintain a separate CEO–COO conversation for sensitive trade-offs, role boundaries, and emerging risks. Do not let that relationship become a shadow management system that bypasses functional leaders.

At day 90, review outcomes rather than activity. What improved? What remains blocked? Which responsibilities genuinely moved away from the founder? Agree on the next quarter’s priorities, including what you will stop doing.

Make Sustainable Leadership Part of the Plan

The strongest early contribution is not proving that you can carry more pressure than everyone else. It is helping the company make clearer decisions and deliver commitments without relying on constant intervention.

For structured reflection and practical planning, explore Jessica Hill Holm’s workbook library. If you want personal support with your mandate, CEO partnership, or leadership priorities, consider a coaching call with Jessica.