1-on-1s for engineering managers: a 30-minute ritual that prevents resignations

Why 1-on-1s die in delivery-driven companies

In a services company every hour has a visible price. Client work is revenue; everything else is cost that shows up in the utilization number someone reviews weekly. So when a sprint slips or a client calls, the 1-on-1 is the first meeting to get bumped — it has no deadline, no client, and no immediate consequence for skipping.

That's the trap: the consequence is real, just delayed and unattributed. A 1-on-1 skipped in March doesn't hurt in March. It hurts in September, as a resignation that "came out of nowhere" — from an engineer whose frustration had no scheduled place to surface, so it surfaced as a signed offer from somewhere else. The conversation happens anyway in the end — as a counteroffer negotiation, with a fraction of the leverage and none of the goodwill.

There's a second, quieter death: 1-on-1s that survive on the calendar but rot into status meetings. "How's the ticket going?" is delivery management wearing a 1-on-1's clothes — the project gets discussed because it's the easiest thing to discuss, and the person never is.

The fix for both is the same: a format cheap enough that billable pressure can't justify killing it, and rules that keep status out.

The 30-minute format that survives

Cadence: every two weeks, 30 minutes, recurring, per pair. Weekly during onboarding or a rough patch; never rarer than monthly — below that it's not a ritual, it's an event. Thirty minutes is small enough to defend: a busy week can't argue with half an hour, and a short meeting that always happens beats a long one that usually doesn't. Missed one? Reschedule, don't skip — the skip teaches everyone the meeting is optional.

The report owns the agenda; both sides add to it between meetings. Thought of something on Tuesday? Onto the shared agenda, not into a chat message that's buried by Thursday. An agenda both people built during the fortnight is what makes the meeting worth having — and a chronically empty one is a signal in itself (more below).

No status updates. Status lives in the tracker and the standup. If a project comes up, it's the person's relationship to it — stuck, bored, stretched, proud — not the burndown.

Three questions cover most of what matters:

1. "What's slowing you down or wearing you out?" — friction and load, caught before they compound.
2. "What do you want more of?" — growth, project fit, the thing they'd regret not getting.
3. "What should I do differently?" — asked every single time, so that around the fifth time it gets a real answer.

End with action items, written down, with names — and open the next meeting by reviewing them. A 1-on-1 whose action items evaporate teaches people the talking was decorative.

Private notes: candor needs a guarantee

During a 1-on-1 a manager hears things that must be remembered and must not be published: "I'm close to burning out", "the client's PM keeps bullying our QA", "a recruiter reached out and I took the call". A manager who writes that down honestly is doing the job. A manager who suspects HR, an admin, or the owner might read it will write something else — vague, polished, useless. Notes that might be read by someone else aren't notes; they're performance.

So the guarantee matters more than the note-taking feature: private manager notes must be readable by their author and no one else — not HR, not admins, not the owner. A policy promise ("we don't look") is weaker than a system property ("we can't"): if the permission model genuinely cannot show the note to anyone but its author, the manager can write the truth.

Two things deliberately not private: the shared agenda (both sides see and build it) and action items (commitments need witnesses). That split is the design: shared commitments, private candor. One document trying to be both ends up being neither.

The early-warning signals a 1-on-1 surfaces

Almost nobody resigns abruptly; they resign gradually, then abruptly. The gradual part shows in 1-on-1s months before it shows anywhere else — if you know what to listen for:

• The agenda goes empty. Someone who used to bring topics now has "nothing, all good". Disengagement rarely announces itself; it just stops contributing.
• Complaints stop. Counterintuitive but reliable: complaining is investment — people push on what they still expect to improve. The engineer who complained about the deploy process for two months and then went quiet didn't get happy; they stopped expecting.
• Growth questions disappear. When "can I get a harder project?" and "what's the path to the next grade?" stop coming up, the ambition usually moved somewhere you can't see it.
• Answers get shorter and more polite. Candor shrinking into courtesy is distance, measurable meeting to meeting.
• They start rescheduling. Occasional conflicts are life; a pattern of deferrals from their side often means the conversation has become something to manage.

None of these is proof — people also go quiet over a mortgage or a newborn. But two or three together are worth naming gently: "You've seemed further away these past few weeks — what's going on?" Asked three months early, that question changes outcomes; asked the day the resignation letter arrives, it's a formality. It's also where 1-on-1s and eNPS compose: the anonymous survey says something is off; the 1-on-1 is where you learn what.

How Helia HR does this

The 1-on-1s pack ($1/employee/mo — see pricing) is built around exactly this ritual:

• Cadence per pair — set the rhythm once per manager–report pair; the schedule stops depending on anyone's memory.
• A shared agenda both sides add to between meetings, so topics accumulate during the fortnight instead of evaporating in chat.
• Private manager notes, enforced at the database layer — readable only by their author. Not visible to HR, not to admins. The candor guarantee is a property of the system, not a policy.
• "What we discussed last time" — the previous conversation surfaces when you open the next one — what turns a series of meetings into a relationship.
• Action items — captured in the meeting, reviewed at the next one.

It pairs naturally with Reviews & Goals: when 1-on-1s happen all year, the review confirms rather than surprises.

FAQ

Weekly or bi-weekly?

Bi-weekly for most pairs; weekly during onboarding, a role change, or visible turbulence. The cadence you will actually keep beats the cadence that sounds committed — a never-skipped fortnightly meeting builds more trust than an often-cancelled weekly one.

What if the person says they have nothing to discuss?

Once — fine: run the three questions anyway; they usually generate the agenda "nothing" was hiding. Repeatedly — that's not an empty agenda, that's a signal from the early-warning list above — name it in the meeting itself.

Should skip-level 1-on-1s replace manager ones?

No — they answer different questions: the manager 1-on-1 is the working relationship; a skip-level (founder with the engineer, occasionally) checks its health from the outside. Quarterly is plenty — and only if the manager knows they happen and nobody treats them as an appeals court.

Do 1-on-1s still matter in an 8-person team that talks all day?

Daily contact is about the work; the 1-on-1 is scheduled permission to talk about the person. Founders keep discovering that someone they spoke with daily had been unhappy for months — proximity produced zero occasions to say it. Half an hour a fortnight is cheap insurance against exactly that.