Menu

A better way to approach Net Promoter

Back in my eBay days, when Net Promoter was just becoming a huge deal, there came a time when we were asked to include the measurement in our user research. Even then I was extremely uncomfortable with the simplistic nature of the measure, but I just didn’t have the experience to speak up about it. It seems that NPS is finally getting the wind taken out of its sails. The latest takedown I read is Matt LeMay’s excellent On Net Promoter and Data Golems:

This very ubiquity is a huge part of what makes Net Promoter so attractive. It’s a system with an official-sounding name that consistently produces a measurable quantitative output. The score it produces can be easily benchmarked against that of any other company. And this is why, no matter how many times it is critiqued and debunked, Net Promoter only seems to grow in power and pervasiveness. The primary value of Net Promoter is not how effectively it predicts customer loyalty, but rather how effectively it covers your ass.

The main problem with the NPS question—”How likely are you to recommend [product] to a friend or colleague”—is that it’s a data model that doesn’t fit the social model of recommending products.

But by oversimplifying the multifaceted and highly variable human context around recommendation, Net Promoter falls into one of the biggest pitfalls of the “data-driven” age: it puts forth a data model that does not accurately reflect the underlying social model. When’s the last time you thought to yourself “I am likely to recommend this product to my friends or colleagues” as opposed to something like, “I can’t wait to tell my friend Tricia about this new slow cooker because I know that she doesn’t like to cook things on the stove”?

Luckily, Matt provides some really good ways to improve the use of NPS. Is this is something you deal with in your company I highly recommend his article.

Pretending at closeness

Leigh Alexander wrote a very interesting essay on how Facebook is getting a little… “intimate” with its users lately. She extrapolates that to a growing trend in The New Intimacy Economy:

Pretending at closeness is really the only way forward for anyone who wants to make money on the internet. As such, watch as organizations pretend, with increasing intensity, that they are individuals. Start counting how many times platforms, services and websites entreat you in human voices, with awkward humor, for money. Watch as the things we expect to be invisible, utilitarian, start oozing emojis and winky-smileys. Even Silicon Valley, global epicenter of whitewashed empathy voids and 1-percenter sci-fi wank fantasies, is going to pretend it cares about you.

AAPL the stock vs. Apple the company

Neil Cybart has a very interesting analysis of AAPL, the stock, and Apple, the company. From The Two Apples:

While AAPL investors look at changing revenue sources and Apple entering new industries as risk factors, for Apple such characteristics are normal business and according to plan. It is this divide that will likely continue indefinitely, suggesting it is unwise to expect AAPL to one day begin to follow Apple. Just as a declining AAPL stock price is no indication of a struggling Apple, there will likely come a time when AAPL outperforms peers even though Apple, the company, may be struggling.

The whole article is worth reading if you’re interested in the disconnect between a company that seems to be doing really well, and a stock price that doesn’t reflect that.

Apple Revenue

Quote: Patrick Rothfuss on the importance of travel

If you want to know the truth of who you are, walk until not a person knows your name. Travel is the great leveler, the great teacher, bitter as medicine, crueler than mirror-glass. A long stretch of road will teach you more about yourself than a hundred years of quiet introspection.

—Patrick Rothfuss, The Wise Man’s Fear.

Entity-relationship modeling as a starting point for product design

It’s been roughly 15 years since I made an entity–relationship model, so it is with great surprise that I sat in a meeting the other day and thought to myself “This project needs an ER model before we can do anything else.” I almost asked out loud, “WHO SAID THAT!?” But once I got over the initial shock I realized that my subconscious isn’t completely full of crap (this time).

But let’s back up. I’m working on a project to combine a variety of different back-end services into a single product. As we were talking about it and the discussion shifted to design, I realized that before we could create user journeys and get started on the interaction design we first needed to understand the relationships between the different entities in those services. I worried that without that model, we’d get ourselves tangled up really quickly.

So I brushed up on my theory1 and got to it. First, the obligatory definition:

[An] entity–relationship model (ER model) is a data model for describing the data or information aspects of a business domain or its process requirements, in an abstract way that lends itself to ultimately being implemented in a database such as a relational database. The main components of ER models are entities (things) and the relationships that can exist among them.

This is a tool that’s primarily used as the first step in relational database design. But I found it really useful for us to define the constraints within which we could create user flows. Let me explain with an example. Here’s a simplified version of the ER model we came up with for this project (using Crow’s foot notation):

Entity-relationship model

Each color represents a different back-end service. Here’s a subset of what the diagram tells us:

  • A team can have multiple tasks, but each task can only be assigned to one team.
  • A task can have multiple files associated with it, but each file can belong to only one task (or team).
  • A person can be part of multiple teams, and a team is made of multiple people.
  • There is a 1:1 relationship between teams, tasks, files, and the conversations about those entities.
  • Outside of those relationships, a person can be part of multiple conversations, and a conversation can consist of multiple people.

If all this sounds a little bit boring, I hear you, but here’s the power of this diagram: it ensures that whatever UI we come up with serves the underlying entity relationships, and not the other way around. This is huge. For example, if we started with the UI we might say that users can attach files to a task or project within the product’s main interface. But since a 1:1 relationship exists between Conversation and File, it means we can also attach a file to a task by dropping it into the Conversation view of that task. The relationships help us to come up with the most useful and robust UI.

