3.2 - The one-on-one playbook: Debugging mental blocks
One-on-one (1:1) meetings are your most powerful operational sensor as an Engineering Manager. However, most new managers waste this time by turning it into a status update. If you are asking, "What is the status of Jira ticket #402?", you are doing it wrong.
As a Tech-Led Coach, you must treat 1:1s the same way you treat debugging a complex system: you are looking for hidden memory leaks, race conditions, and infinite loops inside the human mind.
Shift from status to alignment
Status updates belong in daily standups or Slack channels. The 1:1 is a dedicated space for career growth, emotional alignment, and uncovering invisible roadblocks before they become major incidents.
Use this simple structural framework for a 30-minute 1:1:
- 10 Minutes: Their Agenda. Let them drive. What is on their mind? What are they struggling with?
- 10 Minutes: Your Agenda. Share wider business context, provide feedback, or discuss upcoming architectural changes.
- 10 Minutes: Career & Growth. Discuss long-term goals. Are they learning? Are they bored?
The "debugging" script for 1:1s
Engineers are often introverted and may not volunteer information about burnout or frustration. You need to ask the right questions to pull the data out.
To debug burnout and workload:
- "What was the most frustrating part of the codebase to work with this week?"
- "If you had a magic wand to fix one process on our team, what would it be?"
To debug motivation and career alignment:
- "Are you feeling appropriately challenged by your current tasks, or are you operating on autopilot?"
- "What is one technical skill you want to learn in the next three months, and how can I find a project that helps you practice it?"
To debug team dynamics:
- "Who on the team has been the most helpful to you recently?"
- "Is there anything slowing you down that I can remove from your plate?"
Documenting the variables
Just like you would log errors in a system, you must keep a private log for each direct report. Track their goals, their frustrations, and the promises you have made to them. When you remember a small detail from three weeks ago and act on it, you prove that you genuinely care.
Delivering feedback with the SBI model
From practical experience, the SBI (Situation-Behavior-Impact) model is one of the most effective tools to use during 1:1s. Whether you are giving applause for a job well done or critical feedback to correct a problem, SBI helps staff improve significantly by removing emotion and focusing on facts:
- Situation: "In yesterday's sprint planning..."
- Behavior: "...you stepped up and clearly outlined the technical risks of the new feature..."
- Impact: "...which helped the product team adjust the timeline before we committed to an impossible deadline."
Using this structure prevents feedback from sounding like a personal attack and ensures your praise feels genuine and specific.
🎯 Self-Reflection for You
- Look at your calendar for your next 1:1. Are you prepared to discuss the engineer's career, or were you planning to just ask for a project update?
- Do you know the long-term career goal of every single person on your team?
If your 1:1s feel awkward, forced, or unproductive, let's redesign your communication scripts together in a virtual coffee chat.