The Trade-Off

3-5 day simulationIntermediate

At 6:47 AM, a production incident took down billing for two hours. Alex Rivera, your most experienced engineer, stayed up investigating and found the root cause — an architectural weakness in the payment queue. Your VP needs a postmortem for the exec meeting. Your PM needs the client demo Friday. Alex says the proper fix takes two weeks. You have to choose.

Start this scenario See how it works

Already playing? Log in

From

Alex Rivera

Subject

Post-incident: billing integration root cause

Hi Alex, Wanted to give you the full picture on this morning's billing outage before the noise starts. Root cause: race condition in the payment processing queue. When two batch jobs hit the same merchant account within a 200ms window, the locking mechanism fails silently and both transactions proceed with stale data. This isn't a new bug. It's an architectural weakness in how we handle concurrent writes. I've scoped the fix at roughly 2 weeks of focused work...

THE SITUATION

No right answer, just trade-offs

This morning’s billing outage is over. No data was lost, but 340 transactions failed. Alex Rivera found the root cause: a race condition that’s been lurking since Q3, and it will happen again in three weeks.

The proper fix requires redesigning the queue’s concurrency model — two weeks of focused work. A patch would just raise the threshold without eliminating the failure mode.

Your VP needs a postmortem ready for the exec team meeting. Your PM has a client demo Friday that depends on the same engineers who’d be doing the fix.

You can’t do all three perfectly. The question is which trade-off you’ll name — and which one you’ll pretend doesn’t exist.

WHAT YOU'LL PRACTICE

4 leadership skills, one scenario

Incident prioritization under pressure

A postmortem, a client demo, and a critical fix all need the same people at the same time. Learn to sequence without pretending you can do everything.

Naming trade-offs instead of promising everything

The most dangerous response to competing demands is "we’ll handle it all." Practice saying what you’re choosing — and what you’re not.

Balancing technical debt against business deadlines

The fix takes two weeks. The demo is Friday. The next outage is in three weeks. Every option has a cost.

Communicating upward when the news isn’t clean

Your VP wants a clear postmortem. The situation isn’t clear. Practice delivering honest assessments to leadership that doesn’t want ambiguity.

HOW IT WORKS

From inbox to insight

Receive Alex’s post-incident email

A detailed technical breakdown that ends with a warning: this will happen again in three weeks.

Reply with your priorities

Your real email, your real words. What you address first signals what matters most to you.

Alex, Priya, and Jordan respond

Your engineer, your PM, and your VP each react based on what you chose to address — and what you left out.

Navigate competing demands

Each reply moves the clock. Promises made to one person constrain what you can offer another.

See the outcome

The fix ships or it doesn’t. The demo goes well or it doesn’t. The postmortem is honest or it’s not.

Get your debrief

A personalized coaching assessment: which trade-offs you named, which you avoided, and what your patterns reveal.

Start this scenario

Already playing? Log in

Alex is waiting for your response

The incident is over. The hard part is what comes next — a postmortem that’s honest, a client demo that’s realistic, and a fix that actually gets scheduled. You can’t do all three perfectly. The question is which trade-off you’ll name.

Start The Trade-Off

New to Prism Signal? Start with The Burnout Blindspot — free, no credit card.