There is an intriguing pattern in design history: changes that matter rarely move smoothly from an old state to a new one. They often pass the point that seems like a sensible balance first.

In other words, correcting course sometimes means going too far. Sometimes it has to. The hand cursor's journey from macOS 26 to 27 is a small but telling example.

From erasure to choice

Before macOS 26, the pointing hand had three lines suggesting a glove and a pronounced cuff. In macOS 26, those details were pared back: the cuff disappeared, the three lines were removed, and the hand became a simpler, more abstract outline.

In macOS 27, the three lines returned in a lighter form. The cuff did not.

The hand cursors before macOS 26, in macOS 26, and in macOS 27: the three lines disappear and then return in a lighter shade.

This comparison captures a swing in design. The result is neither a copy of the old cursor nor a straightforward continuation of macOS 26. It is a third state: three pale lines, no cuff.

Had the designers started with the old cursor and made only cautious reductions, they might have arrived at a slightly more modern version of it: fainter lines, a shorter cuff, a cleaner outline.

The problem is that familiar forms create their own inertia. It is hard to tell whether an element still has value or remains simply because it has always been there. Only after macOS 26 removed almost everything could the value of each detail come into view.

Losing the cuff seemed to cost little. Losing the three lines, though, took away some of the hand's familiar structure and character. By macOS 27, the question was no longer what to remove from the old cursor. After clearing the slate, it became what deserved to return.

That is the point of going too far. It is a way to learn, not a final answer.

iOS 7: reject, then rebuild

A similar process played out on a larger scale with iOS 7.

Before iOS 7, the interface spoke the language of physical objects: leather, wood grain, glass highlights, metallic textures, and raised buttons. These details served a purpose in the early days of smartphones. Metaphors from the real world helped people understand the buttons, bookshelves, and notepads on a screen.

But when a successful form lasts long enough, it can turn from a solution into an unquestioned tradition. iOS 7 rejected much of that tradition. Textures vanished, shadows receded, type became extremely thin, icons were flattened, and the interface leaned on space, transparency, and color to create order.

Looking back, iOS 7 went too far in some respects. Its visual hierarchy weakened, its type was too thin, and parts of the interface became harder to read and use. Yet later versions of iOS did not return to iOS 6.

Shadows came back. Type grew heavier. Cards regained boundaries. Blur, materials, depth, and spatial layers returned to the interface. Leather and wood grain did not.

What returned was not the old form, but the work that form had done. Hierarchy, a sense of what could be touched, spatial relationships, and visual feedback were created anew.

Why keep an old form?

This brings to mind Nietzsche's idea of a “revaluation of all values.” Revaluation does not mean declaring everything in the past wrong. What needs to be broken is the habit of leaving long established things unquestioned.

Why must a button have a shadow? Why must an icon suggest a particular material?

Often, we inherit these forms instead of choosing them. A sufficiently bold design change first removes their air of inevitability. It says “no” because, without ever rejecting an old form, we may not even know why we would affirm it again.

This is also what “self-overcoming” means in design. A mature system can do more than overturn its past; it can keep testing its own decisions. iOS 7 moved beyond iOS 6, and later versions of iOS had to move beyond iOS 7. macOS 26 rejected the old hand cursor, and macOS 27 reconsidered the judgment macOS 26 had made.

Letting design change its mind

The hardest part is not making a bold change. It is remaining willing to reconsider afterward.

If a design team decides that bringing back the lines would amount to admitting failure, innovation soon becomes another dogma. A thoughtful revision is a fresh choice made after something has been questioned.

There is an important difference here. Keeping a detail without questioning it is tradition. Removing it entirely, discovering that it still matters, and then bringing it back is a choice.

That is why macOS 27's pale lines are more than a simple restoration. They have already been through a disappearance. The cuff's absence suggests it may have been a matter of habit. The lines' return suggests they serve a deeper role in recognition and visual structure. Their lighter appearance shows that bringing something back need not mean restoring it exactly.

An experiment in what matters

A gentle adjustment can only ask, “Could we use a little less of this?” Removing something altogether forces a deeper question:

If it were gone entirely, what would we actually lose?

The first question is about degree; the second is about what matters at all. The value of going too far lies in the comparison it creates. Take something away completely, and you can see whether it performed a necessary function or merely persisted through habit.

The balance rebuilt after that experiment is often more deliberate than the balance that came before. Design is no longer a straight line from “wrong” to “right.” It is more like a pendulum: from accepting the old, to rejecting it decisively, to finding a new way to affirm what still matters.

A wiser balance does not require a system that has never lost its way. It comes from having gone too far and learning what can be discarded, what must remain, and what deserves to remain in a new form.

Seen this way, the three lines that return, lighter than before, in macOS 27 are a tiny design parable. They are not nostalgia. They are a renewed affirmation after a moment of rejection.

Sometimes we have to lose something completely before we can know, for the first time, why we would choose it again.

More from the notebook