The One-on-One Is Not a Status Meeting

As engineering leaders, we often get trapped in the daily grind. We want a bird's-eye view of every project, but we must remember: the one-on-one is not a status meeting. If your direct reports are just reading their Jira tickets to you, you are doing it wrong. A great manager acts as a force multiplier, not a micromanager who needs hands-on control over every single line of code.

The golden rule of one-on-ones is simple: the agenda belongs entirely to your report. This is their dedicated time to check in, air a concern, or discuss their long-term career aspirations. Your job is to listen, ask open-ended questions, and read between the lines. If you do all the talking, they will quickly become disengaged and drift away.

Earlier in my career, I struggled with this concept. I was supposed to be a supportive mentor, but I kept treating these meetings as progress updates. I would constantly interrupt my engineers to ask about specific bugs. I was going to change my approach, but my fear of losing control kept getting in the way. I had to learn the hard way.

I remember a recurring meeting with one of our senior developers, Matt. He was about to share some feedback about our broken deployment pipeline, but I immediately hijacked the conversation. I spent fifteen minutes explaining how I was to restructure the entire platform team. He just sat there with a lukewarm expression, completely shutting down.

By treating the meeting as a status update, I missed a crucial opportunity to pick his brain about team morale. Instead of letting him open up about his career trajectory, I put him on the spot about a minor release delay, losing my bird's-eye view of his growth. Our connection began to fizzle out, and I had to give him a heads-up that we needed a more hands-on reset.

Another time, during a skip-level meeting with Scott, a junior developer, I made the same classic mistake. Scott had brought a single talking point about pair programming, which was supposed to be the main focus. But I was so eager to share my hands-on coding philosophy that I completely brushed off his input and ran the clock down.

This brings me to my absolute worst one-on-one, which happened with Scott that very day in Manchester. I had promised myself that I was going to let him drive the conversation. I had even prepared a list of open-ended questions to help him air his unspoken frustrations about our sprint planning.

Unfortunately, my ego took over. I talked for exactly twenty-eight minutes out of our thirty-minute slot, explaining my bird's-eye view of the department's future. Scott only had two minutes to speak, which he used to politely tell me he was resigning. It was a massive wake-up call that changed my management style forever.

Read again and choose the right answer

What does Taylor say is the primary purpose of a one-on-one?

• To get a detailed status update on Jira tickets
• To let the report drive the agenda and share concerns
• To allow the manager to explain future restructures

Why did Taylor's connection with Matt begin to fizzle out?

• Because Matt was too busy with the database migration
• Because Taylor focused on status and minor delays instead of career aspirations
• Because Matt refused to work in Manchester

How did Scott react during his skip-level meeting when Taylor shared his coding philosophy?

• He actively participated and agreed with Taylor
• He brushed off Taylor's ideas and left early
• He was unable to focus on his own talking point

What was the twist at the end of Taylor's worst one-on-one with Scott?

• Scott used his remaining two minutes to resign
• Taylor managed to stay quiet for the entire thirty minutes
• Scott thanked Taylor for the bird's-eye view of the company

Sources: photo by cottonbro studio on Pexels