Vact Effective One-on-One Meetings for Project Managers and Team Leads
One-on-one meetings are the most important meeting a manager or team lead has. They are the primary channel for building trust, identifying problems early, supporting individual growth, and aligning personal goals with team objectives. Yet one-on-ones are frequently skipped, rescheduled, or run as status updates — missing their purpose entirely. A good one-on-one is the team member’s meeting, not the manager’s, and it should focus on the person rather than the project.
Effective One-on-One Meetings for Project Managers and Team Leads
The Purpose of One-on-Ones
One-on-ones serve three functions:
Relationship building. Trust is the foundation of effective team leadership. Regular, private conversations build the relationship that makes everything else possible — honest feedback, early problem reporting, and difficult conversations.
Individual support. Each team member has unique challenges, goals, and concerns. One-on-ones provide the private space to discuss workload balance, career development, interpersonal dynamics, and personal circumstances that affect work.
Early warning. Problems that are invisible in team meetings often surface in one-on-ones. A team member who is frustrated, overwhelmed, or considering leaving will usually share this privately before it becomes a team-wide issue — but only if the relationship supports honest conversation.
Frequency and Duration
Weekly, 30 minutes. This is the recommended default. Weekly cadence ensures consistency. 30 minutes provides enough time for meaningful conversation without being a significant time commitment.
Do not cancel one-on-ones. The message sent by canceling a one-on-one is “you are less important than whatever else I scheduled.” If the regular time does not work, reschedule to the same week.
Structure
The 10-10-10 Format
- 10 minutes: Their agenda. The team member shares what is on their mind. Prompting questions: “What is on your mind this week?” “How are you feeling about the project?”
- 10 minutes: Your agenda. Share feedback, provide context on organizational changes, or discuss specific concerns.
- 10 minutes: Growth and development. Discuss career goals, learning opportunities, or upcoming challenges that support their development.
Opening Questions
| Category | Questions |
|---|---|
| Wellbeing | How are you doing? What is your energy level this week? |
| Work | What is going well? What is frustrating you? |
| Blockers | What is slowing you down? What do you need from me? |
| Team | How is the team dynamic? Any concerns about collaboration? |
| Growth | What skill do you want to develop? What kind of work energizes you? |
What One-on-Ones Are Not
Not Status Updates
If you spend the entire one-on-one reviewing task status, you are wasting the meeting. Task status belongs in daily standups, sprint reviews, and status reports. The one-on-one is for topics that cannot be discussed in group settings.
Not Performance Reviews
One-on-ones are ongoing conversations, not periodic evaluations. Regular feedback in one-on-ones makes formal performance reviews a summary of already-known information rather than a surprise.
Not Problem-Solving Sessions
When a team member raises a problem, resist the urge to solve it immediately. Ask questions: “What have you tried?” “What do you think the solution is?” “What support do you need?” Developing the team member’s problem-solving capability is more valuable than solving the problem yourself.
Giving Feedback in One-on-Ones
One-on-ones are the best venue for individual feedback because they are private, regular, and relationship-based. Use the SBI model:
- Situation: Describe the specific situation (“In yesterday’s sprint planning…”)
- Behavior: Describe the observable behavior (“…you challenged the Product Owner’s priority decision publicly…”)
- Impact: Describe the impact (“…which made her defensive and derailed the planning session for 20 minutes.”)
Follow with a forward-looking question: “How could you raise priority concerns in a way that is less confrontational?”
Common One-on-One Mistakes
Doing all the talking. The team member should talk at least 50% of the time, ideally 70%. If you are doing most of the talking, you are lecturing, not listening.
Only discussing problems. If one-on-ones only happen when something is wrong, team members associate them with negative feedback. Discuss wins, growth, and positive contributions regularly.
Canceling frequently. Every cancellation erodes trust. Consistency signals commitment.
Not taking notes. Without notes, action items are forgotten and conversations repeat. Maintain a shared document where both parties can add agenda items and track action items.
Avoiding difficult topics. One-on-ones are where difficult conversations should happen — performance issues, behavioral feedback, and organizational concerns. Avoiding these topics lets problems fester.
One-on-Ones for Scrum Masters and PMs
Scrum Masters and project managers who do not have direct reports still benefit from regular one-on-ones with team members. These conversations focus on process improvement, blockers, and team dynamics rather than performance management. They complement retrospectives by providing a private channel for individual concerns that team members may not want to raise in a group setting.
Schedule one-on-ones with each team member at least biweekly. For new team members in their onboarding period, weekly is appropriate.