Written by: Mark Hull, Co-Founder and CEO, Exceeds AI | Last updated: April 22, 2026
Key Takeaways
- Engineering managers in 2026 need updated one-on-one templates to handle stretched ratios and AI-generated code now at 41% of global output.
- The 40-20-40 rule structures meetings for maximum impact: 40% engineer-led discussion, 20% analytics review, and 40% action planning.
- A 7-step timed agenda with check-ins, blockers, AI insights, growth discussions, and action items keeps 1:1s focused and effective.
- AI-specific questions on tool effectiveness, code quality, and productivity help you coach engineers and identify scalable best practices.
- Commit-level AI analytics from Exceeds AI turn every 1:1 into a concrete AI ROI conversation.
40-20-40 Time Split for High-Impact Engineering 1:1s
The 40-20-40 rule gives your one on one meeting templates a clear time split that balances engineer voice with data and planning. This framework allocates meeting time across three distinct phases, each with a specific purpose in the conversation.
| Phase | Time Allocation | Focus Area |
|---|---|---|
| Engineer-Led Discussion | 40% (12 minutes) | AI tool wins, blockers, adoption challenges |
| Analytics Review | 20% (6 minutes) | Code quality metrics, AI impact data |
| Action Planning | 40% (12 minutes) | Growth goals, coaching, next steps |
This breakdown shows how a typical 30-minute meeting divides time to balance engineer autonomy with manager oversight. Engineers drive the conversation, while managers bring data and structure to prove AI ROI and support growth.
How to Structure a 1 on 1 Meeting: 7-Step Timed Agenda
The 40-20-40 framework provides the philosophy, and this 7-step agenda gives you the tactical execution. This structure fits into a 30-minute window and keeps conversations focused, predictable, and actionable.
1. Check-in (5 minutes): Build personal connection and gauge energy and stress levels.
2. Progress Review (10 minutes): Cover recent wins, completed work, and key milestone updates.
3. Blockers & AI Insights (10 minutes): Discuss technical obstacles, AI tool effectiveness, and adoption challenges.
4. Growth Discussion (5 minutes): Explore skill development, career aspirations, and learning opportunities.
5. Action Items (5 minutes): Capture specific commitments, deadlines, and clear ownership.
6. Analytics Review (3 minutes): Look at code quality trends, productivity metrics, and AI impact data.
7. Close & Preview (2 minutes): Summarize decisions, preview the next meeting, and express appreciation.
This timed approach ensures comprehensive coverage while respecting busy schedules, which directly impacts engagement outcomes. Teams that institutionalize regular 1:1s experience nearly 3x higher engagement because the structured time allocation surfaces blockers early and builds trust through consistent, predictable conversations.
AI-Era One on One Meeting Questions for Engineering Teams
Targeted one on one meeting questions turn 1:1s into coaching sessions instead of status updates. Engineering managers in the AI era need questions that expose adoption patterns, quality impacts, and productivity gains at the individual level.
The table below highlights three critical question categories and explains why each one matters for coaching effectiveness.
| Category | Sample Questions | Why Ask |
|---|---|---|
| AI Adoption | “How effective is Cursor/Claude on your recent PRs?” | Identifies tool-specific success patterns |
| Code Quality | “What quality trends do you notice in AI-assisted code?” | Surfaces technical debt risks early |
| Productivity | “Which AI workflows save you the most time?” | Scales best practices across teams |
Top AI adopters achieve 2x PR throughput compared to low adopters, and that advantage depends on understanding individual adoption patterns. Questions like “Which dependency is most at risk and what is the fastest unblock?” help managers move from generic advice to precise, situational support.
Transform these questions into actionable insights. See which AI patterns actually drive results for your team — start your free pilot now.
What to Avoid in 1:1s and How to Scale as a Manager
High-trust one-on-one meeting templates avoid misusing 1:1 time for surveillance or basic status reporting. Skip updates that belong in team meetings and avoid surprise performance reviews that erode psychological safety.
Instead, focus on coaching and enablement as the core purpose of the conversation. The most effective way to achieve this coaching focus is through the 70/30 listening rule, which requires engineers to speak about 70% of the time while managers ask strategic questions and provide targeted support.
For managers stretched across larger teams, scaling this coaching model requires data-driven efficiency. Leading companies track AI usage patterns to identify “golden patterns” worth scaling versus “anti-patterns” requiring coaching. By bringing these pattern discussions into your 1:1 agenda, especially during the Analytics Review phase of the 40-20-40 framework, you turn meetings into high-leverage coaching sessions that systematically improve team performance.
Exceeds AI supports this shift by providing commit-level analytics that reveal which engineers effectively use AI tools and which ones struggle. Unlike metadata-only platforms like Jellyfish or LinearB, Exceeds analyzes actual code diffs to distinguish AI from human contributions, prove ROI, and highlight specific coaching opportunities.
Stop guessing about AI effectiveness. Turn your 1:1s into data-driven coaching sessions with commit-level analytics — start your free pilot.
Free 1:1 Templates Built for AI-Heavy Engineering Teams
This free one on one meeting template pack gives engineering managers flexible formats that all follow the same AI-aware structure. Each format supports a different workflow while reinforcing the 40-20-40 framework and 7-step agenda.
Word Template: A fully customizable document with AI-specific questions, the 40-20-40 layout, and space for detailed notes.
PDF Template: A print-ready version suited for offline meetings and consistent formatting across managers.
Excel Tracker: A spreadsheet for action item tracking, meeting history, and progress monitoring across multiple reports.
All templates include pre-populated sections for AI adoption discussions, code quality reviews, and productivity coaching. Managers can tailor questions to match their stack, including tools like Cursor, Claude Code, and GitHub Copilot, while keeping a consistent structure across the team.
Supercharge Your 1:1s with Exceeds AI Analytics
Templates provide structure, and Exceeds AI provides the data that makes those templates truly effective. Exceeds AI turns your one-on-one meeting templates into precision coaching tools by analyzing code at the commit and PR level.
Unlike traditional developer analytics platforms that only see metadata, Exceeds AI identifies which specific lines are AI-generated, tracks quality outcomes over time, and reveals which adoption patterns actually work. Managers can then coach with confidence, backed by objective evidence instead of intuition.
Setup takes hours, not months. Simple GitHub authorization delivers insights quickly, showing which engineers effectively use AI tools and which need targeted support. High-AI-adoption teams complete 21% more tasks and merge 98% more pull requests, and those gains appear when adoption is measured and managed with intention.
Ready to prove AI ROI while scaling best practices? Transform your 1:1s into data-driven wins — start your free pilot today.
Frequently Asked Questions
How do you structure a 1 on 1 meeting?
Structure effective 1:1s using the 7-step timed agenda: Check-in (5 minutes), Progress Review (10 minutes), Blockers & AI Insights (10 minutes), Growth Discussion (5 minutes), Action Items (5 minutes), Analytics Review (3 minutes), and Close & Preview (2 minutes). This 30-minute framework keeps the conversation focused while covering progress, blockers, growth, and follow-through. Engineers should speak about 70% of the time while managers guide with questions and targeted coaching.
What should not be discussed in a 1:1?
Avoid using 1:1s for surveillance, basic status updates that belong in team meetings, or surprise performance reviews. Skip detailed task management, project timelines better handled asynchronously, and broad team-wide announcements. Prioritize coaching, career development, blockers that need manager support, and feedback in both directions. The goal is building trust and enabling growth, not monitoring or micromanagement, so keep discussions confidential and centered on the individual.
What is the best format for a 1:1 meeting?
An effective format combines a clear time structure with templates that fit your workflow. Use Word documents for flexible agendas, PDFs for consistent formatting across the org, and Excel trackers for follow-up on action items. Schedule 30-minute sessions weekly or bi-weekly, with consistent timing and location. Prepare a shared agenda in advance, let engineers drive most of the conversation, and always include sections for wins, blockers, growth topics, and specific action items with owners and deadlines.
How can engineering managers prove AI ROI through 1:1s?
Engineering managers prove AI ROI by bringing concrete data into recurring 1:1 conversations. Ask specific questions about AI tool effectiveness, code quality trends, and productivity patterns, then pair those answers with metrics like PR throughput, review cycles, and incident rates for AI-assisted versus human-only code. Commit-level analytics highlight which engineers successfully adopt AI tools and which need coaching. Document the winning patterns and scale them across teams so leadership sees a clear link between AI investments and delivery outcomes.
What AI-specific questions should be included in engineering 1:1s?
Include questions that reveal adoption patterns and outcomes, such as “Which AI tools are most effective for your current work?” and “What quality differences do you notice in AI-assisted code?” Ask “Where do AI tools create blockers versus acceleration?” and “Which AI workflows should we scale to other team members?” Focus on concrete tools like Cursor, Claude Code, and GitHub Copilot instead of abstract AI talk. Probe for technical debt risks, review burden changes, and long-term maintainability concerns so you can coach effectively and tie AI usage to real business impact.