Jony Ive Didn't Ship Fast. He Shipped with Taste.

In an age of move-fast-and-break-things, Jony Ive is a strange figure to celebrate.

He didn’t ship weekly. He didn’t iterate in public. He spent years on products that barely changed on the surface—and everything changed underneath.

He was obsessed with the things users never consciously notice.

What Taste Actually Means

Taste isn’t aesthetics. It’s not making things look pretty.

Taste is the ability to sense the distance between what something is and what it should be—and to care enough to close that gap, even when closing it is expensive and invisible to most people.

Ive’s famous examples: the click of an Apple mouse. The chamfered edges on an iPhone. The way the original iMac’s handle made it feel approachable. None of these features appeared in spec sheets. All of them shaped how millions of people felt about the product.

That’s what taste does. It operates below the level of conscious preference and creates emotional response. People don’t know why they trust the product. They just do.

The Discipline Behind the Aesthetic

The popular image of Ive is a designer who waved his hands and made beautiful things.

The reality was different. His team built hundreds of physical models for every product. They tested materials that never shipped. They rejected solutions that technically worked because they didn’t feel right.

This wasn’t perfectionism for its own sake. It was the recognition that the feeling a product creates is as functional as the thing it does. Users who trust a product use it more. Users who love a product tell others. The feeling is the product.

For indie builders, this isn’t an argument for slow. It’s an argument for deliberate.

What You Can Steal From Ive Without Apple’s Budget

You don’t need a model shop. You need an honest eye.

Ask, about every element of what you’re shipping: does this feel right? Not “does it work?” Not “is it good enough?” Does it feel right?

The onboarding flow that technically gets users to the core feature—does it feel welcoming or clinical? The error message that accurately describes what went wrong—does it feel human or like a machine scolding you? The pricing page that shows all three tiers—does it feel clear or confusing?

Ive’s lesson is that these questions aren’t decorative. They determine whether your product earns trust.

The Counter-Argument and Why It Doesn’t Win

The obvious pushback: Ive’s approach doesn’t work for indie hackers. You don’t have thirty years. You need to ship.

True. Ship fast. Learn fast.

But “ship fast” doesn’t mean “stop caring.” It means prioritize ruthlessly. You can’t polish everything—but you can decide what the one thing is that users will feel most, and make that feel right.

The details you choose to care about signal whether you care at all.

Ive’s career is an argument that the bar for shipping isn’t “does it work?” The bar is “does it deserve to exist?”

Ship more. Care more. They’re not in conflict.

The taste you build now—through small products, imperfect launches, honest self-criticism—compounds into something that can’t be copied.

Because taste is practice, not talent.