You have a 1:1 with a developer in four minutes. You glance at your calendar, try to remember what you talked about last time, scan Slack for anything obvious, and walk in with some version of "So… how's it going?" Sound familiar? You're not alone. Most engineering managers do this. Not because they don't care — but because doing it properly is unreasonably hard.

The prep tax

A good 1:1 should be grounded in what's actually happening. That means checking recent commits, open PRs, sprint progress, meeting load, Slack activity, and whatever was flagged last time. Across GitHub, Jira, Google Calendar, and Slack, that's four tools minimum — each with its own UI, its own search quirks, and its own version of "what happened this week." For one direct report, that's maybe ten minutes of clicking around. Multiply that by six or eight reports and you've burned over an hour just preparing to have conversations. Most managers don't have that hour. So they skip the prep, rely on memory, and hope their reports will surface anything important. Sometimes they do. Often they don't.

What gets missed

The cost of winging it isn't dramatic. It's quiet. It's the senior engineer who's been reviewing everyone else's PRs but hasn't shipped her own work in two weeks — and nobody's asked if she's stuck or just overloaded. It's the new hire whose commit frequency dropped after week three, right when the onboarding buddy moved to another project. It's the mid-level dev who's been committing at midnight for the past month because he doesn't know how to say no to a side request from product. None of these situations are crises. All of them are heading somewhere you'd rather catch early. But they don't show up in standup. They don't appear in sprint retros. They live in the gaps between your tools, visible only if you go looking — and you don't have time to go looking for every person, every week.

The memory ceiling

There's a threshold every engineering manager hits. Somewhere between four and seven direct reports, your ability to hold each person's context in your head starts to break down. Below that number, you can usually get by on instinct and casual observation. Above it, things start slipping through.

This is when managers start hearing things in 1:1s that they wish they'd known a week earlier. "Oh, I've been blocked on that for a few days." "Yeah, the on-call shift last week was rough." "I've been picking up a lot of reviews for the new team." These aren't failures of the engineer to communicate. They're failures of the system to surface what matters. Your reports shouldn't have to be the ones flagging that they need attention — that's your job. But your job is impossible without information, and the information is scattered across half a dozen tools that weren't built to talk to each other.

Why "just check the dashboards" doesn't work Some teams try to solve this with existing tooling. Engineering metrics dashboards, DORA metrics, velocity charts. These help at the team level, but they're almost useless for the kind of individual, human-level questions that make 1:1s matter. A velocity chart can tell you that sprint points went down. It can't tell you why. A GitHub contribution graph shows commit frequency but says nothing about whether someone's been pulled into an unreasonable number of reviews. A calendar heatmap shows meeting density but not whether those meetings are the kind that drain energy or the kind that don't.

The signal you need for a good 1:1 isn't a metric. It's a pattern — and it usually only becomes visible when you look across tools, across weeks, and through the lens of "what's changed for this person?"

Two minutes instead of ten

The fix isn't working harder at preparation. It's changing what preparation looks like. Imagine opening a single view two minutes before your 1:1 that shows you: this person's PR activity is down this week but their review load is way up. They had three after-hours commits on Tuesday. Their meeting density has increased 40% since last month. Here are two or three conversation starters based on what's actually happening.

You don't need to memorise anything. You don't need to cross-reference four tools. You walk in with something real to talk about, and your report feels like you're paying attention — because you are. The real cost of not preparing

Engineering managers often underestimate what good 1:1 preparation does for retention. Developers don't usually leave because of one big thing. They leave because of an accumulation of small things that nobody noticed. The slow creep of too many meetings. The feeling that their work isn't visible. The sense that their manager doesn't really know what they're doing day to day.

A well-prepared 1:1 quietly counteracts all of this. It says: I see what you're working on. I notice when something's off. I'm here before you have to ask. That's not a productivity hack. It's the core of the job.

TeamPlot

TeamPlot pulls signals from the tools your team already uses — GitHub, Jira, Slack, Calendar — and gives you a two-minute briefing before every 1:1. It spots patterns like after-hours work, review bottlenecks, and quiet periods so you can walk into every conversation prepared. Start free with up to 9 seats →