Menu

Posts tagged “user experience”

"Ack, think, act"—building trust as a product manager

Many (oh my word, so many) years ago I wrote that I thought “fairness” is the most important characteristic of a good Product Manager. I still stand by that, but I had another thought recently about a related characteristic that forms the other side of that coin.

Jakob Nielsen’s 30+ year old usability heuristics remain true to this day, but it’s not just relevant to UI/UX. In particularly I think “Visibility of System Status” is one of the most important skills a PM can internalize. The principles states:

The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.

When users know the current system status, they learn the outcome of their prior interactions and determine next steps. Predictable interactions create trust in the product as well as the brand.

A PM can do nothing without trust. And to build trust in an organization, applying “visibility of system status” thinking is the #1 way to gain (and keep) that trust. That means a PM needs to:

  1. Ack: Acknowledge comments or questions as soon as reasonably possible (within hours, not days), even if it’s just to say, “I saw this and will get back to you.”
  2. Think: Respond to the original comment/question—with ultimate clarity—in a timeframe that balances thoughtfulness and pragmatism (days, not weeks).
  3. Act: Follow through on any commitments / next steps with regular proactive updates (for as long as it takes).

Note that the order is important here as well. Don’t Ack only after you’ve taken the time to Think. Don’t Act before you Think. That seems obvious, but I’m sure we recognize the wrong order all around us (and in ourselves!) all the time.

This all might sound hard, but once you’re in the rhythm of this cycle, it becomes second nature. “Ack, think, act” becomes just the way you go through your day. I think this is something we should all aspire to more in product (and probably beyond).

DeepSeek is also a design story

Interesting theory by Casey Newton that good Design helped Deepseek to become popular so quickly:

Both models “thought” for about 13 seconds. ChatGPT showed me a handful of two- or three- word snippets to tell me what it was doing during this time: “comparing protocols,” for example. For the most part, though, I was in the dark about what it was up to.

DeepSeek, on the other hand, shared more than 500 words about its process. I found it disarmingly humble. “Let me start by recalling what I know about these two technologies,” it wrote. “First, ActivityPub. I remember it’s a W3C standard, so it’s widely adopted in the Fediverse. Mastodon uses it, right?” (Right.) As the model continues, it eventually stops to review its work for errors. (“But I should check if I’m mixing things up.”) And 13 seconds after starting—the same time that ChatGPT took—it offered me its full answer.

This is what Jakob Nielsen—back in 1994!—called “Visibility of System Status” as part of his 10 usability heuristics for design:

The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.

Whether or not Casey’s theory about Deepseek is correct, I find it remarkable that over 30 years after those 10 heuristics were defined we are still seeing examples of their effectiveness on a large scale today.

Lessons from going freemium: a decision that broke our business

In Lessons from going freemium: a decision that broke our business, Bobby Pinero (CEO of Equals) makes some interesting points about what they’ve learned about freemium pricing models. This point about how user friction is not always a bad thing stood out to me:

In all of our pursuit of getting people into the product, the thing we forgot is that the goal of onboarding is not for people to complete onboarding. It’s not to just get people into the product. The goal of onboarding is for people to get their first moments of value from your product. To get “activated.” And removing friction is actually detached from this goal.

Just like everything in product, this all depends. Every business is different. But it’s nice to see things from another perspective

Improving work relationships using the lens of “The 9x Effect”

There’s a concept in UX design that I’ve been thinking about a lot in the context of interpersonal work relationships. It’s called “The 9x Effect” and I wrote about it… checks watch… 10 years ago. In short (and heavily simplified), customers value their existing solution/product 3x more than any new “innovation”, and companies overvalue their innovative new product by 3x of what’s currently in the market. So you end up with a 9x mismatch between what companies build and what people believe they need.

There’s another adage that when someone cuts you off in traffic they’re a jerk, but if you cut someone off you had a good reason. We tend to rationalize our own actions while not giving others the benefit of the doubt.

So I’ve been thinking about this in the context of competence at work. I wonder if we sometimes overvalue our own competencies by 3x, and undervalue others’ skills by 3x[1]. And I wonder how that affects the efficiency and health of organizations. We all have a tendency—especially in large organizations—to disagree with strategy, or at the more extreme end of the spectrum, view leadership as “inept” or “clueless”. And I wonder if it’s because of the 9x effect, and if we can all just divide our own opinions by 3 things would get a lot better.

