← BackSee all toolsThe Install CrunchMy own account · counts rounded, names removed
Leadership story · STAR

The Install Crunch

A leadership story: thirty installs due, investors who could not see the money and one limit I said out loud.

I tell this story in interviews. Counts are rounded and anonymised.

The story

A leadership moment, told as a short case.

This is a story I tell in interviews. Figures are as I recall and report them, rounded.

Situation

Two crises at once

More than thirty installs were due on a fixed date. At the same time, investors could not see where the money was going, because the finance data lived in loose spreadsheets. I was the only person who could lead both.

Task

Deliver, and make the money visible

Hit the install dates and build a clear picture of cash, without letting either one starve the other.

Action

Name the limit, then add capacity

I said out loud that I could not do both at once. Within two weeks I brought in a data and automation engineer and an operations manager I had worked with before. I set objectives, key results and KPIs for each, and moved the finance data into one connected database.

Result

25 of the 30+ on time

The other five slipped for reasons on the customer side, including a site that had not been built. Investors got a clear view of cash.

The result

What came of it.

30+Installs due
25On time
5Slipped: customer side
<2Weeks to add two specialists
On time
Customer-side delay

The curveball

What if I could not hire?

Interviewers often change the constraint. Pick one to see how I would rank the work.

The constraint

Add capacity first, then split the work so each person owns one set of objectives.

  1. Hire two specialists Under two weeks. One for data and automation, one to run the customer and partner relationship.
  2. Make cash visible Move the finance data into one connected database and hand it to the new analyst.
  3. Run installs on objectives Each install lane gets objectives, key results, KPIs and dates.
  4. Ship the easy wins Pre-configured plug-in units before any full install.
  5. Reset the late dates Only the ones that depend on the customer.

What I took from it

Four lessons.

  1. Say the limit. “I can solve both, but not at the same time” is the most useful sentence in a crunch.
  2. Add capacity, not hours. Two people on two objective sets beat one person on twelve.
  3. Gate on readiness. Five misses came from sites that were not ready. A readiness check before a date is promised is the fix.
  4. Cash first. If you cannot see the money, you cannot run the rest.

More in Briefing, Teaching & Leadership

See all tools