Scenario examples
When engineering and product managers are under delivery pressure, a one-to-one can become another status meeting. These scenarios help L&D leaders practice the moments that require curiosity, care, and sound judgment.
In fast-moving technology teams, the recurring one-to-one can easily become a tactical status update. These scenarios help L&D leaders define what managers should practice instead: asking useful questions, noticing changes without jumping to conclusions, discussing development, repairing trust, and making space for workload concerns.
The engineer insists everything is fine, but they have become quieter in team discussions and keep postponing a development goal they previously valued.
What good looks like: Asks open-ended questions, leaves silence, and creates enough psychological safety that the real issue finally surfaces.
A normally proactive product manager has stopped contributing to planning discussions and gives short, noncommittal answers about the upcoming quarter.
What good looks like: Names the observed change without diagnosing the cause, asks what has shifted, and explores workload, development, and role fit without pressuring the person to disclose more than they choose.
The report brings a detailed list of Jira tickets to the 1:1 and tries to spend the entire thirty minutes reviewing sprint progress.
What good looks like: Acknowledges the tactical work, then deliberately lifts the conversation to career growth, goals, and what the report wants to learn next.
During a recent post-mortem, the manager failed to back up the report, and now the 1:1 feels noticeably cold and guarded.
What good looks like: Names the elephant in the room, owns their part in the incident, and deliberately works to rebuild the relationship.
It is the final week of a major release. The report asks to cancel the 1:1 to focus on shipping, but the manager knows they are nearing burnout.
What good looks like: Protects the time, makes it count by focusing on workload and well-being rather than status, and signals the person matters more than the backlog.
In a skip-level check-in, an individual contributor says their direct manager may be creating unnecessary decision bottlenecks but hesitates to give specifics.
What good looks like: Validates the concern, asks probing but neutral questions, and gathers actionable feedback without undermining the direct manager.
Keep exploring
A practical guide for L&D leaders on building a first-90-days program that prepares new tech managers for managing former peers and handling hard conversations.
FrameworkA 90-day blueprint for L&D leaders to transition top individual contributors into capable tech managers, focusing on the critical conversations of the first three months.
DiagnosticA short scorecard for L&D leaders: how ready is your new-manager program to transition top ICs into capable leaders? Answer six questions for a benchmark.
Practice at scale
Let managers practice drawing out concerns and turning status updates into development conversations through realistic voice-based simulations.