What might happen if as employees we go “well maybe the way I think it should be done is only ⅓ of the answer”. And what if, in turn, leaders go “maybe the way I think things should be done is only a ⅓ of the answer.” Would we be able to come together in the middle and make better decisions together, and in doing so massively improve a company’s culture, autonomy, and efficiency? Sorry, I don’t mean to be a vague question-talker with this post, but I am genuinely curious about this.

A little more critique of ourselves, a little more grace for others… I think I’d like to try that.


  1. Yes, I’m very familiar with the Dunning-Kruger effect. What I’m talking about here is a bit broader and through a different lens.  

Dear Alt-Twitter Designers: It's about the network!

Excellent post by danah boyd, reminding us that with social networks it all comes down to nurturing the network dynamics, not the technical features.

That’s the thing about social media. For people to devote their time and energy to helping enable vibrancy, they have to gain something from it. Something that makes them feel enriched and whole, something that gives them pleasure (even if at someone else’s pain). Social media doesn’t come to life through military tactics. It comes to life because people devote their energies into making it vibrant for those that are around them. And this ripples through networks.

Threads isn’t depressing, it’s just not for you

I don’t think that Threads—the new Twitter-like service from Meta—is above critique. It’s noisy, it lacks a lot of features, and there seems to be a lot of desperate land-grabbing going on by various celebrities and brands. You might even say the whole thing feels off—and there is even a fairly academic reason for that feeling. In It’s Not Cancel Culture—It’s A Platform Failure Charlie Warzel reminds us about “context collapse”:

Context collapse occurs when a surfeit of different audiences occupy the same space, and a piece of information intended for one audience finds its way to another—usually an uncharitable one—which then reads said information in the worst possible faith.

We’ve probably all experienced this to some degree—you say something and it gets misunderstood or misconstrued (sometimes understandably!) by an audience that doesn’t have all the context. Anne Helen Petersen uses that concept to explain exactly why The Thread Vibes Are Off:

Twitter was for thoughts, and Instagram is for vibes—and Threads is trying to pull your Instagram feed into a Twitter format. And I’m here to tell you: THE VIBES ARE OFF. […]

What’s happening early on with Threads is that influencers are experiencing their own kind of context collapse, where their vague, sometimes vapid messages are traveling toward a different type of audience. This is pretty much what Threads feels like to me now: a place that’s ostensibly interesting (look, so many people are already here!) but is actually totally boring. It’s “fun,” but definitely not funny.

So, like I said: Threads isn’t above criticism and there’s a lot of work to be done to improve it. But I also think it’s important for the complainers to realize that it’s possible that maybe—just maybe—Threads isn’t for us. And that’s ok. One example is the constant complaints I see (and I have as well!) about the lack of a “following-only” feed, and a lot of “how could they launch without it” incredulousness. However, to that point, Sara Morrison makes this observation in TikTok is confusing by design:

TikTok is the ultimate example of how our digital world is shifting from seemingly limitless possibilities and choice—the internet of my formative years—into a controlled experience that’s optimized to know or decide what we want and then deliver it to us. And TikTok is one of the best examples of this change.

That piece is worth reading in full, but it explains how the chronological feed might be a thing of the past—and not because companies want it, but because user data shows that they want it. This is why posts like Facebook’s Threads is so depressing—which I’ve seen quoted and mentioned a lot in my various feeds—really rubs me the wrong way. It is one big wall of snark about how bad Threads is, how it should die, and how it has no redeeming qualities at all. What’s worse is that I’ve seen lots of product people quote that piece and praise it, which I find really confusing.

Yes, Threads has lots of room for improvement. I find it too chaotic (right now) for what I want in a social network. But if you scroll just a little bit it’s clear to see that people on there are having a blast—so how about we don’t judge anyone and everyone who gets on there! Isn’t having empathy for users and curiosity around certain behaviors everything in product? Shouldn’t we be impressed and interested in what we can learn from how Meta built that product to scale to 10 million users in 24 hours without a hitch?

It’s natural to get riled up about products that mean something to us, but we have to guard against blind spots when it comes to how people who are not like us use the web. It’s ok to not like Threads, but it’s not ok to negate and mock the experience of millions of people who are clearly enjoying the product immensely. Not just because it’s unkind and unnecessary, but also because we’d be losing out on a huge opportunity to learn from how that team executes.

