Category: Blog

Your blog category

  • The Single Source of Truth Problem: Why COOs Have It Worst

    The Single Source of Truth Problem: Why COOs Have It Worst

    Every organisation has multiple systems, multiple data sets, multiple versions of the same number depending on who you ask and when.

    COOs have it worse than almost anyone else in the leadership team, because they sit at the intersection of the most systems: project management, finance, HR, capacity planning, strategic planning. Each function has its own data, its own tools, its own definitions. When the COO tries to synthesise across them, the inconsistencies are as numerous as the data points.

    Why Single Sources of Truth Are So Hard

    The technical problem is real but solvable — data integration is well-understood, even if it’s expensive. The harder problem is definitional. What do we mean by “project cost”? Does it include people time? Contractor fees? Infrastructure? The answer varies by function and by question.

    “What’s the capacity of the engineering team?” means something different to the project manager (how many dev-days are available?), the finance team (what’s the fully-loaded cost rate?), and the COO (can we take on this new initiative or not?).

    Until the definitions are agreed, no single source of truth can satisfy everyone — because the truth looks different depending on what question you’re asking.

    The Practical Approach

    The pragmatic answer is not one system to rule them all. It’s a clear hierarchy of systems, with agreed definitions for each context.

    For operations decisions, the project management and capacity system is authoritative. For financial decisions, the finance system is authoritative. For people decisions, the HR system is authoritative. The COO’s role is to synthesise across these authoritative sources, not to find one system that replaces them all.

    What the COO does need is a dashboard layer that aggregates the key signals from each system — not replacing the underlying systems, but surfacing the operational intelligence that sits across them.

  • Workforce Planning in a Volatile Market: A COO’s Survival Guide

    Workforce Planning in a Volatile Market: A COO’s Survival Guide

    A global pandemic, a hiring market that flipped from talent shortage to mass layoffs in eighteen months, remote work adoption that redrew the boundaries of where talent lives — the rules that worked in 2019 were inadequate by 2021, and different again by 2023.

    Workforce planning in a volatile market requires a different approach from workforce planning in a stable one.

    Plan for Ranges, Not Points

    In a stable market, headcount planning produces a specific number: “We will hire 24 people in FY26.” In a volatile market, this precision is false. Build ranges instead: “We will hire between 16 and 28 people in FY26, depending on which of our three scenarios materialises.”

    Ranges look imprecise, but they’re more honest — and they create explicit trigger conditions that tell you where in the range you’ll land.

    Diversify Your Workforce Flexibility

    Traditional workforces are mostly permanent, full-time employees. This maximises cultural coherence and skill depth but minimises flexibility. When volumes change, the only lever is layoffs — which are expensive, slow, and damaging to culture.

    COOs in volatile markets increasingly build blended workforces: a permanent core supplemented by contractors, consultants, and freelancers who can be scaled up or down faster than permanent headcount. The right mix depends on the nature of the work — some functions require permanent staff, others can be effectively delivered by contractors.

    Make Attrition a Planning Input

    Most headcount plans model net hiring. They should also model attrition — because attrition is a form of workforce flexibility, and its rate and pattern matter. High attrition in critical skill areas is a crisis. Moderate attrition in a period of strategic pivoting can be an opportunity — a natural way to reshape the team without painful decisions.

    Model attrition explicitly: what is your expected attrition rate by team and role type? What does that mean for net headcount and capability at year-end? Use this to inform hiring targets that account for replacement, not just growth.

    Build the Organisational Muscle

    Volatile markets reward organisations that can reconfigure themselves quickly. That means leadership that can make headcount decisions fast, HR processes that can move from approval to offer in days rather than weeks, and a culture comfortable with change.

    Building that muscle is itself a workforce planning exercise — investing in the processes, tools, and leadership development that make the organisation adaptable, not just for the next volatility event, but as an enduring capability.

  • The Hidden Cost of Delayed Hiring Decisions

    The Hidden Cost of Delayed Hiring Decisions

    The hidden cost — the cost of not hiring, or hiring late — is less visible but often larger. It doesn’t show up as a line item on the P&L. It shows up as missed revenue, delayed projects, burned-out teams, and strategic opportunities that passed because the organisation didn’t have the capacity to pursue them.

    Opportunity Cost Is Real Cost

    When a product team is under-resourced for two quarters, the features that weren’t built represent real revenue — from customers who would have bought them, from the competitive advantage that would have been captured. This opportunity cost is diffuse and invisible, which is why it’s chronically underweighted in hiring decisions.

    The discipline of making opportunity cost explicit is hard but important. “If we don’t hire this engineer, Project X will slip by one quarter. Project X is expected to generate $Y in new revenue. Therefore, the cost of not hiring is approximately $Y minus the hire’s salary and overhead.” That’s not a perfect calculation, but it reframes the decision correctly.

    The Team Cost

    Beyond revenue impact, delayed hiring has a team cost. When teams are chronically under-resourced, they absorb the overload — and eventually they stop absorbing it. Senior people leave. Quality drops. The culture shifts from proactive to reactive. These costs are real, and they compound over time in ways that are very hard to reverse.

    A $100K engineer who prevents $300K in attrition costs (replacement of two senior people, recruiting fees, productivity loss during ramp-up) has generated a 3x return before writing a single line of code.

    The Decision Asymmetry Problem

    Hiring decisions are evaluated asymmetrically. The cost of a bad hire is visible and attributed. The cost of a late hire is invisible and diffuse. This asymmetry makes most organisations structurally too slow to hire — they’re optimising for the visible risk, not the total risk.

    COOs who understand this asymmetry can reframe the conversation: “What is the cost of waiting three more months to decide?” Putting a number on the cost of delay makes the decision symmetric — you’re choosing between two risks, not between risk and safety.

  • How to Use Scenario Planning to Make Hiring Decisions Faster

    How to Use Scenario Planning to Make Hiring Decisions Faster

    Once you hire someone, you’re committed to at least several months of salary, and letting someone go is costly in both financial and human terms. So leaders are cautious — they want certainty before committing to headcount.

    Scenario planning doesn’t give you certainty. But it gives you the next best thing: pre-made decisions for multiple possible futures, so when conditions become clear you can move fast.

    The Hiring Decision Problem

    The classic hiring dilemma looks like this: “We think we’ll need three more engineers in Q3, but we’re not sure how Q2 revenue will land. If Q2 hits target, we definitely hire. If it misses, maybe we wait. So let’s wait and see.”

    By the time Q2 results are known, you’re in Q3. The hiring process takes 3–4 months. The engineers won’t be productive until Q4 at the earliest. You’ve lost the entire year.

    The scenario planning solution is to make the decision conditional in advance. “If Q2 revenue is >$X, we begin hiring immediately. If it’s between $Y and $X, we hire for two of the three roles. If it’s below $Y, we hold.”

    Now the decision is made. What’s left is monitoring the trigger, not agonising over the framework.

    Building a Hiring Decision Tree

    For each scenario, define:

    • Trigger: What signal tells you you’re in this scenario? (Revenue milestone, funding close, win rate threshold)
    • Hiring response: Which roles, how many, in what sequence
    • Timeline: When does hiring begin, what’s the target start date
    • Budget impact: What does this headcount cost, and where does it come from

    This decision tree should be built during the annual or quarterly planning process — not when the signal arrives.

    Moving From Decision to Action Quickly

    When the trigger fires, the decision is already made. The operational task is to execute it quickly — job descriptions are drafted, interview panels are identified, recruiting partners are briefed. Everything that can be done in advance should be.

    The goal is to compress the lag between “we know we need to hire” and “the person is in the role” from six months to three.

  • What Happens When You Plan for Only One Future

    What Happens When You Plan for Only One Future

    The default planning mode is a single best-estimate forecast: here is what we expect revenue to be, here is the headcount we’ll hire, here is the roadmap we’ll deliver. One plan, one future, all energy focused on executing against it.

    The problem is that the future rarely looks like the plan.

    The Illusion of Precision

    Single-point forecasts create an illusion of precision. A budget that says “we will spend $4.2M in H1” sounds precise. It implies a level of confidence in the underlying assumptions — revenue trajectory, hiring timeline, project scope — that almost never exists in practice.

    This illusion is dangerous because it discourages adaptive planning. If the plan is specific, deviating from it feels like failure. So organisations stick to the plan past the point where the plan is clearly wrong — because changing the plan requires admitting the original was flawed.

    The Cost of Single-Scenario Betting

    The cost of planning for only one future shows up differently depending on which direction reality diverges. If things go better than expected, the organisation is slow to accelerate — there’s no pre-built plan for upside. If things go worse, there’s no pre-built response — leadership has to improvise under pressure, in a compressed timeframe, with deteriorating options.

    Both are expensive. The upside miss is often invisible — you never know how much faster you could have grown. The downside scramble is painful and visible — decisions made under pressure that a little prior thinking could have made better.

    Building Adaptive Capacity

    The alternative to single-scenario betting is not analysis paralysis. You don’t need to model every possible future. You need to model the futures that matter — the ones where you’d respond differently.

    Start by identifying the two or three most uncertain variables in your operating environment. For each pair of extremes, ask: would we do anything differently? If the answer is yes, you need a scenario for it. If no, you don’t.

    Most businesses need three to four scenarios, not fifty. The value is not in the modelling — it’s in having made the decisions in advance.

  • Scenario Planning 101: A COO’s Framework for Uncertain Times

    Scenario Planning 101: A COO’s Framework for Uncertain Times

    It’s the practice of developing multiple explicit alternative futures and preparing the organisation to navigate each of them, rather than betting everything on a single forecast.

    In a predictable environment, scenario planning is useful. In an uncertain one — economic volatility, rapid market change, geopolitical disruption — it’s essential.

    What Scenario Planning Is Not

    Scenario planning is not the same as forecasting. A forecast is your best estimate of what will happen. A scenario is a coherent narrative about a possible future, not necessarily the most likely one.

    Scenario planning is also not the same as contingency planning. Contingency plans are reactive — “if X happens, we’ll do Y.” Scenario planning is proactive — “we’ve thought through what world X looks like, and we’ve made decisions in advance that make us resilient to it.”

    The Four-Scenario Framework

    A practical COO-level scenario framework covers four quadrants of the two variables that matter most for your business. For a growth-stage SaaS company, these might be: market demand (high/low) and access to capital (ample/constrained).

    This generates four scenarios:

    • High demand + ample capital: Aggressive growth mode — full hiring plan, accelerated investment
    • High demand + constrained capital: Prioritise ruthlessly — hire only critical roles, maximise revenue capture
    • Low demand + ample capital: Product investment — use capital advantage to build while demand is soft
    • Low demand + constrained capital: Survival mode — protect core, extend runway, minimum hiring

    Each scenario should have pre-agreed responses across headcount, budget, and strategic priority. The goal is to make the decisions in advance, not under pressure.

    The Planning Process

    Step 1: Identify your two key uncertainties — the variables with the highest impact and the highest uncertainty for your business.

    Step 2: Build four scenarios from the extremes of those two variables.

    Step 3: For each scenario, define what the company would do differently across three dimensions: headcount, budget, and strategic priorities.

    Step 4: Identify leading indicators — early signals that would tell you which scenario is developing.

    Step 5: Agree decision triggers — at what point would you move from one scenario response to another?

    The Update Cadence

    Review scenarios quarterly. The scenarios themselves don’t need to change frequently — what changes is your assessment of which scenario is most likely to develop, and whether the early indicators are pointing in one direction.

  • How to Build a Headcount Plan Your CEO and CFO Will Both Trust

    How to Build a Headcount Plan Your CEO and CFO Will Both Trust

    The COO needs a headcount plan that’s grounded in what the business actually needs to deliver its commitments. The CFO needs a headcount plan that’s tied to revenue assumptions and financial constraints. The CEO needs a headcount plan that reflects the company’s strategic priorities and growth ambitions.

    These three perspectives are often in tension — which is exactly why most headcount plans satisfy none of them.

    Start With Demand, Not Org Charts

    The most common mistake in headcount planning is starting with the org chart — who do we have, what roles are open, what does the next tier of management look like? That’s supply-side thinking.

    Start with demand: what work needs to be done to deliver the company’s strategy, and what skills and capacity does that work require? The gap between required capacity and current capacity defines the hiring need.

    Connect Headcount to Deliverables

    Every headcount request should be tied to specific deliverables: what will this person enable the company to do that it cannot do now? Generic headcount requests (“we need another engineer”) don’t get funded. Specific ones (“we need a senior backend engineer to deliver the enterprise API by Q3, which unlocks the $2M sales pipeline”) do.

    The COO’s job is to ensure that every headcount request in the plan is connected to a specific deliverable and a specific strategic priority.

    Model the Timing

    Headcount has a long lead time. A senior engineering hire takes 3–4 months from approval to start date. Add ramp-up time — another 1–3 months before the person is fully productive — and a decision made in January might not generate capacity until Q3 or Q4.

    Build this lag into the plan. Show not just when hires are planned, but when they’ll be productive — and how that productivity curve affects project delivery timelines.

    Build in Scenarios

    The CFO will want to know: what if revenue underperforms? What if we raise a round sooner than expected? Build two to three headcount scenarios tied to financial outcomes. Scenario A (base case): full headcount plan. Scenario B (conservative): 70% of headcount plan, priority roles only. Scenario C (accelerated): expanded headcount plan, funded by upside.

    Having the scenarios pre-built means leadership can make fast decisions when conditions change, without having to go through a full replanning cycle.

    Present It as an Investment, Not a Cost

    The framing of headcount as “cost” is both accurate and limiting. The CEO and CFO also respond to “investment” framing when it’s connected to returns: “This hire cohort will cost $X and will enable us to deliver $Y in new revenue / $Z in efficiency savings / the A strategic initiative.”

    The COO’s skill is connecting the people investment to the business outcome — making the headcount plan a strategy document, not just a staffing document.

  • 5 Budget Reporting Mistakes COOs Make (And How to Fix Them)

    5 Budget Reporting Mistakes COOs Make (And How to Fix Them)

    Budget reporting is one of those functions that everyone does but few do well. Here are the five most common mistakes COOs make in budget reporting — and the fixes.

    1. Reporting Actuals Without a Forecast

    Reporting “we’ve spent $X against a budget of $Y” is retrospective and therefore actionable only if you’re already over budget. The more useful number is the forecast — what you expect to spend by year end. Always pair actuals with a forecast.

    Fix: Add a “forecast to completion” column to every budget report. This is the number that drives decisions.

    2. Too Much Detail at the Leadership Level

    Leadership-level budget reports that contain every line item produce the same outcome as no report at all: nobody reads them carefully enough to act. Leaders need the exception view — what’s off track and by how much — not the full ledger.

    Fix: Lead with the exceptions. Show the four or five biggest variances from plan, with brief explanations and recommended actions. Detailed breakdowns go in an appendix.

    3. Lagging Data

    Budget reports that are 30 days behind are management history, not management tools. By the time a March overspend appears in a report reviewed in May, the decisions that caused it were made in February.

    Fix: Move to real-time or near-real-time budget dashboards for operational use. Reserve monthly reports for governance and compliance purposes.

    4. Not Connecting Spend to Outcomes

    “We spent $500K on the platform migration” means nothing without the context of what was delivered. Budget reports that track spend without connecting to deliverables and outcomes treat money as the end rather than the means.

    Fix: For every major project or initiative in the budget report, include a one-line delivery status alongside the financial status.

    5. Treating All Variances Equally

    A 5% overspend on a critical strategic programme and a 5% overspend on office supplies are not the same problem. Budget reports that surface all variances with equal urgency cause decision fatigue — leaders either chase every variance or ignore them all.

    Fix: Flag variances by materiality and strategic importance. A threshold-based alert system (e.g., flag variances over 10% on strategic projects, over 20% on operational costs) focuses attention appropriately.

  • Budget vs Actuals: A Framework for Mid-Year Financial Reviews

    Budget vs Actuals: A Framework for Mid-Year Financial Reviews

    They’re the moment when you have enough actual data to know whether the original plan was realistic — and enough time remaining in the year to do something about it if it wasn’t.

    Here is a framework for running a mid-year review that produces real decisions, not just updated spreadsheets.

    Before the Review: Prepare the Data

    Gather three sets of numbers for each project and cost category:

    1. Original budget: What was approved at the start of the year?
    2. Actuals to date: What has actually been spent through the mid-year point?
    3. Full-year forecast: Based on actual run rate and known future commitments, what do you expect to spend by year end?

    The comparison between original budget and full-year forecast is the key number. Variance between actuals and budget at mid-year is expected — projects run at different rates. Variance between forecast and budget at year-end is what tells you whether you need to act.

    The Four Quadrants

    Categorise every project into one of four quadrants:

    • On track: Forecast within 10% of budget, delivery on plan
    • Over budget but on scope: Forecast exceeds budget, but scope is justified — requires either reallocation or budget amendment
    • Under budget: Forecast below budget — may indicate slow delivery, scope reduction, or delayed hiring
    • Off track: Forecast over budget AND delivery behind plan — highest priority for intervention

    The Conversation for Each Quadrant

    Each quadrant requires a different conversation. Over budget but on scope needs a funding decision. Under budget needs a delivery accountability conversation. Off track needs an intervention plan with a named owner and a clear decision point.

    The mistake most organisations make is treating all variances as the same — requiring justification for every variance, regardless of whether it signals a real problem. The four-quadrant framework lets you focus intervention energy where it matters.

    Reallocating Budget at Mid-Year

    Mid-year reviews often surface opportunities for reallocation — underspend in one area that can fund a priority in another. Treat mid-year reallocation as a strategic decision, not just a financial one. Before moving budget, ask: why is there underspend? Is it because the work isn’t happening, or because it’s being done more efficiently? The answer matters.

  • People Costs Are 70% of Your Budget. Are You Managing Them Right?

    People Costs Are 70% of Your Budget. Are You Managing Them Right?

    It is, by a wide margin, the largest cost category. And yet in most organisations, people costs are managed at the departmental level in HR systems and payroll, completely disconnected from the project budgets and capacity plans where they actually matter.

    This disconnect has real consequences.

    The Attribution Problem

    When a software engineer spends 60% of their time on one project and 40% on another, which project pays their salary? In most companies, the answer is: neither. The salary goes to “Engineering.” Both projects show no people cost in their budget. Both projects appear dramatically under-budget. And no one has a real view of what projects actually cost.

    This isn’t just a reporting problem — it’s a decision-making problem. Without visibility into people cost attribution, you cannot:

    • Compare the cost efficiency of different projects
    • Make informed build-vs-buy decisions
    • Understand the true ROI of initiatives
    • Set realistic project budgets that include the team’s time

    The Tracking Gap

    The reason people costs aren’t tracked at the project level is usually that it’s hard. Actual salary data is sensitive. Allocation percentages change frequently. Calculating “the cost of an engineer’s time allocated to Project X this quarter” requires integrating capacity data, HR data, and project data — three systems that rarely talk to each other.

    The pragmatic fix is to use a blended rate approach: establish a cost rate per role (e.g., “senior engineer = $X/day fully loaded”) and allocate to projects based on capacity allocation percentages. It’s not precise to the dollar, but it’s directionally accurate — which is what you need for operations decisions.

    What You Unlock With People Cost Visibility

    When people costs are attributed to projects, a set of powerful analyses become possible:

    • True project cost: What did that feature actually cost us to build?
    • Cost per team: What does it cost to run the platform team for a quarter?
    • Scenario cost modelling: If we hire two senior engineers next quarter, how does that change the project’s financial profile?
    • Make vs buy: Is it cheaper to build this in-house or contract it out?

    None of these questions can be answered well without people cost attribution. With it, you have the foundation for genuinely data-driven resource and budget decisions.