Great Products are Made of Tiny Decisions

Don’t underestimate the importance of craft.

Users Can Feel the Care

Don’t underestimate the importance of craft. Products are made from decisions big and small. When you put care into those decisions, users can feel it in the product.

Each small act of care may be imperceptible on its own, but together they compound into a product’s character. That character is what makes products easy to use, trust and enjoy. Craft is how you transmit care to people you will never meet.

Because great products are made of tiny decisions, we should put care into as many of those decisions as we can. A thousand small moments of care can accumulate into an impression of quality as customers step through their journey; but a single careless detail can bring it all down.

I do believe that we have this ability to sense care… I think you might understand it more if I said you sense carelessness.
Jony Ive

The more senior you become, the more your work moves towards product and organisational strategy. You could be forgiven for thinking that means stepping away from the details: thinking on longer horizons, shaping the business, and leaving execution to others. You will often be encouraged not to sweat the details, to focus on the bigger picture. Craft asks the opposite. The reason to sweat the small stuff is precisely that it becomes the bigger picture. The quality of the product today helps determine whether the business is still here tomorrow.

The details are not the details. The details are the design.
Charles Eames

Train Yourself to Notice

How do you develop a sense of craft? You start by noticing more. Look closer at the tiny details everyone else has learned to ignore. As you use products day to day, slow down. When something feels unusually good, ask why. What did the team understand? What did they remove? What did they make easier than it had to be? The more you notice craft in the world, the better you become at applying it to your own work.

Take Tesla navigation. You can share a destination from Google Maps on your phone straight to your car. When you get in, it is already loaded. Put the car in drive and guidance begins.

That simple flow contains a lot of product judgment. Let’s break it down:

• First, Tesla meets the user where they already are. Most people plan journeys in Google Maps: checking the route, the timing, the parking. Tesla does not force that behaviour into its own app. The lesson: understand the wider user journey, including adjacent or rival products.

• Second, there is no address management. You do not save the destination, retrieve it from favourites, or find it in recents. It is just there when you need it. The lesson: remove the steps and features that only exist because the system needs them, not because the user does.

• Third, the default is brave. Selecting drive starts navigation. Tesla assumes the destination you sent is probably still your intent, but makes the state visible and gives you a way out. The lesson: intelligent defaults work when the user can see what is happening and change course easily.

• Fourth, the handoff feels almost invisible. You share to the Tesla app, but you do not have to open the app. It feels like sharing directly to the car. The lesson: sometimes the best interface is not an interface at all but a background automation.

• Fifth, Tesla uses its own strengths. Continuous connectivity across phone, app, cloud, and car makes this possible. The lesson: craft often comes from making full use of the capabilities your product, hardware, or organisation uniquely has.

• Finally, it lets the user act at the right moment. Planning a destination is easier on a phone than on a car screen, and it can happen while you are waiting, walking, or getting ready to leave. I almost exclusively set my destination before entering the car now. The lesson: improve the journey enough and you can create new behaviours.

The specific lessons here are almost incidental. We could have chosen a hundred different interactions and drawn a thousand different lessons from them. What matters is not the lesson itself, but the habit behind it: developing the eye to spot good product judgment, the curiosity to understand why it works, and the taste to reimagine it in your own context over time.

Put Craft Where It Matters Most

Do you have to care about all of the details? Yes. Every rough edge or moment of carelessness can damage how a product feels. But real product teams have finite time and attention, so you have to lean into craft where it matters most.

Focus your time where it matters most: onboarding, first use, handoffs and those key signature moments that make the product feel distinct. The smallest moments often carry the product’s character. Care enough to make the whole experience coherent, then care disproportionately about the moments that shape trust, ease of use, and differentiation.

There is also craft in knowing when not to invent. Jakob’s Law is a useful guardrail: users spend most of their time in other products, so they expect yours to work like the ones they already know. If there is a place to scale back your bespoke attention, it is reinventing platform conventions. Craft is not always invention; often it is restraint.

Where you can, scale craft through standards. Design systems turn care into reusable defaults: spacing, language, states, components, accessibility, motion, and interaction patterns that are considered once, then applied consistently across the product.

Build Products You Are Proud to Sign

Take pride in your work. Make every interaction feel considered, because users can tell when a product has been built with care. Develop your taste by deconstructing great experiences: slow down, notice what works, and ask what the team understood that others missed. Then bring that curiosity back into your own product. Each day, look for one opportunity to show care through a small, thoughtful product decision. Obsess over the details that matter, because they change the product’s character. Build products you are proud to put your name to. Otherwise, what are you doing here?