The 1:1 template that cut my engineering attrition from 22% to 6%
Most engineering 1:1s are status updates with extra steps. Here's the four-question structure I borrowed from clinical coaching and rolled out across 40 EMs.
When one HR leader took over a 180-person engineering org in 2023, annualized regrettable attrition was running at 22%. They didn't change comp, didn't change scope, didn't reorg. They changed one thing: every EM ran the same four-question 1:1, every two weeks, no exceptions. Twelve months later, regrettable attrition was 6%.
- What's the most energizing thing you worked on since we last talked — and what's the most draining? (Energy audit.)
- Where did you feel blocked, slowed down, or unsupported in the last two weeks? (Friction audit.)
- If you imagine yourself 12 months from now, what skill or scope do you wish you'd grown into? (Growth audit.)
- Is there anything you've been holding back from telling me? (Trust audit.)
- Manager asks: 'How's the project going?'
- Engineer recites JIRA tickets.
- Manager nods, adds two action items.
- Nothing changes between meetings.
- Manager asks about energy and friction.
- Engineer surfaces things they wouldn't put in Slack.
- Manager removes one blocker per meeting, on average.
- Trust compounds. Surprises stop being surprises.
Amy Edmondson's foundational research on psychological safety shows that team performance correlates more strongly with whether team members feel safe to speak up than with almost any other variable, including individual talent. The four-question 1:1 is, mechanically, a psychological safety ritual. The 'trust audit' question ('is there anything you've been holding back from telling me?') gives the engineer explicit permission to surface things they otherwise wouldn't — and over months of repetition, the permission generalizes to the rest of the relationship.
There's also a Hawthorne-effect read on why it works: people behave differently when they know they're being observed with curiosity rather than evaluation. The energy/friction questions explicitly observe what's working and what's slowing them down, with no implied judgment. Compare to the implicit observation in a status 1:1 ('are you on track?'), which feels like surveillance. Same meeting, different mechanism, very different outcomes.
A 90-engineer infra team, as one HR coach recounted, in 2023 had a 19% regrettable attrition rate and a 'we have great 1:1s' belief among managers. The HR team instrumented the meetings (with consent): the median 1:1 was 23 minutes, 18 of which were status. They rolled out the four-question template with a 5-minute pre-1:1 written reflection from each engineer. Six months later attrition was 7%. The complaint nobody anticipated: engineers said they were 'tired in a different way' because the meetings now required them to think, not just report. That's the whole point.
- Move all status to writing (Slack, Notion, async update) before your next 1:1.
- Send the 4 questions to every direct report this week as the new shared agenda.
- Ask them to spend 5 minutes pre-1:1 writing one sentence per question.
- In the meeting, listen first. Resist the urge to 'solve.' Your job is to remove blockers, not validate plans.
- Track one number for 12 weeks: blockers surfaced and removed per quarter.
- Run the 'trust audit' question even when you're sure the answer is 'no.' The point is the standing invitation.