How to Architect Stay Interview Meeting Agenda in Microsoft Teams: Operational Blueprint

Behind the surface request, the real problem this template addresses is regretted attrition becoming visible only post-resignation when interventions are no longer available. Calibrated to the workflow signature of people operations partners balancing employee experience against scaled communication needs, the template wires stay-conversation cadence into the structure itself so the post produces durable regretted-attrition tracking rather than one-time alignment. Building a proactive retention conversation cadence where stay interviews happen before resignation rather than after. The downstream outcome is a Teams channel where retention posts are scannable, ownable, and accountable — converting communication overhead into compounding operational signal.

The Core Blueprint

Software Environment: Teams (Enterprise AI: Copilot, ChatGPT, Claude, etc.)
Role Focus: HR
Execution Complexity: Advanced Logic
Taxonomy Tag: #RETENTION

PROMPT TEMPLATE

"Build a stay interview agenda exploring what they love, what frustrates them, growth aspirations, what would make them leave, and what would make them stay longer."

1.1k RUNS

Strategic Use Cases

By enforcing markdown layouts and conciseness, this prompt prevents miscommunication during critical chat blasts:

Surfacing flight-risk signal early enough to intervene, without creating a surveillance dynamic that itself erodes engagement.

Building a proactive retention conversation cadence where stay interviews happen before resignation rather than after.

Execution Workflow

Broadcast your formatted alert without breaking chat etiquette:

1
Open the appropriate HR or people-operations Teams channel and stage the prompt; double-check that any references to policy, benefits enrollment, or sensitive personnel context are accurate and reviewed.
2
Substitute the bracketed variables with situation specifics — names, dates, owners, scope — without restructuring the scaffold itself; the scaffold encodes stay-conversation cadence that arbitrary edits will quietly destroy.
3
Publish into the channel, immediately tag named owners in thread replies, and link any pre-reads or referenced artifacts so the post stands alone as a self-contained record rather than a placeholder for context that lives elsewhere.

Advanced Optimization

Tailor the chat output for maximum asynchronous impact by modifying the core snippet:

Early Conversation
"...stay conversations happen on a cadence, not when a signal triggers; trust requires routine, not surveillance."
Intervention Specificity
"...interventions are scoped to what's actually within the manager's control; vague promises destroy trust faster than no intervention."
Regretted-Attrition Discipline
"...exit data is mined for patterns, not just collected; without aggregation, exits stay anecdotal."