P.S. If you are more of a visual person, here’s a 16-second Youtube video summarizing this post.

Product-led growth and micro-conversions

The first part Sara Ramaswamy’s Product-Led Growth and UX is just a summary (a good one!), but the “How UX Can Help” sections has some really great insights and ideas, like this one:

While macro conversions (high-level conversion tied to the primary purpose of the site) are often the first success indicators considered, it is, however, important to define and revisit micro conversions, which measure incremental improvements to the user experience. In product-led growth, products are competing at the micro-conversion level. Analyze the conversion user journey and create milestone micro conversions that capture progress toward primary macro conversions. Also identify secondary user actions on site that are correlated with macro conversions.

“Compete at the micro-conversion level” is a really good lens to keep in mind as we improve our products.

Design with users, not just for them

In What we’ve learned from our users about designing for accessibility Andrew Gosine describes how their team lived out one of Slack’s primary design principles, which is to design with users, not just for them:

In another proposed update, we tried to get clever about where we placed a user’s focus when they opened a thread. If there was an unread message, we’d drop them into that first message in the thread. If there were no unread messages, we’d move focus to the message input. We believed this would increase efficiency for screen-reader users. Our feedback group reacted strongly to this. We’d unintentionally deteriorated the reliability of knowing exactly where you would be when you open a thread, and, as a result, we broke the way-finding our users relied on in Slack. Thanks to our group, we reverted that change.

This is a great read with lots of examples from the project.

Link roundup for March 1, 2023

Open Circuits is “a photographic exploration of the beautiful design inside everyday electronics. Its stunning cross-section photography unlocks a hidden world full of elegance, subtle complexity, and wonder.”

Good conversations have lots of doorknobs. This is a fascinating essay about the elements of good conversation and the difference between “takers” who keep things going, “givers” who tend to ask a lot of questions, and how the wrong match-up can cause a conversation to stall. Includes good advice backed up by tons of academic research. This is one to save and revisit often.

Why do modern pop songs have so many credited writers? Some of the examples are wild. “When these cases are settled in favor of the plaintiff, more songwriting credits are added after a song’s release. This is why the number of songwriters listed on Mark Ronson’s “Uptown Funk” has increased over the years. To avoid a Mark-Ronson-style-courtroom-induced headache, artists will sometimes preemptively credit writers of older songs even if the similarity between the older song and their composition is purely coincidental.”

A “Last of Us” Episode 7 musical mystery (light spoilers). I just want to say don’t worry The Last of Us fans, I’m thinking about the important things over here.

The choice is easy. Robin Sloan with a good reminder: “Anyone who adds one of those email newsletter pop-ups to a website demeans them selves and makes the world worse for everyone else.” Reminder that if you are an author using Substack you can turn off “Subscribe prompts on post pages” in Settings.

Quick Review Summary. Ok this seems like an actually good use of OpenAI. Instead of poring over hundreds of reviews of a hotel, copy the Tripadvisor URL of the hotel into this website and it will generate a summary of the general sentiment of the hotel.

Neurodiversity Design System. Great resource. “The NDS is a coherent set of standards and principles that combine neurodiversity and user experience design for Learning Management Systems. Design accessible learning interfaces supporting success and achievement for everyone.”

SoundPrint is an app to “discover quiet places and share them with others.” This looks really useful, especially if you’re a fellow tinnitus sufferer.

Principles for building software for developers

Kathy Korevec started a series about her principles for building software/tools for developers. Since I work on Postmark—one such tool—I read the intro post with great interest. The second installment is on the principle she calls You are a chef cooking for chefs:

Developers are masters of building applications, so when you’re building tools and experiences for them, you’re cooking in their kitchen. You can marvel at the delight you bring to the experience because no one can appreciate your hard work more than another developer. Developers can spot inconsistencies, antipatterns, and hurdles a mile away, so you must pay close attention to these details. At the same time, they know the challenges, understand the concerns, appreciate the details, and can provide crucial feedback to make your product even better.

This is one of the main reasons why I love working on developer tools. It’s an audience that can be brutal critics. But for the most part they do that because they care and want to see the product succeed—not because they want to fight just for the sake of it. And because they care, feedback generally have a degree of specificity that is invaluable for troubleshooting, use case discovery, and improving the product.

Anyway, this looks like a fantastic series and I can’t wait to read the rest. You can sign up for Kathy’s newsletter here.