What essentially happens if you start UI design with an ER model is that you create the boundaries of what’s “allowed” in the UI. It pushes you to think up useful ideas without the danger of coming up with something that wouldn’t work in the final implementation.

I don’t think ER models should be the starting point of every project. But in certain specific cases where many disparate products or services need to come together it’s proved to be really useful.

And now, on to journey mapping…


  1. Ok fine, I read the Wikipedia article. 

That Dragon, Cancer: a game that explores faith, hope, and love

Tomorrow, a game called That Dragon, Cancer becomes available to play. The premise is heartbreaking:

An immersive narrative videogame that retells Joel Green’s 4-year fight against cancer through about two hours of poetic, imaginative gameplay that explores faith, hope and love.

Earlier this month Wired did an incredible profile on the creator of the game: Joel’s dad, Ryan Green. From Jason Tanz’s A Father, a Dying Son, and the Quest to Make the Most Profound Videogame Ever:

Over time, That Dragon, Cancer became Green’s primary method of dealing with Joel’s illness, as well as a way for him to preserve a connection to his son, whom he struggled to get to know. In real life, Joel couldn’t talk about his feelings, leaving Green to guess at his thoughts and emotions. Joel’s reaction to radiation therapy was particularly puzzling. Children usually hated being placed on the gurney inside the giant linear accelerator, resisted the anesthetic, fought and clawed at their parents and doctors every time they entered the room. But Joel loved it. He grew impatient in the waiting room, and his face lit up when the doctors came to get him, more excited than his parents had ever seen him. Green couldn’t know just why Joel was so enthusiastic about undergoing the anesthesia, but he wrote a scene imagining the adventures Joel might be experiencing in his mind—riding animals made of stars, giggling and tearing across the cosmos.

It is an incredible story—equal parts sad and inspiring. This game scares me—I’m not sure I have the strength to play it. Here’s the trailer…

The myth (and danger) of the ‘perfect response’

Adam Sternbergh breaks down The Internet Fantasy of the ‘Perfect Response’, that mythical one-liner that puts someone in their place, makes them realize the error of their ways, and changes their minds in an instant:

But the Perfect Response you cheer for and re-post frantically also tends to be one that (a) confirms whatever you already believe and (b) sticks it to someone you already despise. The Perfect Response is, in essence, not a radical new perspective, but simply a person saying a thing you agree with to a person you disagree with. It’s a kind of linguistic record-scratch, a perfectly crafted gotcha that ostensibly stops trolls in their troll-tracks and forces them to deeply reconsider the sad wreckage of their wasted lives. Which means the Perfect Response is also largely a figment of the internet’s imagination.

The problem is that the idea of a ‘Perfect Response’ makes us think that changing hearts and minds isn’t hard work. And that’s simply not true:

The Perfect Response, while apparently so bountiful in theory, is actually appealing precisely because, in practice, it’s so rare as to be almost nonexistent. It’s just a fantasy we yearn for, and to which we happily subscribe, because the hurly burly of actual internet interaction can be so imperfect, and frustrating, and wearying, and hard. The give-and-take of real debate can be all of those things as well, but it also has the attractive by-product of potentially leading to change, something no Perfect Response has ever done. Which is how we ended up with the phenomenon of the Perfect Response in the first place—it’s an imperfect response to just how difficult real communication can be.

Norman, the boring anti-hero

Halfway through his day at work, Norman yawned.

“Oh no, don’t start doing that!” a coworker joked.

Norman chuckled. “Yeah, I know.”

“Rough night?”

“You could say that,” Norman lied.

Norman didn’t have a rough night. Norman had gotten eight hours of restful sleep. Norman was just always a little tired.

That’s a story from The Life of Norman, a reddit thread where thousands of people tell boring stories about the fictional Norman’s boring life. And it’s fascinating. From Michell Woo’s The Life of Norman (and the Rise of Boring):

Now, all day, every day, redditors construct the intricacies of the life of this unremarkable man, mostly in 500 words or less. Reading through the titles feels like watching paint dry. Norman goes into his office building. Norman makes a steak for dinner. Norman receives a text message. Norman does the laundry. Norman meets a friend and they talk about how they both used to enjoy opening Microsoft Paint, drawing some squiggles, and coloring in the spaces. Life of Norman is possibly the most action-deficient fanfiction series in existence—and that’s what makes it so compelling to its creators and audience.

Why are people drawn to this? One possible reason:

After writing 40 stories about Norman and following his journey so closely, [Cameron Crane, a moderator of the Life of Norman subreddit] believes he’s drawn to the character partly because he’s an example of what he doesn’t want for his life. Redditors will sometimes tell him that they’re grateful for Norman, sharing with him that they’ve been depressed and stuck in a rut and that Norman serves as a wake-up call.

That’s true for him, too. “At the heart of it, I think I’m just afraid, afraid of becoming Norman,” Crane says. “Norman isn’t a role model. It’s okay to be like Norman, but you shouldn’t accept it. He’s comfortable, and the only way to get ahead in life is to make yourself uncomfortable.”

More

  1. 1
  2. ...
  3. 69
  4. 70
  5. 71
  6. 72
  7. 73
  8. ...
  9. 201