Menu

The convergence of Product Management and User Experience Design

Melissa Perri in Changing the Conversation about Product Management vs. UX:

Product Management with no User Experience Design creates functional products that don’t make users excited. User Experience Design with no Product Management produces delightful products that don’t become businesses.

I have a few quibbles with this article (including the idea that the role of UX is to make users excited…), but I like this quote because it ties in with a common theme I write about: the importance of combining both user needs with business goals to create successful products.

When being alone on our smartphones, together, is okay

Emma Brockes wrote an essay for The Guardian called In praise of being alone on our smartphones, together:

The act of being with someone—or better yet, a group of people—and on one’s phone is just the modern iteration of a key pleasure of family life: to be among those whom one is sufficiently comfortable with to drift in and out of communication. Like doing homework at the kitchen table, it is the state of doing your own thing while others do theirs around you. The point is, whatever you are doing on your phone, it would be less pleasurable were you to be doing it alone in your room.

Screen addiction alters this, and there are levels of disengagement that can turn a sentient being into a piece of furniture, but the parameters of acceptable phone use should surely widen at this point to permit some middle way between being on one’s phone and considered rude, or turning the device off altogether.

The title of the essay is a clever reference to Sherry Turkle’s book Alone Together: Why We Expect More from Technology and Less from Each Other. It’s a book I enjoyed a lot, despite it being relentlessly full of depressing paragraphs like this:

Now demarcations blur as technology accompanies us everywhere, all the time. We are too quick to celebrate the continual presence of a technology that knows no respect for traditional and helpful lines in the sand.

[A] stream of messages makes it impossible to find moments of solitude, time when other people are showing us neither dependency nor affection. In solitude we don’t reject the world but have the space to think our own thoughts. But if your phone is always with you, seeking solitude can look suspiciously like hiding.

I recommend danah boyd’s It’s Complicated: The Social Lives of Networked Teens as a positive palate cleanser afterwards.

Anyway, back to Emma’s article. She also references Susan Dominus’s Motherhood, Screened Off, an article that was in heavy rotation towards the end of last year. Susan makes the point that smartphones result in a lack of transparency, since people (i.e. our kids…) don’t know what we’re up to when we’re on them:

It is that loss of transparency, more than anything, that makes me nostalgic for the pre-iPhone life. When my mother was curious about the weather, I saw her pick up the front page of the newspaper and scan for the information. The same, of course, could be said of how she apprised herself of the news. […] All was overt: There was much shared experience and little uncertainty. Now, by contrast, among our closest friends and family members, we operate furtively without even trying to, for no reason other than that we are using a nearly omnipresent, highly convenient tool, the specific use of which is almost never apparent.

And that’s where the answer to all of this comes back to “it’s complicated.” Yes, sometimes it’s ok to be alone on our devices, together in quiet contentment. But other times the lack of transparency about what we’re doing can be incredibly alienating to others. This wouldn’t be a problem if we could tell the difference between the two situations perfectly, every time. But alas, we are only human.

The streaming music ceiling

Cortney Harding makes some good points about the behaviors of different music buying personas in Is There a Streaming Ceiling?

The future is beginning to look like it will be a two tiered system — the top group of music fans will pay for streaming and everyone else will buy a handful of albums a year. Think of all the people you know who bought the Adele album, and I’ll bet that for many of them, it was the only album they bought this year. Many of these consumers aren’t all the interested in what streaming can offer them — they are content with hearing new music on the radio, buying one or two albums a year, and perhaps seeing one or two concerts.

It feels like the music industry has never been this complicated.

Service design for airport restrooms

The Transportation Research Board (TSB) recently published a 100-page PDF called Guidebook for Airport Terminal Restroom Planning and Design. If I know anything about the readers of this site, it’s that this is the kind of stuff we live for. Service design for airport toilets? Sign us up!

Ian Bogost provides a handy summary of this delightful document in The Airport Restroom of the Future:

The TSB report ends with an appendix on the “Airport Restroom of the Future.” After a surprisingly detailed history of public toilets, the TSB concludes that gender-neutral restrooms would offer travelers the most relief. Not only would they better address evolving gender identity norms, but they would also reduce congestion, maintenance, and accessibility by foregoing the barriers that help create the constriction of today’s restrooms. The TSB’s mockup puts individual sink basins in stalls to avoid flow to a common sink area, and adds a spacious waiting area flanked by two “art vitrines.”

I doubt airports care much about this, but it’s at least nice to see the TSB investing in this kind of service design research.

Wisdom quotes for the rest of us

Jennifer Kahn’s The Happiness Code, an article about bringing rationality to self-improvement, is interesting in and of itself. But it’s Hannah Whitaker’s photo illustrations with lettering by Luke Lucas that really drew me in. I’m sure many of you despise pithy “wisdom quotes” as much as I do. So these are like smooth balm to a tortured soul.

Wisdom

Wisdom

Wisdom

Wisdom

You can see more of Hannah’s excellent work here. Luke’s personal website with some his great graphic design projects is here.

Customer needs up and down the technology stack

I’ve seen Anshu Sharma’s Why Big Companies Keep Failing: The Stack Fallacy come up in my feeds a bunch of times over the last couple of days. I personally found the writing quite confusing, and had to read it several times to figure out what he was trying to say. I even drew a picture to help me.

If I understand the argument correctly, Anshu is saying that wherever your core business is in the technology stack, it’s easier to expand your market by going down the stack than up. Like so:

Stack Fallacy

This is obviously an oversimplification and leaves a lot of things out, but it was just a way for me to make sense of the article. That said, it’s this part in particular that stood out for me:

The bottleneck for success often is not knowledge of the tools, but lack of understanding of the customer needs. Database engineers know almost nothing about what supply chain software customers want or need. They can hire for that, but it is not a core competency.

