Skip to the page

Plainly Put

One sentence about building things, taken apart

HomeProduct

Solve the hard problem and keep the difficulty out of sight

A laptop body cut from a single block of aluminum looks simple. The work that makes something look simple is exactly what the user is not supposed to notice.

We try to solve very complicated problems without letting people know how complicated the problem was.

Jonathan Ive

Apple’s unibody MacBook, introduced in 2008, has a case milled from a single block of aluminum. To the owner it is a clean, rigid shell with no visible seams. Behind it sit machining processes that had to be developed for volume manufacturing, tolerances that had to be held across millions of units, and a long stretch of work by Jonathan Ive’s design group and Apple’s engineers. None of that is meant to be visible. The buyer is supposed to notice only that the laptop feels solid.

That is the principle in Ive’s line. The designer’s job is to take on the complexity so the user does not have to. The iPhone’s single front button follows the same logic: the software behind it is elaborate, but the user needs to learn only one thing about it. A product that shows its difficulty, through a crowded settings screen or a manual that must be read before first use, has passed its problems on to the customer.

For product teams, the practical consequence is where effort goes. Hiding complexity usually takes more work than exposing it. Each option removed from a settings page needs a sensible default, and every step removed from a setup process needs some automatic process to replace it. Teams that skip that work and simply delete the controls end up with a product that looks simple and behaves unpredictably.

The approach has a cost when the hidden parts fail. In 2010, the iPhone 4 used its outer steel band as part of its antenna, a clever way to make room inside a thin phone. Some users found that holding the phone a certain way weakened the signal, and they had no way to understand why, because the design had been kept deliberately invisible. Apple ended up giving away free cases. The complexity had been hidden until it broke, and then it surfaced without explanation.

A related cost is dependence. When a product is sealed and its workings concealed, the user cannot repair or adjust it and has to rely on the maker. For many buyers that trade is acceptable. For professionals who need to understand and control their tools, it can be a reason to go elsewhere.

There is a small irony in how the principle is practiced. Apple hides the difficulty from the product and then shows it in the marketing: launch videos for the unibody laptops walked viewers through the machining in detail. The user never has to know how complicated the problem was, but the buyer is often told, because the effort itself is part of what is being sold.

The principle is sound for most consumer products. It works best when the team hiding the complexity also plans for the moment it leaks: clear errors, honest explanations and a way for the few users who need control to reach it.