Why Prep Matters
Most engineering managers have 5-8 direct reports. That's 5-8 weekly or biweekly 1:1s. Without preparation, these meetings default to status updates — which could have been an async standup.
Research from Google's Project Oxygen found that the single most important behavior of effective managers is being a good coach. You can't coach someone effectively if you don't know what they've been working on, what's blocking them, or how they're feeling.
The gap between a good 1:1 and a wasted one is usually 5 minutes of preparation. Here's how to spend those 5 minutes well.
The ROI of prep
A prepared manager asks "I noticed your PR has been open 4 days — need a review?" An unprepared manager asks "So, how are things?" The first conversation surfaces real problems. The second gets a polite "fine."
The 5-Minute 1:1 Meeting Prep Checklist
Before every 1:1, run through these five items. It takes less than 5 minutes and transforms the conversation.
Review their last standup updates
Know what they've been working on without asking
Check open action items from last 1:1
Follow up on commitments before they're forgotten
Look at goal progress
Discuss what's on track and what's slipping
Check for blockers or risk signals
Address problems proactively, not reactively
Review recent PRs or ticket activity
Acknowledge work and ask informed questions
What to Review Before Each 1:1
Standup Updates
If your team runs async standups, skim the last 3-5 entries. You're looking for patterns: repeated blockers, shrinking updates (a disengagement signal), or themes you want to dig into.
Action Items
Check what was committed to in the last session. Are items complete? Overdue? Never started? Following up on action items shows that 1:1s have consequences — they're not just talk.
Goal Progress
Active goals should move between sessions. If a goal has been at 60% for three weeks, that's a conversation worth having. At-risk goals deserve direct questions: "What would it take to get this back on track?"
Recent Work Output
For engineering teams, this means PRs, commits, and tickets. Not to micromanage — to acknowledge. "I saw your refactor of the auth service — that must have been gnarly" goes a long way.
Signals and Sentiment
If you have tools that detect sentiment shifts, burnout risk, or disengagement patterns — review them. These are the conversations that matter most and are easiest to miss without data.
Building a Prep Routine
The best prep routine is one you actually do. Here are three approaches, from minimal to comprehensive:
Minimal (2 minutes)
Review last check-in notes and open action items. Good enough to avoid repeating yourself and follow up on commitments.
Standard (5 minutes)
Review standups + action items + goals + recent activity. This is the sweet spot for most managers. Use the 5-minute checklist above.
Automated (30 seconds)AI-powered
Use a tool that aggregates everything into a prep brief. Open the 1:1, skim the brief, walk in prepared. The data review happens automatically.
Common Prep Mistakes
Relying on memory
Use a checklist or tool. You manage 6+ people — you will forget details.
Only discussing status updates
Status is available asynchronously. Use the 1:1 for coaching, feedback, and career growth.
Skipping prep when busy
An unprepped 1:1 wastes both people's time. Even 2 minutes of prep changes the conversation.
Not reviewing previous check-in notes
Patterns only emerge across multiple sessions. Review at least the last 2-3 check-ins.
Asking generic questions
Replace 'how are things?' with specific, data-informed questions about their actual work.
AI-Powered Prep: The Next Evolution
The manual checklist works — but it doesn't scale. If you manage 8 engineers and have biweekly 1:1s, that's 40 minutes per week just on prep. AI can reduce that to under 4 minutes total.
Modern tools like Vereda AI's prep briefs aggregate data from multiple sources and generate a prioritized brief automatically:
The key difference from generic AI (like pasting notes into ChatGPT) is that dedicated tools have access to your actual engineering data — standups, GitHub, Jira, goals, check-in history — so the prep brief reflects reality, not guesswork.
Prep Templates
If you're building a manual prep routine, start with one of these templates:
Weekly 1:1 Prep Template
Before the meeting:
- Review standup updates from the past week
- Check action items from last 1:1
- Note any blockers or concerns raised
- Check goal progress
- Review recent PR/ticket activity (acknowledge effort)
During the meeting:
- Start with their agenda (what do they want to discuss?)
- Address any signals or concerns
- Review goal progress together
- Discuss career development (at least monthly)
- Agree on action items with owners and deadlines
After the meeting:
- Write down key takeaways (shared + private)
- Log action items with deadlines
- Note any follow-ups for next session
Signal-Based Prep Template
For managers using tools with signal detection. Start with the highest-priority signal and work down:
Tools for One-on-One Meeting Prep
Here's how common approaches compare for engineering manager 1:1 prep:
Google Docs
Pros
Free, simple, familiar
Cons
No structure, no signals, no automation, nothing connected
Best for
Solo managers with 1-2 reports
Fellow
Pros
Nice shared agenda, integrations
Cons
No engineering-specific signals, no risk detection, no standup data
Best for
Non-technical teams wanting structured agendas
Lattice
Pros
Full performance suite
Cons
Enterprise pricing, no engineering-specific context, no live data in prep
Best for
Large HR-driven organizations
Vereda AI
Pros
AI prep briefs from live data, signal detection, risk scoring, standup integration
Cons
Engineering-focused (not general purpose)
Best for
Engineering managers who want data-driven 1:1s
Frequently Asked Questions
How long should I spend preparing for a 1:1?
5 minutes is the sweet spot. Review standups, check action items, glance at goals and recent activity. Any more than 10 minutes means your data is too scattered. AI tools like Vereda can reduce this to under 30 seconds.
What should I review before a 1:1 with an engineer?
Review their recent standups/updates, open action items from the last 1:1, goal progress, any blockers or risk signals, and recent PR or ticket activity. This gives you enough context to ask specific, meaningful questions.
How is 1:1 prep different for engineering managers?
Engineering managers have access to more data signals than other managers: PR activity, commit velocity, code review patterns, ticket throughput, and technical blockers. Good prep means reviewing these alongside the standard agenda items.
Can AI help with 1:1 meeting prep?
Yes. AI tools can aggregate data from multiple sources (standups, GitHub, Jira, previous check-ins) and generate a prep brief with talking points, risk signals, and conversation starters. This reduces prep time from 5-10 minutes to under 30 seconds.