A Manager’s Handbook to Effective and Useful One on Ones
I briefly touched upon this topic in the previous article, ‘Meetings that don’t suck.’ It is a subject particularly close to my heart because I have wrestled with it, danced around it, and dodged it for quite some time. It has also surfaced in some of my meetings with other managers, leading me to realize that everyone grapples with finding effective ways to conduct one-on-one sessions with their reports.
I’ve encountered a variety of challenges in my one-on-one meetings. Some engineers wanted to delve into every intricate detail of their projects during our half-hour catch-up. Others struggled to find topics for discussion, often offering only single-syllable responses. I found myself in the position of needing to guide the conversation or prompt more specific questions to fill the half-hour. Additionally, a few desired more frequent meetings, while others considered it an obligation.. For example:
Me: “How’s everything going?”
Engineer 1, taking out the laptop and walking me through the entire code he wrote in the past week.
Engineer 2: “Good.”
What was happening here? Well, what was prominently absent in these meetings was clear expectations. When people are unsure about the purpose of the meeting, they either fill the time with unnecessary details to make an impression or disengage and leave the direction up to the other person.
The key to a successful solution is embracing the fact that there’s no one-size-fits-all approach when dealing with people. I’ve explored various strategies to address this challenge, but the following three have consistently proven to be highly effective for me.
1. Create a Running Document:
Human memory is limited, and as a manager, you juggle various responsibilities. Consequently, you’re prone to forgetting small but crucial details that may resurface at a later time, and you might fail to recall important information necessary for sound decision-making. This highlights the significance of documenting your conversations. Your notes need not be overly comprehensive, but they should capture key decisions, enabling you to retrieve information swiftly. Think of it as…