Periagoge
Concept
8 min readagency

ChatGPT for Engineering One-on-Ones: Prepare Better in Less Time

Pre-prepared one-on-one agendas and follow-up notes keep meetings focused on real issues rather than improvisation while freeing time for deeper listening. The preparation matters most; shallow agendas produce shallow conversations regardless of who generates them.

Aurelius
Why It Matters

Engineering leaders spend 6-10 hours weekly in one-on-one meetings, yet many arrive underprepared due to competing priorities. ChatGPT transforms how engineering managers prepare for these critical conversations by analyzing team data, surfacing patterns, and generating thoughtful discussion topics in minutes. Instead of scrambling through scattered notes and metrics before each meeting, you can use AI to synthesize context from sprint reports, pull request activity, performance trends, and previous meeting notes. This allows you to shift from administrative preparation to strategic thinking—focusing on what really matters: developing your people, removing blockers, and building trust. For engineering leaders managing 5-15 direct reports, this isn't just about saving time; it's about showing up fully present and prepared for conversations that shape team culture and individual growth.

What Is ChatGPT for Engineering One-on-One Preparation?

ChatGPT for engineering one-on-one preparation is the practice of using AI to analyze team member activity, synthesize context, and generate personalized discussion frameworks before scheduled meetings. Rather than manually reviewing Jira tickets, GitHub contributions, Slack conversations, and previous notes, engineering leaders provide ChatGPT with relevant data and receive structured summaries, potential discussion topics, and coaching recommendations. This approach works by feeding ChatGPT information like recent project contributions, blockers mentioned in standups, code review patterns, or career development goals discussed previously. The AI identifies trends (like decreased PR activity or repeated frustrations with tooling), suggests empathetic questions to explore challenges, and helps you connect individual work to broader team objectives. It's not about automating the conversation itself—one-on-ones require human empathy and judgment—but about ensuring you arrive informed, thoughtful, and ready to focus on your team member rather than scrambling to remember context. The result is more meaningful conversations that strengthen relationships and drive growth.

Why This Matters for Engineering Leaders

Engineering one-on-ones are the highest-leverage activity for leaders, yet they're often the first thing to suffer when priorities collide. When you arrive unprepared, team members notice—it signals their growth isn't a priority and erodes psychological safety. Research shows that quality one-on-ones directly correlate with retention, engagement, and performance, but only 30% of engineers report having truly valuable conversations with their managers. The cost of poor one-on-ones compounds: top performers disengage, blockers go unresolved, and cultural issues fester. ChatGPT addresses the core constraint—time—allowing you to compress 30 minutes of preparation into 5 minutes while improving quality. By quickly surfacing patterns across multiple data sources, AI helps you spot early warning signs (like a previously engaged engineer becoming quiet) that human memory might miss. For managers handling 8-12 direct reports, this means consistently showing up prepared for every conversation, not just the squeaky wheels. The competitive advantage is clear: teams led by well-prepared managers ship 23% faster, report 35% higher satisfaction, and experience 40% less attrition. In today's talent market, losing a senior engineer costs $200K+ in recruiting, onboarding, and lost productivity—making effective one-on-ones a critical business capability, not a nice-to-have.

How to Use ChatGPT for One-on-One Preparation

  • Gather relevant context before the conversation
    Content: Start by collecting data about your team member's recent work and activity. This includes their last 2-3 weeks of commits and PRs from GitHub, Jira tickets they've worked on or commented on, relevant Slack conversations where they raised concerns or questions, and notes from your previous one-on-one. Don't manually summarize—just copy the raw data. For example, export their last 10 pull requests with descriptions and comments, grab their sprint board showing completed and in-progress work, and include any documented goals or career development items. The key is providing ChatGPT with actual specifics rather than your interpretation, which allows the AI to identify patterns you might miss.
  • Ask ChatGPT to synthesize patterns and themes
    Content: Paste the context into ChatGPT with a prompt asking it to identify trends, potential concerns, and noteworthy achievements. Request that it highlight any changes in behavior (like decreased participation or velocity shifts), flag potential blockers or frustrations, note technical growth areas based on code contributions, and identify opportunities to recognize wins. For instance, ChatGPT might notice that a team member has been exclusively fixing bugs rather than building features, suggesting they may feel stuck on maintenance work. Or it might identify that someone who usually provides thorough PR reviews has become terse, potentially indicating burnout or disengagement.
  • Generate a structured discussion framework
    Content: Ask ChatGPT to create a prioritized agenda based on the patterns it identified. This should include 3-5 specific open-ended questions tailored to the individual's situation, suggested recognition points for accomplishments (with specifics), potential career development topics based on their work and goals, and any clarifying questions about blockers or concerns. The framework should guide conversation, not script it—you need flexibility to follow where the discussion naturally goes. For example, if ChatGPT identifies that someone completed a complex database migration, it might suggest asking how they approached the technical challenges and what they learned, rather than just saying 'good job.'
  • Prepare coaching or support strategies
    Content: If the synthesis revealed challenges—technical struggles, team dynamics issues, or career frustration—ask ChatGPT for coaching approaches. Provide additional context about your team, company resources, and the individual's goals, then request specific strategies. For instance, if someone is struggling with system design decisions, ChatGPT might suggest pairing them with a senior architect for the next project, recommend specific learning resources, or propose breaking down their current work into smaller design review opportunities. The AI can help you think through multiple approaches before the conversation, so you arrive ready to offer concrete support rather than vague encouragement.
  • Document outcomes and action items
    Content: Immediately after the one-on-one, use ChatGPT to help structure your notes and follow-through. Dictate or paste key discussion points, commitments you made, and action items, then ask ChatGPT to organize them into a clear summary you can share with the team member. This ensures accountability and provides continuity for the next conversation. For example, the AI can format notes into categories like 'Current Projects Discussion,' 'Career Development,' 'Blockers Identified,' and 'Manager Action Items,' making it easy to track commitments over time and ensuring nothing falls through the cracks between meetings.

