The Uncomfortable Truth About What We Design For
I spent last Tuesday watching a client's analytics dashboard. Seventy-three percent of their users never advanced past the onboarding flow. They had built something genuinely useful—a tool for creators to manage their projects—but most people stopped before they could make anything. This isn't a bug report. It's a design choice that nobody explicitly made.
We talk about democratizing creation. Figma talks about it. Notion talks about it. I talk about it. But here's what keeps me up: the easier we make consumption—just scroll, just watch, just tap—the harder creation becomes by comparison. Not technically harder. Psychologically harder. Our brains are pattern-matching machines, and if we've spent four hours in an algorithmic feed, the friction of a blank canvas feels insurmountable. I'm not sure this is even a design problem anymore, actually. It might be a dopamine problem.
- Netflix removed the "continue watching" list in 2019 to force deliberate choice—users rebelled immediately
- But
- TikTok's infinite scroll generates 50 million posts daily, and creators still flood the platform despite having zero guarantee of visibility
So which is the real human behavior? Both are.
The Maker's Paradox Nobody Discusses
Five years ago, I believed in "democratizing tools." Put design software in everyone's hands. Lower the barrier to entry. Make it free or cheap. But I've watched something strange happen with every tool I've shipped: the easier it becomes, the more people use it passively. They poke around. They consume templates. They share what others built. The actual making—the difficult, uncertain, messy work of creating something from nothing—that part stays hard because it fundamentally *is* hard, and no interface redesign changes that.
What we've actually done is create the illusion of participation. You can "make" a video in TikTok's editor without understanding composition. You can "design" a poster in Canva without learning typography. And maybe that's fine, maybe that's genuinely democratized, but I keep wondering if we've just redistributed the labor of creation—pushed it onto the creators while everyone else gets to feel creative without the vulnerability of actual creation.
The real makers? They're using the same tools they've always used. Adobe. Blender. Code editors. The people who make things that matter don't optimize for ease. They optimize for control.
Where the Design Debt Actually Lives
Last month I audited a product that had spent $2M on UX improvements. Faster load times. Better onboarding. Smoother animations. User retention went down anyway. Why? Because every feature we added was designed to reduce friction. Every pixel was optimized for the path of least resistance. And the path of least resistance is always: do less, consume more, keep scrolling.
This is the uncomfortable thing designers don't say out loud in meetings: consumption scales. Creation doesn't. Netflix serves 260 million accounts. How many of those are creators? The economics are backwards. The incentives are backwards.
I keep thinking about this in terms of defaults. When we design a product, we choose what happens when someone does nothing. We choose the starting state. And almost universally, across every platform, every app, every SaaS tool, we choose consumption as the default state because that's where engagement metrics live. That's where the business model works.
- We could make creation the default
- Build interfaces that demand something of users—not in a punitive way, but in the way a blank canvas demands something
- Make sharing harder than creating (don't do this, shareholders will hate it)
The Question I Can't Answer
Are humans naturally makers who've been engineered into consumption? Or are we naturally lazy, and tools just match that reality? I genuinely don't know. Some days I think we're born wanting to build things. Other days I watch my own behavior—the way I reach for Instagram instead of opening Figma when I have fifteen minutes free—and I think maybe consumption is the natural state and we've just gotten very good at packaging it as choice.
What I do know: every product I ship now, I'm asking a different question. Not "how do we reduce friction?" but "what friction are we removing, and what are we losing when we do?" Because the easiest path through an interface isn't always the one that leads somewhere worth going.
Maybe that should be written on every designer's monitor.
