The One-on-One Framework I Use with Tech Leads

With three programs and 50+ engineers, the most important meetings on my calendar are not stakeholder reviews or sprint demos. They are my weekly one-on-ones with tech leads.

These four conversations determine whether everything else runs smoothly or falls apart.

The Structure

Every one-on-one follows the same four-part structure. It takes 30 minutes.

First five minutes — their agenda. The tech lead brings whatever is on their mind. A team conflict, a technical concern, a process frustration. This is their time, and I do not redirect it. Whatever they want to talk about first is the most important thing.

Next ten minutes — blockers and risks. We review what is stuck, what might get stuck, and what needs my intervention. This is where I add the most value. A PM's job is to remove obstacles, and I cannot do that if I do not know where they are.

Next ten minutes — people and process. How is the team doing? Is anyone struggling? Is anyone underutilized? Are there process changes we should try? This is the strategic conversation that prevents problems before they become crises.

Last five minutes — decisions and actions. We explicitly state what was decided and who owns what. No ambiguity. I take notes during the meeting and share them within the hour.

Why This Works

The structure creates safety. Tech leads know they will have time for their concerns. It creates accountability because decisions get documented. And it creates a rhythm that makes the relationship feel reliable, not reactive.

The Anti-Pattern

The worst one-on-ones are status updates in disguise. If your tech lead is just reading you their Jira board, something is wrong. You should already know the status from your dashboards. One-on-ones are for the things that do not show up in tickets — team dynamics, morale, technical debt concerns, career growth.

Invest in these meetings. Everything else scales from them.