Steve Jobs once said that without owning something over an extended period, where you have to see your recommendations through multiple iterations and "accumulate scar tissue for the mistakes," you learn only "a fraction of what you can."
In my experience, this insight applies directly to product design. When we take the time to truly understand problems and live with the consequences of our design decisions, we unlock the key to creating genuinely lovable products.
Yet here's what I've observed across hundreds of product teams: most stop defining the problem at the functional level. They ask 'How do we help people complete this task?' instead of 'How do we help people feel genuinely cared for while completing this task?' The difference between these two questions is the difference between a product that works and a product that people love.
Consider the last time you used a product that felt like it was designed specifically for you as a human being, not just as someone completing a task. Maybe it was how Spotify creates those perfectly curated 'time capsule' playlists that somehow capture exactly how you felt during a specific period of your life. Or how Notion gives you a blank page and doesn't tell you what to do with it, just a quiet "Get started with" toolbar that stays out of your way until you need it.
These aren't accidents. They're the result of teams who took the time to understand not just what people need to accomplish, but how they want to feel while accomplishing it.
Human is the foundation. Get this wrong and nothing else matters.
The human dimension measures whether your product feels like it was built by humans, for humans, with genuine human understanding. It's the foundation that everything else builds upon. A product can't be truly empathetic, authentic, remarkable, or transformational if it doesn't first feel fundamentally human.
Enter your email to unlock the full chapter and get notified when the book launches.
No spam. Unsubscribe anytime.
But what does human actually mean in the context of digital product design?
Human design recognises that:
You can feel the difference between products that get this right and products that don't.
Slack doesn't say "Message sent" or "Error: delivery failed." It says "You're all caught up" when there's nothing new. It says "It's quieter than usual" when a channel is empty. When you type a message and someone else is typing too, it tells you. These aren't features. They're tone choices. The product speaks like a colleague, not a system. That's human language.
Duolingo used to punish you for missing a day. The streak counter was relentless and the owl guilt-tripped you. People hated it. Not because streaks are bad, but because the product was operating on its own timeline, not yours. They softened it. The owl got gentler. Streak freezes became easier to use. The product started respecting that people have lives outside of language learning. That's human timing.
Notion gives you an empty page and doesn't tell you what to do with it. No wizard. No forced template. Just a quiet "Get started with" toolbar that stays out of your way. Some people ask the AI. Some people browse templates. Some people just start writing. The product supports all of these without privileging one over the others. That's human flexibility.
Spotify knows that music isn't content to be catalogued. It's emotional. Wrapped doesn't just show you what you listened to. It shows you who you were. The time capsule playlists work because they treat your listening history as a story about you, not a dataset about your preferences. The product remembers who you were, not just what you played. That's human recognition.
None of these are technically impressive features. They're decisions. Small, deliberate choices to put the person first. That's what designing for the human dimension looks like in practice.
Through analysing dozens of products that people genuinely love versus those they merely tolerate, I've identified four consistent qualities that make digital experiences feel human:
Products that feel human speak like humans, not like corporate entities or robots.
Conversational tone: "Let's set up your profile" instead of "Complete your account setup"
Helpful error messages: "Oops, that password too easy to guess. Try adding a number or symbol" instead of "Password not valid"
Natural phrasing: "Because you watched Breaking Bad" instead of "Recommended for you"
Context-aware communication: "Back at it, Matt" instead of treating everyone like it's day one
Human-centered products respect that people don't operate on computer time.
People need time to think: Important decisions shouldn't be rushed with countdown timers or aggressive prompts
Context switching is hard: People shouldn't be penalised for stepping away or taking breaks
Learning takes time: Complex features should be introduced gradually, not all at once
Mistakes happen: Undo options should be generous and obvious
Rigid products feel mechanical. Human products accommodate the messy reality of how people actually work.
Multiple paths to success: Recognising that people approach tasks differently
Graceful failure recovery: When something goes wrong, help people get back on track without shame
Changeable minds: People should be able to easily modify, cancel, or restart processes
Personal preferences: Interfaces that adapt to individual working styles and needs
This might be the most powerful pillar: products that feel human acknowledge people as complete individuals with lives, achievements, and stories that matter.
Celebrating progress: Recognising effort and improvement, not just completion
Remembering context: Building on previous interactions in meaningful ways
Acknowledging expertise: Treating experienced customers differently than newcomers
Respecting time: Showing gratitude for individual investment and attention
Here's a practical framework you can use today to assess how human your product feels:
Once you've completed your human design audit, the real work begins: systematically improving each dimension. In my experience, teams get the biggest impact by focusing on the area with the lowest score first.
If Language scored lowest: Start with a content audit. Review every piece of text in your product: buttons, error messages, help text, notifications. Rewrite them as if you're speaking to a friend who's trying to accomplish something important.
If Timing scored lowest: Map out your flows with a focus on cognitive load and decision points. Where are you rushing people? Where could you give them more time to think or breathe?
If Flexibility scored lowest: Look for the rigid, one-size-fits-all parts of your experience. How could you accommodate different approaches or gracefully handle when things don't go as planned?
If Recognition scored lowest: Focus on the moments when people invest effort or achieve something meaningful. How could you better acknowledge their investment and make them feel seen?
Remember: human design isn't about adding complexity. It's about adding consideration. The best designs are often invisible, removing complexity and design clutter to enhance the experience. The most human products feel simple because they've thoughtfully eliminated the friction and frustration that make digital experiences feel mechanical.
Human design is about removing the barriers between people and their goals, not adding features that showcase how clever we are as designers.
In the next chapter, we'll explore how human design becomes the foundation for truly empathetic experiences: products that don't just feel human, but feel like they deeply understand you.
The full book is being finished. Join the waitlist to get it first, and unlock the complete sample chapter now.
No spam. Unsubscribe anytime.