Technical Program Management · Case Study · 04 / 06

LabOps
Intelligence

An interactive planning tool for an engineering organisation that is growing faster than its lab space. It connects hiring growth to lab capacity, then to the build projects, budgets, risks and approvals needed to close the gap.

24-Month Forecast Capacity Planning Scenario Planning Risk Triage Governance Synthetic Data
The Problem

Growth Outruns
Lab Space.

Engineering organisations hire faster than they can build lab space. The warning signs sit in different places: headcount plans in HR, seat and bench counts in facilities, build projects in a project tracker, budgets in finance, and risks and approvals in someone's inbox.

So the shortfall shows up late, when engineers are already waiting for benches. At that point the only fixes are expensive ones. The problem isn't missing data. Nobody connects it early enough to act.

Design Goal

Not a prettier spreadsheet. A repeatable way of deciding that links demand signals to projects, budget, approvals and leadership decisions, so a planning number turns into an action with an owner and a date.

Who It's For

  • Program / portfolio manager: runs the recurring review and needs to see which labs, projects and risks need attention this week.
  • Engineering leadership: needs a short list of decisions (speed up, re-order, fund, escalate), not a 40-row status report.
  • Facilities, finance and safety owners: each owns part of the critical path and needs to see how their item affects lab capacity.
How It Works

Forecast → Capacity
→ Decisions.

StepWhat the model does
1 · Forecast demandStarts from current headcount per team, annual growth, seats per engineer, specialised bench needs and a planning buffer. Projects monthly seat demand 24 months out.
2 · Model real capacityDiscounts nominal capacity for downtime, and counts new capacity only from the month its build project is due to finish. Seats and benches are tracked separately.
3 · Drive decisionsLinks each shortfall to the projects that would close it, then to their budget, risks, approvals and dependencies. Red items go to executive triage with an owner.

What You Can Do in the Demo

  • Scenario planning: move the annual growth and planning-buffer sliders, and demand, lab usage and the recommended capacity action all recalculate.
  • Executive dashboard: a 24-month demand vs capacity chart, plus how full each of the 8 lab zones will be at month 12.
  • Portfolio view: 12 concurrent projects (capacity, safety, IT, utilities) with priority, progress, target date and budget, filtered into Executive Triage, Weekly Watch or Standard Cadence.
  • Risk and approval triage: risks scored by likelihood × impact with an owner, and approvals flagged when they are close to blocking a schedule.
PM Thinking

The Decisions
That Mattered.

Capacity only counts when it's real

A common planning mistake is counting a lab expansion as capacity the day it's approved. Here, new capacity only counts from the month its project is due to finish. So if that project slips, the chart shows the shortfall right away. That ties the project schedule directly to capacity risk.

Tiers of management attention

Not every project deserves leadership time. Projects sit in three review tiers (Executive Triage, Weekly Watch, Standard Cadence), so the recurring review spends its time on the few items that can actually change the outcome.

The Recurring Review, in Four Questions

Which labs are close to their buffer or already short? Which milestones or dependencies threaten capacity delivery? Which investments need funding or escalated approval? Who owns each mitigation, and by what date?

Synthetic data on purpose

Every lab, budget, schedule and risk is synthetic. That keeps the model reproducible and shareable while keeping the shape of a real engineering portfolio.

← Home · All Work · LabOps Intelligence