Design
Learning notes on product design and UX, shared from the perspective of building understandable products.
To see posts from a specific category, click the category button above.
-
Every pixel on your screen tells a story, but it’s the words that guide users through it. A single word change can dramatically shift how people experience your product. Whether you’re building an app, designing a website, or crafting a digital service, the text users encounter shapes their entire journey. This guide covers UX writing
-
1. Why UX Research Insights Often Fail to Become Actionable If you have ever wrapped up interviews, usability tests, support ticket reviews, or field observations and thought: You are not alone. This “organized but ambiguous” outcome happens even in teams that are doing research frequently. The issue is rarely the amount of data. It is
-
1. Why UX Research Often Fails to Influence Real Decisions UX research rarely fails because teams did not collect enough data. More often, it fails because the data never becomes meaning. Many teams recognize this feeling: The problem usually sits between three stages that are treated as separate activities: Stage What Happens Where It Breaks
-
1. Why Observing Users Is Harder Than It Looks We live in a world where data is abundant. Dashboards update in real time. Funnels show precise drop-off points. Session replays let us watch clicks, scrolls, and hovers down to the millisecond. On the surface, it feels like we understand users better than ever. Yet many
-
Most teams have experienced this at least once: This is usually not a delivery problem. It is an expectations problem. The Kano Model helps you reason about a simple but often ignored idea: A feature’s impact is not determined by how “good” it is. It is determined by what users expect 1. Why “More Features”
-
If you’ve worked in agile teams for a while, you’ve probably seen user story mapping used in a very narrow way: This post is about a different idea: stories are primarily a tool for conversation and shared understanding, not a “mini contract” that shuts down discussion. This post looks at story mapping not as a
-
The customer intervew conversation was friendly. The person nodded along. They said your idea sounded “useful” and even suggested a feature or two. Weeks later, nothing happens. This gap between positive feedback and real-world action is where many product teams get misled. What usually went wrong is not execution speed or product quality. It is
-
Product teams often carry quiet assumptions: “Users will think like us.”“This is basic, everyone knows this.”“We can explain it if needed.” These assumptions feel reasonable because they are grounded in our own context. But user research repeatedly shows how fragile they are. Dan Russell, a long-time search UX researcher at Google, once shared an example
-
KJ Technique: A Better Alternative to Brainstorming for Turning Messy UX Inputs into Clear Decisions
Product teams run meetings every day, but decisions often feel slow, unclear, or political, especially when teams rely on unstructured discussions instead of methods like the KJ Technique. The KJ Technique is a simple but powerful way to turn messy opinions, data, and instincts into shared understanding and concrete action. This guide explains what it
-
UX problems rarely fail because teams lack data or effort. Instead, they happen because the problem itself is not clearly understood. Modern product teams deal with complex systems shaped by user motivation, context, and constraints. However, many discussions quickly collapse into screens and features, losing sight of the relationships that actually drive behavior. In practice,