Feedback is given in a number of situations. You might be a student looking for help. Or an employee wanting to grow. In these cases feedback could come in a few forms:

– Comment on your work
– Clarification on a topic
– Criticism that gives constructive insight
– Confirmation that you’re doing the right thing
– Correction to show what you’re doing wrong

There are many more examples, but you get the point. Not all feedback is helpful or warranted, and it’s not always valuable for the receiver. Feedback is likely not helpful if it doesn’t answer a simple question: where can I go next?

The same can be said in product and software development. If your feedback processes don’t help you close the gap between what is understood and what is aimed for, then it’s likely not useful. The aim is to reduce the discrepancy between the current status of development and the overall goal.

ConsiderDo your current feedback mechanisms with users, customers and technologists help you know ‘where can I go next?’

Sign up to receive our newsletter and new posts

I'm the Chief Operating Officer for Emergn and Product Manager for VFQ®. Inbetween my day job running Emergn and working with our clients, I write content and develop courses for Value, Flow, Quality®. I’m passionate about learning, helping people change and own the way they work, and helping them develop their own passions.