Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Home ›› Agile and Iterative Process ›› Don’t Make it Hard for Users to Provide Feedback #wtfUX

Don’t Make it Hard for Users to Provide Feedback #wtfUX

by Daniel Brown
2 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

User feedback is the lifeblood of experience design. Make it easy and rewarding for your customers to share their feelings and ideas about your product or service.

While most users provide feedback “for the greater good,” it’s still wise to thank them and encourage them to continue doing so. At the very least, avoid doing things that discourage them from submitting feedback.

Bug reports, feature requests, and general feedback help to populate a company’s “to-do list”—a carefully-curated and painstakingly-prioritized roadmap that defines the features of the product. Each of those features has the potential to further empower existing users and attract new ones.

Within the last few months, I’ve provided feedback to a variety of companies, but two experiences stand out.

The first was with Evernote. I had an idea about how to improve Skitch that would save me from having to jump into Photoshop to get the effect I wanted. A day or two later, they sent me the following message:

Evernote feedback

I want to point out a key sentence in that message: “I will be happy to submit this to our developers for you.”

Let’s contrast that with a response from Gliffy. I noted that their zoom function actually requires two clicks just to zoom in and out rather than just one. This was their response:

Gliffy feedback

While Gliffy also thanked me for my feedback and went into inspiring detail about how valuable such feedback is, they rewarded that effort with “Could you now take that feedback, go to a different section of our web site, click on a button, and then re-enter it in a format that is more helpful to us.”

Nnnnnnnope. I already took time out of my day to clearly outline the issue I was having and even proposed a solution for you. My work as a user should be done. Not only did I not re-enter that initial feedback, I’m also not terribly motivated to send them any feedback in the future. What if I don’t remember the method that’s most convenient for them?

The point here is that user feedback can be incredibly valuable; especially when that feedback is coming from paying users who are utilizing your software in a “live” environment. You can get all the feedback in the world from people unable (or unwilling) to pay for your software, but they don’t help you make payroll. When someone takes the time to send you feedback, treat it—and its author—graciously.

 

Keep these coming. Send them to us via Twitter or Facebook using the hastag #wtfUX or email them to: [email protected] with “#wtfUX” in the subject line. Include as much context as you can, so we get a full understanding of what the f%*k went wrong. Image of conversation bubbles courtesy Shutterstock.

post authorDaniel Brown

Daniel Brown, Daniel has spent the past 20 years in software companies both large and small. From web design and development for a “boutique” web design firm to Evangelism for Adobe Systems, to helping budding startup companies get a foothold in the market, he’s worn a variety of “hats". Daniel has spoken at a variety of events worldwide including the Sundance Film Festival, Anderson Ranch Arts Center, Santa Fe Digital Workshops, and the Pacific Imaging Center in Hawaii on the topics of web design, digital imaging, photography, and user experience. Daniel currently serves as the head of the interface and user experience department at a small medical software company in Providence, Rhode Island.

Tweet
Share
Post
Share
Email
Print

Related Articles

What do Architecture, Computer Science, Agile, and Design Systems have in common?

Article by Kevin Muldoon
A Pattern Language
  • The article explores Christopher Alexander’s impact on diverse fields, from architecture to software development, introducing the concept of design patterns and their influence on methodologies like Agile and the evolution of Design Systems.
Share:A Pattern Language
7 min read

As consumers’ privacy concerns continue to grow, so should our attention to addressing privacy issues as user experience designers.

Article by Robert Stribley
Designing for Privacy in an Increasingly Public World
  • The article delves into the rising importance of addressing privacy concerns in user experience design, offering insights and best practices for designers and emphasizing the role of client cooperation in safeguarding user privacy.
Share:Designing for Privacy in an Increasingly Public World
9 min read

Knowing your audience, business values, voice tonality, voice refinement, and team trust.

Article by Eva Schicker
5 UX Development Phases to Create Your Brand’s Voice
  • The article offers a concise guide to crafting a brand’s voice in five key UX development phases.
  • The author emphasizes practical strategies and tools for creating a unified brand identity that connects with customers and builds trust.

Share:5 UX Development Phases to Create Your Brand’s Voice
5 min read

Did you know UX Magazine hosts the most popular podcast about conversational AI?

Listen to Invisible Machines

This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and