In this series I have written about our hiring process, but now I want to talk about what work with developers once they are at the company. Once developers, or indeed any staff member starts at your company, you have a duty to develop them over time. Buying Butler is no different. I have worked for many companies both large and small and seen some good examples of staff development, but also some terrible examples. Naturally I want Buying Butler to be a good example.
I run the development teams across both Buying Butler and RightIndem, so I am going to be talking about how I work with my developers specifically, but anything I say here is just as applicable to any type of skilled knowledge worker. Like most companies, we conduct 1 to 1’s with our staff. We use these as a way to give feedback but also offer some coaching if required and to see how developers are progressing with objectives. When giving feedback, I feel this should generally be positive in the 1 to 1. If there is anything bad that you need to bring to their attention then this should have happened prior to a 1 to 1. This meeting shouldn’t contain any bad surprises in my opinion.