unsolicited feedback

Your graph is garbage.

No productive conversation has started with words like these. However, in the past week, I’ve read them (directed at someone else’s data visualization) and had a similar comment posted to me about a blog article I published in 2012 (in which my words were referred to as “rubbish;” despite the similar trashy language, stated by a different critic). This is the dark side of the internet: where everyone has access to everything and feels they have free rein to say whatever they want. I think one of the things that irks me most in these scenarios is the clear imbalance. On the one hand, someone takes time and energy to create something and put it out into the world, perhaps with the hopes that someone will learn or be inspired, or simply to share something of which they are proud. Yet it takes very little effort to criticize.

This type of exchange is, unfortunately, all too common online. Anyone who shares their work regularly in a public setting, or follows others who do, has likely experienced or witnessed it. Such comments can send content creators in all sorts of unproductive directions: mentally (or actually!) drafting and redrafting killer comebacks, obsessing over the motivations of the commenter, or perhaps even questioning their own abilities.

While some fault-finders may criticize as a way to make themselves feel better, I try to avoid assuming malevolent intent. Instead, I imagine a scenario where the commenter is actually trying to help, but is simply going about things in a poorly-considered manner.

With that in mind, I thought I’d share some practical tips for providing unsolicited feedback. While I’m writing these from the perspective of giving unsolicited feedback online, these strategies could be applied equally well in a work setting to give input to others.

Assess: should you share your opinion? Just because a thought crosses your mind when you see something someone else shares, it does not mean you need to say it. Consider: do you have something of value to contribute? Are you interested in a productive exchange? How would you feel if someone said the words you are about to post to you—in particular if you didn’t ask for feedback? If you find yourself thinking of adding a reply or comment because you think others will like it, it may make you look good, or it might embarrass someone else, please refrain. 

Connect directly. Rather than commenting in public, consider sending a direct message. This can reinforce pure intent, because it makes it clear that you aren’t simply commenting to score internet points. This is not to say that all feedback should take place in private: there can be value in having conversations in a public setting for shared learning. But it’s best if both parties agree to that game.

Ask permission. Asking someone if they would like your input is a simple gesture that puts the power of choice in their hands. “I have some ideas for how you might improve your graph—would you like to hear them?” It starts the exchange off in a courteous manner, which makes it easier to continue in that way. 

Don’t assume—ask questions. The creator (of the graph, slide, data visualization, article, or whatever it is) invariably faced or imposed constraints to which you have no visibility. Additionally, people often place their own priorities, preferences, beliefs, and goals on other people’s work. For instance, when I’m visualizing data in a business setting, I tend to optimize for efficiency of information transfer when creating graphs: I keep things simple and take steps to make the main message clear. But this is not the only reason to visualize data, so it does not necessarily make sense for me to put this lens on someone else’s work. To deduce that, I need more information. Asking questions can help build context and having context means you can provide better input. Consider questions like, “Why are you visualizing this data?”, “Who is your audience?”, and “What are your goals?”

Practice the Socratic approach: ask more questions. In addition to understanding the situation, asking questions can also be a terrific way to offer feedback. For example, if I encounter a graph that could be described as Rainbow Brite’s nightmare, rather than lead with that, I might ask, “I’m curious: what led to your color choices in this visual?” Direct feedback can be reframed into a question to soften it. For example, “You should have used a bar chart here,” could be rephrased to “Did you consider using a bar chart for this data?”. 

Be respectful. While these seem like words that shouldn’t have to be said, it’s clear from the awful exchanges I see take place that a simple reminder to be nice is warranted. When you provide input, make it about the work, not about the person. One filter I sometimes find useful: don’t say anything online that you wouldn’t say to the person if they were sitting with you in your living room, or to a stranger you pass in a cafe. There is no good reason not to be nice to others. 


Share this the next time you see someone post something snarky about someone else’s work. Read it again on the occasion you’re tempted to do so. We each have a finite amount of time and energy and get to choose how we spend those things. Consider how you’d like to spend yours, and the impact that choice has on others. 

When you do decide to offer unsolicited feedback, please do so thoughtfully.


Related resources:
For more on feedback, have a listen to our very first episode of the SWD podcast, the art of feedback.
To practice giving input to someone who asked for it, check out the feedback section in SWD community.