Leading in Tech, week 5 case

Case: the pipeline nobody will fund

A failing CI and deploy pipeline costs the team more per quarter than fixing it would. The roadmap has said "next quarter" twice.

Her manager agrees privately and will not fight publicly. A skip-level with the head of engineering is in two weeks.

You will now hear the full case, one page, 5 minutes. Listen for what has already been tried.

Leading in Tech, week 5 case

Case: the laws in tension

  • Buy-In: the proposal was heard twice; the person was never bought
  • Timing: last month's outage is still in recent memory, and memory fades
  • Priorities: three-day releases are quietly eating the roadmap that outranks them

Three laws, and they do not point to the same move.

Leading in Tech, week 5 case

One pitch, both tracks

Whether you lead a team of reports or lead technical direction without reports, you have watched a correct proposal die.

The IC's dead pipeline proposal and the EM's dead headcount ask die the same death: idea heard, person not accepted.

And timing is half of every pitch.

Leading in Tech, week 5 case

Activity: prepare your camp

Assigned camps, 10 minutes. One camp argues: bring it to the skip-level now, while the outage is fresh. The other argues: spend a quarter turning pain into money and pre-wiring the leads, then walk in with allies.

Build your opening and your best evidence from the case text.

Challenge: what is the other camp's strongest attack on you?