LEADERSHIP SCENARIO

The Quiet Resignation

3-5 day simulationIntermediate

Nadia Patel is your best engineer. Sprint velocity is fine. Deliverables ship on time. But something shifted three months ago, and you can feel it in the spaces between her emails — shorter, more efficient, stripped of everything that isn’t task execution. Your director just asked you to nominate someone for tech lead. Nadia’s the obvious choice. She declined.

From
Lisa Huang
Subject
AI feature sprint priorities — quick sync

Hey, Hope you had a good weekend! Quick note on this week's priorities. The AI feature push is in full swing and I want to make sure we're aligned on the sprint deliverables: - Dashboard endpoint needs to be wrapped by EOD Wednesday for the Thursday client demo - Nadia's auth integration is the critical path — everything else sequences off it - Ryan's been great about picking up the caching layer work Also, I heard from your director that they're looking at tech lead nominations for the next rotation. Nadia seems like the obvious pick from your team...

THE SITUATION

The signals are in what’s missing

Three months ago, DataFlow cancelled Project Lighthouse — the internal data platform your team spent months building — to chase an AI feature push. Nobody complained. Nobody pushed back. Nadia just... adjusted.

She still ships. She still answers questions. But the extra context she used to volunteer, the ideas she used to float in threads, the opinions she used to have about architecture decisions — gone. Replaced by "Noted" and "Will do" and emails that answer exactly what was asked and nothing more.

Your Product Manager is focused on the Thursday demo. A junior engineer on the team has quietly started picking up work that used to be Nadia’s territory.

And you’re staring at a tech lead nomination form with Nadia’s name on it, knowing that the person you’d be nominating doesn’t exist anymore.

WHAT YOU'LL PRACTICE

4 leadership skills, one scenario

Detecting disengagement beneath good metrics

Sprint velocity won’t tell you someone has mentally resigned. Learn to read the signals that live in tone, initiative, and absence.

Naming what you see without softening it

The conversation Nadia needs isn’t "how are you doing?" It’s something more specific and harder to say.

Navigating competing pressures

Your PM needs the Thursday demo. Your director wants a tech lead nomination. Nadia needs something nobody has asked about yet.

Offering something concrete

Empathy without action is just observation. The scenario tests whether you can move from "I see you" to "here’s what I’m willing to do."

HOW IT WORKS

From inbox to insight

1

Receive Lisa’s email

A sprint priorities message that seems routine. Every detail in it is a signal.

2

Reply naturally

Your real email, your real words. No interface, no templates.

3

The team responds

Nadia, Ryan, and Lisa react based on your tone, your timing, and what you choose to address.

4

Navigate 4–6 exchanges

Each reply shapes trust, surfaces or buries information, and moves the clock.

5

See the outcome

Nadia stays and reinvests, or Nadia stays and keeps going through the motions, or Nadia leaves.

6

Get your debrief

A personalized coaching assessment: what you saw, what you missed, and what your communication patterns reveal.

Start this scenario

Already playing? Log in

Nadia is waiting for your reply

The metrics say everything’s fine. You know it isn’t. The question is whether you’ll write the email that opens the real conversation — or the one she can nod through.

Start The Quiet Resignation

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