One to Ones – Another Feedback Loop

http://www.flickr.com/photos/jm999uk/
http://www.flickr.com/photos/jm999uk/

Over the last couple of weeks I have been committing one of the worst sins as a manager. Not keeping up with my one to ones. This makes me feel really bad. Although I offer an “open door” policy, or in my specific case a no door policy (I don’t have an office) and I always try to encourage my directs to approach me whenever they have a problem or need advice, I still feel I have let them down by not having the metronomic opportunity to have my undivided attention and talk.

It still surprises me how few people have experiences of regular 1-1′s so I thought I would share my thoughts on my experiences.

What are One to Ones?

One to ones (1-1) are a regular and frequent meeting to give and receive feedback to your direct reports; those people that you manage. In the same way that we approach releases we approach one to ones, early and often, tightening one of the many feedback loops in Agile teams. It’s a time to allow direct feedback and build relationships with your staff. Giving feedback isn’t just about negative feedback nor telling someone how badly they are doing, it’s a time to offer encouragement and coaching. There any many techniques on providing feedback such as reflective questions or non threatening language but I wont go into that here.

The Anti-pattern

Annual reviews are a common practice in the business environment but the frequency extends the feedback loop between yourself and your directs to months. This allows little time for course correction until its too late and the behaviors that either you, your directs, or worse both, reach a point of no return and its time for personal improvement programs or other last resort corrective techniques that too often come as a surprise. How many times have you sat down with your directs to provide feedback at an annual review and you receive a look of shock and horror, as they were unaware of the impacts of their behavior or the fact that they were even doing it?

The cost of not doing them?

  • Your directs don’t know where they’re going wrong or what they’re doing well.
  • Morale depletes due to lack of encouragement or effecting other teams members with the unchanged bad behaviors.
  • As a manager you don’t get to find out what’s really happening on the ground and how people feel about it.
  • You don’t build up solid relationships with your directs.
  • You don’t allow yourself the opportunity to discover those gems of information about your directs that can help you understand where they are coming from and empathize.
  • You don’t allow a constant and open channel for communication.

What do they look like?

I generally make the 1-1 sessions 30 mins long, but this will depend on your availability and how many directs you have reporting to you. The session is split into 3; 19 mins for their feedback, 10 mins for my feedback and then 10 mins for any other business. My 1-1′s very rarely stick to this schedule but that’s OK. The important part is that the first part of the meeting is focused on what they want to say, reinforcing the fact that this meeting is for them and not a status update and that all parties have an allotted time to provide feedback.

Schedules can be tricky and the frequency is a balance. Too often and they can be time consuming for your direct with little to discuss at each. Too infrequent and you loose the opportunity for course correction and you slip too close to the anti-pattern.

I hope to share more of the specific challenges that I have faced in 1-1′s in the future, but hopefully, if your not doing them yet, this is enough to get you started.

There’s some useful pod-casts on 1-1′s and feedback in general from the people at Manager Tools. If you can get past the jovial conversational format there’s some good content.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>