Try This AI Prompt

I'm preparing for a one-on-one with Sarah, a senior backend engineer on my team. Here's her recent activity:

Pull Requests (last 2 weeks):
- #847: Refactored payment processing service (merged, 2 approvals)
- #851: Fixed critical bug in auth flow (merged, fast-tracked)
- #856: Database query optimization for user service (in review)

Jira Activity:
- Completed: 3 bug fixes, 1 technical debt ticket
- In Progress: Database performance improvement epic
- Commented on 5 tickets raising concerns about test environment instability

Previous one-on-one notes (3 weeks ago):
- Interested in learning more about distributed systems architecture
- Mentioned feeling reactive lately, wants more strategic work
- Action item: I promised to discuss potential tech lead path

Please analyze this information and provide:
1. Key patterns or themes you notice
2. Potential concerns or opportunities
3. 4-5 specific, open-ended questions I should ask
4. Suggested recognition points
5. A recommended discussion structure for our 30-minute meeting

ChatGPT will provide a structured analysis identifying that Sarah is doing strong technical work but may be frustrated by reactive bug-fixing and test environment issues. It will generate thoughtful questions about her experience with the recent critical bug, whether the test environment problems are blocking her strategic work, and how the database performance project connects to her distributed systems interests. The AI will also suggest recognizing her fast response on the critical auth fix while exploring whether she wants to continue being the go-to person for urgent issues or shift toward more planned architectural work.

Common Mistakes to Avoid

  • Treating ChatGPT output as a script instead of a discussion guide—one-on-ones must be genuine conversations, not interrogations following AI-generated questions verbatim
  • Providing only high-level summaries instead of specific data—ChatGPT needs actual examples (PR descriptions, specific Slack messages, concrete project details) to identify meaningful patterns
  • Using the same generic prompt for every team member—each person has unique circumstances, goals, and communication styles that require tailored preparation approaches
  • Forgetting to remove sensitive information before pasting into ChatGPT—always sanitize salary discussions, performance improvement plans, or confidential business information
  • Over-relying on AI analysis without adding your own context—ChatGPT doesn't know about hallway conversations, team dynamics, or personal circumstances that should inform your approach
  • Skipping the human review step—always read through ChatGPT's suggestions critically and adjust based on your knowledge of the person and situation before the meeting

Key Takeaways

  • ChatGPT compresses one-on-one preparation from 30 minutes to 5 minutes by synthesizing team member activity, patterns, and context across multiple data sources automatically
  • The AI excels at spotting trends humans miss—like behavior changes, repeated frustrations, or unrecognized contributions—by analyzing data without recency bias or selective attention
  • Effective preparation requires specific data inputs: actual PR descriptions, Jira comments, Slack messages, and previous notes, not just your memory or high-level summaries
  • Use ChatGPT as a preparation assistant that surfaces insights and generates discussion frameworks, but always bring human judgment, empathy, and relationship context to the actual conversation
  • The ROI is significant: better-prepared one-on-ones directly improve retention, engagement, and performance while reducing the cognitive load on engineering leaders managing multiple direct reports
Helpful guides
Aurelius
Work & Leadership
Related Concepts
Peri
Questions about ChatGPT for Engineering One-on-Ones: Prepare Better in Less Time?

Peri can explain this concept, give practical examples, help you decide whether it applies to your situation, or recommend a journey if appropriate.

Ready to work on ChatGPT for Engineering One-on-Ones: Prepare Better in Less Time?

Explore related journeys or tell Peri what you're working through.