How to prepare a 1:1 that actually matters
Most managers walk into 1:1s without any preparation. Not out of bad intentions — out of lack of time, or because they believe "it flows naturally." The problem is that without preparation, the 1:1 quickly drifts into a status meeting. And a status meeting is a meeting that could have been a Slack message.
Why the status 1:1 is a trap
The unprepared 1:1 always looks the same: "How are you?", "Any blockers?", "What's new?" The engineer answers politely. The conversation spins. Neither person leaves with anything actionable.
This isn't a matter of goodwill. It's a matter of context. Without recent context — what the person has been working on, commitments made together last week, tensions visible in their commits or calendar — you're navigating blind.
The status 1:1 has another side effect: it creates distance. The engineer eventually perceives that their manager is "doing their weekly 1:1" rather than having a real conversation. And gradually, they share less.
3 things to prepare before every 1:1
The good news: preparing a 1:1 doesn't take long. It takes 5 minutes if you have the right context at hand. Here's what you need before walking into the room (or opening the call).
1. Commitments from the last session
What was said in the last 1:1? What has been done since? Following up on commitments is the strongest signal of your managerial reliability. When you arrive saying "last week you mentioned you were going to talk to Claire — how did that go?", you send a clear message: you listen, you remember, you follow through.
2. The person's recent context
What have they been working on this week? Not to control them — to show you know what's going on. An "I saw you spent a lot of time on the Postgres migration on Thursday, how did that go?" completely changes the dynamic of a conversation. The person feels seen, not audited.
3. A real substantive topic
Not just "any blockers?" but an intentional question. About their 6-month trajectory. About a recent technical decision that seemed risky. About team dynamics. A good substantive question takes 2 minutes to prepare and can open 30 minutes of useful conversation.
Using context to go deeper
This is where the real difference plays out. A manager who arrives with context — Git activity, calendar events, notes from previous weeks — can bring up topics the engineer wouldn't have mentioned spontaneously.
"I noticed you had several back-to-back meetings on Thursday. How are you managing your workload right now?" That's a question that shows you're paying attention. That you care about the person's experience, not just their deliverables.
Same goes for technical activity. An engineer pushing lots of small late-night commits might be a signal. Not necessarily — but it's worth paying attention to. Not to monitor, but to support.
What it changes in the relationship
When an engineer sees their manager arrive prepared, something shifts. Trust builds. Conversations become more candid. Difficult topics are easier to raise because there's a real space, not just a routine check-in.
Conversely, the manager who arrives without context — even with the best intentions — sends a signal: "I didn't have time to prepare." Over time, this creates distance. The engineer unconsciously adjusts what they share based on what they think their manager will actually act on.
The prepared 1:1 isn't a control tool. It's an investment in the relationship. Five minutes before, so the thirty minutes together are truly worth it.
Going further
Preparing a 1:1 shouldn't take more than 5 minutes. But those 5 minutes change everything. They change the quality of exchanges, the level of trust, and ultimately the quality of your team's work.
That's exactly why we built Moston: so you arrive at every 1:1 with the context you need — without spending an hour digging through notes and tools. The AI brief gives you in 30 seconds everything you need for the conversation to matter.