The reason for this is that you are yourself a natural customer of the lower layers. Apple knew what it wanted from an ideal future microprocessor. It did not have the skills necessary to build it, but the customer needs were well understood. Technical skills can be bought/acquired, whereas it is very hard to buy a deep understanding of market needs.

In other words, it’s easier for Apple to take on Intel than it is for Apple to take on Facebook. Likewise, it’s easier for Amazon (AWS) to take on hardware manufacturers than it is for them to take on Salesforce. And the reason for this is that most companies understand the customer needs of the components their core business is built out of, but they don’t understand the customer needs of the businesses that other companies build using their components.

Update: This tweet from Peter Matthaei is a much better summary than the one I came up with:

.@RianVDM If your company uses something, it’s down the stack; anything that companies can build with your stuff is up the stack.

— Peter Matthaei (@mobivangelist) January 20, 2016

It’s an interesting theory, especially if you consider the logical conclusion that apps and services like Facebook and Salesforce (etc.) are at the top of the stack, and everyone not originally in the software business is going to have a really difficult time competing with them. I’d be curious to hear what others think of this…

The handicap of big product teams

Most businesses don’t admit how costly things like company wide announcements, project management, interviewing, internal politics, and large scale collaboration are on productivity. They all work against flow, and should be considered a handicap on product teams. Small teams substitute process with trust, eliminating overhead.

— Kyle Neath, Million Dollar Products

Why sad songs make us feel good

Princess Ojiaku summarizes some recent research on Why sad songs can be feel-good and noise music can be nice:

Sad music might make people feel vicarious unpleasant emotions, found a study published last year in Frontiers in Psychology. But this experience can ultimately be pleasurable because it allows a negative emotion to exist indirectly, and at a safe distance. Instead of feeling the depths of despair, people can feel nostalgia for a time when they were in a similar emotional state: a non-threatening way to remember a sadness.

I guess this is the reason we love to immerse ourselves in all kinds of books and stories as well. It’s a safe way to experience unsafe things. Or, as C.S. Lewis put it, “We read to know we are not alone.”

Utility is more important than usability

I’ve long held Jakob Nielsen’s Useful = usability + utility formula in high regard. The Introduction to Usability article it comes from is still one of the best intros to user experience I’ve seen. That said, I’ve recently started to wonder about the ideal ratios on the right side of the equation. What combination of usability and utility results in the most useful product? Is it a 50/50 split? 70% usability, 30% utility? It’s a purely academic exercise because there’s no way to prove any of it, but it did lead me to a theory:

I believe that utility (whether a product provides the features users need) is initially more important than usability (how easy & pleasant these features are to use) in product design.

Let me say right up front that I’m not saying usability isn’t important. I’m just saying that when it comes to a product being used extensively (and payed for) by users, it is more important to get the utility right from the start. Users will struggle through bad usability (up to a point), but they won’t use a wonderfully usable product that doesn’t serve a real need (see Path).

I’ll give two personal examples to back up this view1. My favorite social network at the moment is Goodreads. The site is slow, the UI is confusing, and the mobile apps make me feel completely lost, and yet I keep coming back to it. Because Goodreads is extremely good at what it does: helping me find books I’d enjoy, and letting me share good books with friends.

Goodreads

The second example is Pinboard. If I could take only one website with me to a deserted island it would be Pinboard. I use it more than any other online service. It helps me save, categorize, and find all the useful articles I’ve read over the 5 years I’ve been using it. The UI has tons of little weird quirks, and it’s very much barebones. But that doesn’t matter. It’s indispensable to me, so I care very little about its usability.

Pinboard

These two examples lead me to a second theory:

The more utility a product has, the less its usability matters.

I like Goodreads, but at some point if the usability becomes too frustrating, I’ll just leave. For Pinboard, on the other hand, I’ll walk through usability hell and back just to keep using it. It’s that essential to my work.

I’ve said this a few times in this article, but let me reiterate: I’m not, for a second, saying that usability isn’t important. I’m proposing that if you have a product that has insane levels of utility, its usability becomes a secondary factor in its success. To put it another way, the ROI on increasing utility is probably much higher than the ROI on improving usability.

The moral of the story is this: first find an idea that people can’t live without, then make it a beautiful, usable product. It’s very difficult to do it the other way around.


If you liked this article, you can sign up to get an email every Friday with all new posts that appeared on the site that week. You can, of course, unsubscribe at any time.

#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; } /* Add your own MailChimp form style overrides in your site stylesheet or in this style block. We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */


  1. That’s how science works, right? 

What happens when connected homes disconnect

Nick Bilton quit his Nest Thermostat because a software malfunction left him unable to heat his house for a while. In Nest Thermostat Glitch Leaves Users in the Cold he extrapolates to concerns about what happens when connected devices stop working as they should:

We’ve seen this before, with wireless fobs for keyless cars. They are supposed to make life easier by letting us do away with car keys, but they also make it easier for thieves to break in (by using a simple radio amplifier).

It also happened recently with Fitbit, the maker of wearable activity trackers. The company was hit with a class-action lawsuit in San Francisco asserting that the wristbands failed to “consistently and accurately record wearers’ heart rates,” which is vital for those with certain medical conditions.

I’ve heard dozens of other stories from people with connected homes who were locked out by malfunctioning door touch pads, or about newfangled security alarms going off in the middle of the night because a bug (one with wings, not a digital one) flew by.

This reminds me of Daniel Rivero’s Robots are starting to break the law and nobody knows what to do about it. Since companies are starting to require customers to sign agreements that prohibit them from filing law suits in the event of a malfunction, there is no one to hold responsible. Combine this with last week’s The internet of all the things, and I’m suddenly not so keen on this “connected home” thing any more.