The following is a short extract from our book, Researching UX: Analytics, written by Luke Hay. It’s the ultimate guide to using analytics for improved user experience. SitePoint Premium members get access with their membership, or you can buy a copy in stores worldwide.
To understand why your users behave the way they do, you first need to get to know them. You may make assumptions about who those users are, but you should be constantly challenging those assumptions, or at least be backing them up with facts...
https://www.sitepoint.com/getting-to-know-your-users-with-analytics/
Beware of the HiPPO in the room. When a HiPPO (highest paid person’s opinion) is in play, your organization is most likely not relying on data to inform decision-making. In fact, I believe the HiPPO effect is one of the biggest barriers to more evidence-based and data-driven decision-making. With the quantity and quality of data available today, it is just poor business for organizations to ignore data in favor of making decisions solely based on what the HiPPO wants done...
https://www.forbes.com/sites/bernardmarr/2017/10/26/data-driven-decision-making-beware-of-the-hippo-effect/#1131f38280f9/
To be subjective, or to be objective, that is the question, and the best product managers already know the correct answer is “both.” As product managers, we constantly face situations where the unknowns outnumber the knowns that we can rely on. It’s our job to drive out that uncertainty and ensure that both people and efforts align toward a common objective. Sometimes these discussions flow smoothly, as the goalposts that we set can be quickly and easily agreed upon – things like providing a quality user experience, solving valuable problems for our customers and our market, and introducing competitively differentiating capabilities are hardly controversial.
What does become controversial, however, is how we go about those things as a team, what exactly we should do, and who we should be building those products for. And when those discussions come up, it’s inevitable that everyone at the table will have different ideas about what those things are – and, unfortunately, the vast majority of those ideas will not be based on hard data. Hence why we, as Product Managers, need to make it our business to ensure that we’re bringing data to the table as we represent and advocate for our customers and our market in those conversations; to do so, we must provide stakeholders with the right mix of qualitative insight and quantitative data that will not only help win them over to our preferred course of action, but also minimize the risk of later changes of course.
https://community.uservoice.com/blog/qualitative-and-quantitative-product-feedback/
One of the most popular passwords in 2016 was “qwertyuiop”—the string of horizontal letters from the top line of a keyboard. Even though most password meters suggest that it's weak, none offers advice on how to strengthen it. Researchers from Carnegie Mellon University and the University of Chicago have unveiled technology that offers real-time feedback and advice to help people create better passwords. To evaluate its performance, the team conducted an online study in which they asked more than 4,500 people to use it to create a password.
“Instead of just having a meter say, ‘Your password is bad,’ we thought it would be useful for the meter to say, ‘Here’s why it’s bad, and here’s how you could do better,’” said study co-author Nicolas Christin, professor in engineering and public policy at Carnegie Mellon University.
https://news.uchicago.edu/article/2017/05/09/research-utilizes-data-driven-feedback-help-users-strengthen-passwords/
Most entrepreneurs recognize the importance of great customer service and the importance of rewarding employees for great performance. Put these two things together, and it makes sense for companies to tie the size of their employees’ paychecks to the ratings they receive on customer satisfaction surveys.
More than 90 percent of US companies have shifted a greater percentage of their payroll to variable pay to increase engagement and retain talent, according to Aon Hewitt. Pay-for-performance plans are becoming common for customer-facing roles because frontline employees can directly shape the customer experience, and how people perceive the brand. A full 43 percent of companies base some portion of frontline pay on customer feedback ratings, according to a 2017 Accenture-Medallia survey.
https://www.forbes.com/sites/groupthink/2017/08/24/how-to-pay-employees-based-on-customer-feedback/#cea0cd520b3a/
YOU'VE BEEN THERE: browsing on a slightly backwater website, crossing your fingers as you click what looks like a video's play button. Instead of the TV show you had queued up, a million pop-ups spew out. The page you were on morphs into a Caribbean timeshare ad. It's the sort of misdirection that Google aptly calls an "unwanted behavior." And on Wednesday, the company's Chrome browser team announced a series of fixes that attempt to block these sketchy shenanigans.
Chrome already has a pop-up blocker, and a tool to control autoplaying videos. But the new features will take these user controls a step further. Beginning in Chrome 64, which is currently in developer preview, the browser will block third-party media components (HTML modules known as "iframes" that are often used to display things like ads) from triggering redirects unless you directly click on them.
https://www.wired.com/story/chrome-stop-sketchy-sites-from-redirects/
The challenge is giving negative performance feedback when the Recipient gets defensive. But what about the opposite problem, where you have a person who seems totally receptive to the feedback but then doesn’t act upon it? One manager recently admitted to me that her team readily consents to changes or suggestions this manager makes, but then nothing actually happens.
How do you deal with a feedback Recipient who agrees to change but doesn’t follow-through? Here are five questions to help ensure you’re giving feedback the produces results, not empty promises:
https://www.forbes.com/sites/carolinecenizalevine/2017/10/22/when-you-give-feedback-and-nothing-changes-how-to-give-negative-performance-feedback-part-2/#35fb43336ed2/
In the face of a flood of "fake news," sensationalism, and mass marketing, Facebook has announced it is testing a new, more restricted and curated version of its News Feed.
Based on user feedback, Facebook will determine and prioritize the trustworthiness of news outlets. This goes beyond the social network's previous decision last week to promote "meaningful posts" by filtering out posts and video content from brand posts and boosting those that friends and family share.
https://www.newsmax.com/newsfront/facebook-news-trustworthiness-user-feedback/2018/01/23/id/838892/
In a previous article, we introduced three different ways in which you can collect mobile feedback (in-app): Webviews, APIs and SDKs. We explained that each of these methods have their own strengths and weaknesses. From implementation requirements to technical know-how and from internet limitations to performance (once implemented), we just about covered it all. However, now we want to take an even closer look at one method in particular, which happens to be very much on the rise especially in the area of Analytics: mobile SDKs.
https://mopinion.com/mobile-app-feedback-surveys-sdk/
Bookmarks on this page are managed by an admin user. 
