Execution Speed

Feedback? Just Ignore It

Matthias Kolbusa7 min reading time
Image source: iStock sesame

After every session that deviates slightly from the norm – whether the kick-off for a new project, the presentation of newly developed processes or the annual offsite with colleagues – it has become standard practice to ask for feedback. “I would appreciate it if everyone could briefly say how they found today’s session” is one of the worst such requests. In terms of feedback phenomena, it ranks second. Immediately followed by: “To conclude, I would ask everyone for brief feedback on the content we have presented and developed.”

Just Ignore It

Excuse me? How are these supposed to be feedback mistakes? That is exactly how you do it. After all, you want to know how people found it or where they stand on the content. But is that really the case? Let us look at these and other phenomena – particularly the one that ranks first – and peek behind the curtains.

First, as a frame around the topic of feedback, an insight that the French philosopher François de La Rochefoucauld formulated over 300 years ago:

“Pride has a greater share than benevolence in the reproaches we make to others for their faults, and we rebuke them not so much to improve them as to show them that we ourselves are free of such faults.”

Unsolicited Feedback – Always Decline

La Rochefoucauld’s statement applies 100 per cent to unsolicited feedback. When a participant approaches me after a presentation and asks: “Mr Kolbusa, may I give you feedback on your talk?”, my answer is a simple and polite “No, thank you”. Then I briefly look into the eyes of my visibly irritated counterpart and go on my way. Does this behaviour seem rude to you? On the surface it may appear so, but in reality it is the exact opposite.

In every case where I have engaged with it, the motive of the feedback giver was either malicious or they wanted to put themselves in the spotlight with their know-it-all attitude. Their motive was never to genuinely help me. Whether as a young project manager whose team members offered their feedback, or later board members during a change process in which they were part of the transformation: their “feedback” was always more in their own interest than in mine or the project’s.

But there is more: the effect of unsolicited feedback was, in nearly every case, that I felt worse afterwards than before, without being able to draw the slightest insight or benefit from it. Therefore: unsolicited feedback must simply be ignored. The only feedback that counts and that is helpful comes from people we value for their experience and the certain knowledge that they genuinely want to help us. Unfortunately, such people are rare, but all the more valuable for it.

Process Feedback – The “How” Is Irrelevant

I fail to see the point of asking people “how” they found today’s event. Everyone present is supposed to speak in turn, even though the general tendency is clearly recognisable after the third participant and you know for certain that nothing new will follow. Whatever comments (feedback) still follow are usually perceived as self-congratulation by the person who requested the feedback. And if there is something that genuinely could have been done differently or better at the kick-off, the offsite or another event, then please raise it when there is still time to correct or change course. Not only at the end.

Far more decisive, however, is this point: were the results you aimed for with the meeting achieved or not? If yes, all is well. If not, further work is needed. Whether the participants liked it or felt comfortable is simply irrelevant. It is not about being liked. It is about being respected and producing results. What is the point of asking for feedback on the “how”? You and I, as the responsible managers in the workshop or meeting, are the ones who know what needs to be achieved and how to proceed, who have a clear idea of what is done in which order.

I have stopped asking people “how” they found it after seminars, kick-offs or meetings. It is simply irrelevant. The only thing that counts is whether we identified the top five issues and how we deal with them – or whatever the intended result was. Even with soft topics: did the critical aspects come to the table and get resolved, or were they not? Whether the team or participants felt comfortable and liked the process is beside the point.

Please be clear about this. And if things did not go well and the results were not achieved, we can see that for ourselves – the group does not need to rub it in. So: no feedback on the “how”. Especially not from the very group you have been working with. The only relevant how-feedback is that which we seek from people we respect because they have successfully mastered exactly such situations many times before. Either we ask for their views beforehand to prepare and leverage others’ experience, or afterwards for targeted reflection.

The only relevant how-feedback is that which we seek from people we respect because they have successfully mastered exactly such situations many times before. Either we ask for their views beforehand to prepare and leverage others’ experience, or afterwards for targeted reflection.

Feedback
Image source: AdobeStock Nuthawut

Content Feedback – Addicted to Harmony?

Of course there are situations in which we must ensure that a group of people share the same view or a common conviction on certain matters. For example, when we need to agree on new ways of working with colleagues. It is a question of intelligently designing the development or decision-making process. However, soliciting feedback from participants in a larger group – or even individuals – on the content that has been developed is not only useless but usually destructive in terms of the further process.

If, with considerable effort, it has been clearly worked out for everyone in the room what changes for their area and how the new structure affects them in detail, then the intended results have been achieved. Why should there still be extensive feedback? To be told that someone thinks the new structure is rubbish and they would have had much better ideas?

Some managers not only ask for this useless feedback but, driven by pure addiction to harmony, actually engage with it. A good atmosphere is more important to them than the content, or at least equally important. They are completely wrong, because it does not matter whether we are liked or whether everyone approves of what now needs to be done. It is simply our duty to do the right thing – full stop. The feedback from process participants – whether employees, project members or colleagues who naturally have an opinion on what should be done and how – can be blissfully ignored. Because nothing is easier than philosophising about other people’s lives.

Only Criticism Is Relevant

Besides seeking targeted feedback from genuine experts who have our best interests at heart, criticism is what truly matters. It was only about 100 years ago that this word acquired negative connotations. In the days of Kant and company, criticism meant constructive engagement with a subject. For instance, Kant’s major work – The Critique of Pure Reason – is nothing other than an impartial, intensive engagement with human reason.

True high-performance teams are distinguished by proactively criticising one another in the interest of the cause. We do this far too little. And not infrequently we are too cowardly for it. Yet people are always happy to criticise out of malice. This drama needs to be reversed:

Constructive criticism always, destructive criticism never.

Yours, Matthias Kolbusa