Skip to main content

Manager capstone

A written go/no-go you can show another lead: roster, three owned risks, a named cut, the sentence for the VP. You write it alone.

  1. Read the scenario — Thursday freeze, two people out.
  2. Copy the go/no-go headings and fill every one.
  3. Score yourself against the rubric.

Done when the call is in the first five lines and the plan matches the roster — not a fantasy five-person week. Green CI alone is not a pass.

Scenario

Scenario — Thursday freeze, two people out

You lead a QA team of five on a B2B product (billing + admin + a new “usage export” the sales VP wants in this train).

This week

PersonMonTueWedThu freeze 4pmFri release window
You (lead)InInInEvidence ownerGo/no-go
PriyaInInInInIn
SamSickSick???
RileyPTOPTOPTOBackBack
JordanIn — week 3 of a PIPInInInIn

Jordan's PIP bar: checkout exploratory notes must name a risk and a cut, two releases in a row. Last release they did not.

On-call: Priya was up 1–3am Tuesday for a payments page.

Immovable

  • Contract renewal demo Friday 11am. Enterprise tenant uses SSO + billing.
  • Sales wants usage export in this train. Engineering says it is “probably fine.” No one has a written test plan. Export can dump customer emails if a flag is wrong.
  • CI flake rate on the admin suite is ~25%. Checkout API tests are stable.

You have already ranked eight tickets (same muscle as the eight-bugs lab). You cannot also staff a full settings-UI pass and a new export suite with this roster.

Write the call.

Go / no-go (fill this in)

Go / no-go — (your name, date)

Copy this file. Fill every heading. Keep it to one page if you can.

The call (first five lines)

Go / no-go / go-with-conditions:

The sentence I will say in the room:

Roster (not headcount)

PersonThis weekRole on this train

Who is burned / out / on a PIP, and what that does to the plan:

What we covered

What we are explicitly not testing

  • Cut:
  • Why that is acceptable for this train:

Three risks

RiskOwnerIf it bites

The VP sentence

They want all eight fires, including usage export, with this roster.

What I say:

Artifacts I used

  • Quality-review deck outline
  • Week grid (coverage lesson)
  • Other:

Rubric

Rubric

A pass is specific and short.

MustPassFail
Call in the first five linesGo, no-go, or go-with-conditions, namedStatus novel, “we feel good”
RosterNamed humans and shiftsHeadcount or “the team”
LaborTwo people out / on-call hangover shows up in the planFantasy five-person week
CutOne named thing you will not test, with why“We will try to get to it”
RisksThree, each with an owner and a bite planA laundry list or CI-is-green as the only evidence
PeopleJordan/PIP or equivalent is a staffing fact, not gossipPersonality story
VP sentenceOne sentence they can argue withA slide about process

Green CI alone is never a pass.

When members exist, this paper is what you could bring to a Leadership Circle. Until then, writing it is the practice.