Insights

July 9, 2021

My 1 on 1 Feedback Methodology | Part 2

This is the second part of my personal feedback methodology, it's flexible by nature so always feel free to adjust as it fits your purpose.

This is the second part of a 2 part series of blogs, to read Part 1 click here.

As a reminder, in this article we’ll be reviewing the last 5 items of an interview I like to do regularly with my team. It can apply to anyone you supervise and work regularly with. These questions let them know that you see them not just as a person who brings something to the team and project, but also as someone with their own goals and aspirations. It is meant to be an informal chat and I’ve found that the personal nature of the conversation helps strengthen bonds and trust.

So here are the final five items with an in depth explanation for each, as well as extra details on some subpoints.

feedback methodology

6. Tips to improve my way of work:

  • Things I should start doing
  • Things I should do more
  • Things I should do less
  • Things that you’ve seen work for other teams or people in my role.

This part is focused on you, so keep an open mind and take notes. Again, this is not meant to be an official evaluation, and it promotes trust having your colleague see you writing down things they perceive as faults. This is an opportunity for you to grow, and if you think some of the faults are really qualities, the fact they were mentioned means that at the very least there is an issue of perception that you need to work on.

The last point is especially important for people who are just joining the team. When someone enters a new team, lots of people try to adapt completely to the existing dynamics and don’t question why things are done that way. But coming in fresh from another environment means there’s lots of ideas and opportunities they could bring from there, and this is the perfect time to do so.

7. What do you think of the team?

  • How do you see the team in general?
  • Have you worked with any team members before? Any comments about any specific team members? 
  • Anything you think we should be keeping an eye out for?

Here you give them a chance to share things they’ve seen related to the team in general. Maybe it’s the best team they’ve been in. Maybe they see a certain dynamic brewing in the team that we should get ahead of. Maybe they’ve worked with other members before and know their quirks. This question is best left in an open-ended way in case they want to share anything.

feedback methodology

8. What do you like about the company (outside of the team)?

  • Stuff you like about the installations
  • Things you like about the culture
  • Any kudos you’d like me to pass on?

This one is for them to talk about the company. It’s mostly to give you an idea of how comfortable they are with the structure, infrastructure, offices, etc. And to know what the people appreciate about the organization.

9. What could be improved about the company (outside of the team)?

  • What could be improved
  • Pain points
  • Any ideas you may have

Here you should make it clear that you’ll only share anything they give you permission to share (and that you’d do it anonymously). They could have concerns that they don’t really want others to know, but with just them sharing with you, you might be able to do something.

10. Anything else you’d like to share?

This is just the catch-all for anything else they might want to talk about.

feedback methodology

This methodology is flexible by nature so you are always free to modify the questions and add/remove some as you see fit. Perhaps you want to talk about the expectations you have for them when they join the team. Or there could be certain responsibilities you or them handle that deserve focusing on. Just remember that this isn’t really an evaluation, but rather a meeting to share what you both have in mind and how you can help each other.

I hope you can apply this to the people you work with and I'm more than happy to continue sharing more useful stuff in the future!

Interested in tech leadership? Learn more about team-bases approach in software development here.

Case Study from Arkusnexus
Manuel Márquez
Manuel studied computer engineering and worked as a programmer before making the jump into administration. He is a Product Owner for ArkusNexus Monterrey.
mmarquez@arkusnexus.com
RSS feed
Subscribe to our feed
Back to More ContentMore From this Author
HomeServicesAboutBlogNearshore Software DevelopmentContact
Privacy Policy
San Diego:
3065 Beyer Blvd B-2 San Diego, California 92154 +1-619-900-1164

Los Angeles:
530 Technology Drive Suite 100 & 200 Irvine, California CA 92618