One of the most critical components to feedback is timeliness.

You wouldn’t wait two months until after a project has been completed to say to a developer – “the problem is how you coded it, you should have done it this way and used this library, I saw that issue immediately” – that provides no value.

It might help them the next time they undertake a similar project, but for when it was needed, the boat has sailed, the opportunity was missed.

Feedback doesn’t need to fit into a cycle or a process, it needs to fit into the goal and the growth of the individual.

If you were doing something wrong or if there was a better way to do it that you didn’t know, you would want someone to tell you, you would beg to have someone tell you.

Do the same for your team, because they want it just as badly.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.


Write A Comment