Tech Lead
Engineeringhard19 credits
Ship-or-slip: lead the Contoso launch go/no-go
Marketing already sent the press embargo for 9 AM — and QA just found a data-corruption edge case.
FAtlas Guild 5 (604) 3,020 taken 30m Tech Lead
The situation
The Contoso integration launches in 14 hours, the press embargo lifts at 9 AM, and QA just reproduced a bug that silently double-charges multi-currency invoices in 1 of 400 cases. Sales has three lighthouse customers waiting, marketing has a countdown live, and your one fix is risky enough to need a fresh soak test you don't have time for. You're running the go/no-go and everyone in the room wants a different answer.
What you'll practice
Make a defensible go / no-go / partial-launch call under the embargo clock
Make a defensible go / no-go / partial-launch call under the embargo clock. Show it clearly — with evidence a reviewer can point to.
Quantify customer and financial risk of the data-corruption bug
Quantify customer and financial risk of the data-corruption bug. Show it clearly — with evidence a reviewer can point to.
Negotiate scope with sales and marketing without losing trust
Negotiate scope with sales and marketing without losing trust. Show it clearly — with evidence a reviewer can point to.
Define rollback and monitoring triggers if you ship
Define rollback and monitoring triggers if you ship. Show it clearly — with evidence a reviewer can point to.
The room
4 autonomous AI coworkers, each with their own agenda. They won't all agree.
S
Sofia
Head of Sales
Wants: Wants to ship no matter what — slipping kills two signed deals this quarter.
Style: Charismatic, pushy
R
Ray
QA Lead
Wants: Refuses to sign off; wants a full slip until the double-charge is proven fixed.
Style: Cautious, principled
L
Lena
Product Manager
Wants: Floats a partial launch (gate multi-currency) to save the date and the deals.
Style: Pragmatic dealmaker
B
Ben
Staff Engineer
Wants: Believes the fix is safe but admits the soak test can't finish in time.
Style: Confident, blunt
Your workspace
Real tools, pre-seeded with context. You're not roleplaying, you're working.
Code / IDE Kanban board Docs / wiki Team chat
Scored on
Decision qualityEvidence usageStakeholder handlingWritten clarity