The 1:1 is the single most important meeting on an engineering manager's calendar. Gallup found that employees with regular meaningful one-on-ones are almost three times as likely to be engaged (Gallup). 86% of highly engaged organizations use them, compared to only 50% of disengaged companies (PerformYard). And 80% of employees who received meaningful feedback in the past week are fully engaged.
Yet most 1:1s are bad. They drift into status updates, get canceled when the calendar is tight, or become awkward silences punctuated by "so, how are things?" The problem is not the concept. It is the execution. Here is a template that fixes the execution.
The Core Template: 5-10-5
Thirty minutes. Three blocks. The structure is simple enough to remember without looking at a document, flexible enough to adapt to any conversation.
First 5 minutes: The report's agenda. The report speaks first. They bring what is on their mind: blockers, concerns, wins, frustrations. This section is non-negotiable. If the manager fills the first five minutes with their own topics, the report learns that the meeting is for the manager, and they stop preparing.
Research from Pluralsight's engineering leadership guide confirms: the most effective 1:1s are employee-driven, with the report preparing the initial agenda and sending it in advance (Pluralsight). This is where blockers get surfaced, frustrations get aired, and small problems get caught before they become big ones.
Middle 10-15 minutes: Growth, development, and feedback. This is the coaching block. It is where the 1:1 becomes something you cannot get from Slack, a standup, or a project management tool. Topics include:
- Career trajectory: "Where do you want to be in a year? What skills would get you there?"
- Skill development: "What new technologies or frameworks are you excited to explore?" (Echometer)
- Feedback exchange: one specific piece of positive feedback and one constructive observation, using the SBI framework (Situation, Behavior, Impact)
- Energy audit: "What is energizing you right now, and what is draining you?"
Google's Project Oxygen identified "is a good coach" as the number-one behavior of great managers (Google re:Work). This block is where coaching happens. If you are spending it on task reviews, you are wasting it.
Final 5-10 minutes: Manager items and action items. The manager shares context the report needs: upcoming changes, organizational updates, strategic direction. Then both parties confirm action items. Every 1:1 should end with at least one concrete next step for each person. Without action items, the meeting becomes a pleasant conversation that changes nothing.
The Questions That Surface Real Signal
Bad questions get bad data. "How are things going?" gets "fine." Here are open-ended questions that pull real signal, organized by category.
For blockers and workload:
- "What would make your work better this week?"
- "What is the thing you most want to get off your plate?"
- "If you could change one thing about how we work, what would it be?"
- "How do you balance staying current with emerging trends while managing your day-to-day tasks?" (Echometer)
For team health and dynamics:
- "How would you describe the team dynamic right now?"
- "Who on the team has done something great recently that I should know about?"
- "Is there a collaboration that is working well? One that is not?"
- "Do you feel safe pushing back on decisions? When was the last time you did?"
For growth and development:
- "What is the most interesting problem you worked on this week?"
- "What skill do you wish you were better at?"
- "Have you encountered any challenges recently that could lead to innovative solutions?" (Echometer)
- "What would you want to work on if you had two free days?"
For feedback and trust:
- "What is one thing I could do differently as your manager?"
- "Is there anything you have been hesitant to bring up?"
- "What is the most useful thing I have done for you recently?"
Research from Lattice's analysis of 50 top 1:1 questions confirms that all questions should be open-ended: yes/no questions do not get people talking effectively (Lattice). Rotate through these over several weeks. You do not need to ask all of them every time.
Variant 1: The Silent Report
Some engineers are introverts who process internally. Others have been trained by previous managers that 1:1s are about performing enthusiasm. Either way, the silence is not a problem to fix. It is a communication style to accommodate.
Send the template 24 hours ahead. Let them fill in their topics asynchronously. Some people do their best thinking in writing.
Use specific questions instead of open ones. "What was the hardest part of the deployment last week?" is easier to answer than "How are things going?" Specificity reduces the cognitive load of generating a response from scratch.
Try a different setting. Walking 1:1s, video-off audio calls, or even a shared document where you type back and forth can unlock people who freeze in the traditional face-to-face format.
Shorten the meeting. Twenty minutes with real content is better than thirty minutes of uncomfortable silence. As trust builds, the conversation will expand naturally.
Variant 2: The Skip-Level 1:1
Skip-levels (meetings between a manager and their reports' reports) are powerful calibration tools. They give you ground truth that may not surface through the reporting chain. Run them quarterly, 20 to 30 minutes.
The template is simpler. Three questions:
- "What is going well on the team?"
- "What is not going well?"
- "What should I know that I might not?"
The critical rule: never use information from skip-levels to overrule or bypass the middle manager. If you hear a concern, coach the middle manager on addressing it. Using skip-level intel to micromanage destroys trust in the entire chain.
Skip-levels also build organizational context for ICs who rarely interact with senior leadership. Share strategic direction, upcoming changes, and the reasoning behind recent decisions. The context itself is valuable; people work better when they understand the bigger picture.
Variant 3: The First 1:1 With a New Team Member
The first 1:1 sets the tone for the entire relationship. It deserves its own template. Budget 45 to 60 minutes.
Introductions (20 minutes). Share your management style, your communication preferences, and what you care about. Ask about their working preferences: when they do their best work, how they prefer to receive feedback, what their communication style looks like under stress (Medium/Linn Foster).
Expectations alignment (20 minutes). What does success look like in their role over the next 90 days? What does a great 1:1 look like to them? What are their non-negotiables (e.g., "I need focus time in the mornings," "I do not respond to Slack after hours")? Agree on how you will work together. This is a social contract, and it matters more than most managers realize.
Previous manager learning (5 minutes). "What did your previous manager do that worked well? What did they do that did not?" This question gives you a cheat code. You learn their preferences and pain points in one conversation instead of discovering them through months of trial and error.
The Anti-Patterns: What Breaks 1:1s
Canceling when busy. Canceling 1:1s sends the message that the report is lower priority than whatever else is on your calendar. Gallup's engagement data is built on consistency. Missing a week occasionally is fine. Regularly canceling is corrosive. If you must reschedule, reschedule, do not cancel.
Turning it into a status update. If you spend the entire 30 minutes reviewing task progress, you have a status meeting. Status belongs in standups, project tools, or async channels. The 1:1 is for the things that only surface in a private, trust-based conversation: career concerns, interpersonal friction, burnout signals, and honest feedback. Protect that space.
Manager monologuing. If the manager talks for more than 40% of the meeting, the ratio is wrong. The report should drive 60% or more of the conversation. Your job is to listen, ask follow-up questions, and coach, not to lecture.
No follow-through on action items. If you agree to do something and do not do it, trust erodes. Track action items in a shared document. Review them at the start of each 1:1. 70% of the variance in engagement comes from the manager (Gallup); broken commitments directly undermine that trust.
What 1:1s Cannot Tell You
1:1s reveal what individuals choose to share with you. They do not reveal the full picture of team dynamics between meetings. A report might tell you they are fine while the team around them is fragmenting. Someone might not surface a conflict because they do not feel safe doing so. 1:1s are necessary but not sufficient for understanding team health.
This is where complementary tools matter. QuestWorks is the flight simulator for team dynamics: it surfaces behavioral patterns that show up when teams work through scenarios together but might never come up in a 1:1. QuestDash gives managers visibility into team dynamics in the gaps between one-on-one conversations. HeroGPT provides private coaching to individuals. The platform runs on its own cinematic, voice-controlled environment (it integrates with Slack for onboarding and coaching, but the quests happen on QuestWorks' own platform). 1:1s tell you what one person shares with you. A team dynamics platform tells you what the team reveals through its behavior.
Putting It Together
The template is simple: 5-10-5, employee-driven, coaching-focused, action-item-anchored. The execution is what matters. The best template in the world is useless if you cancel every other week or fill it with status updates.
Start this week. Send the template to your reports. Ask them to prepare their agenda for the next meeting. Use one question from the list above that you have never asked before. See what surfaces. The data says this is the highest-leverage 30 minutes you will spend all week.
For the broader framework on engineering management practices, see how to be a better engineering manager. For tools that complement your 1:1 practice, check out the best tools for new engineering managers. And for the trust-building foundation that makes 1:1s work in the first place, read our guide on building trust on a remote team.