COURSE ESSAY
·
US OPEN 2026
·
CONFIDENT UX APPLIED

What Shinnecock Asks

The course doesn't care how good you are. It only cares whether you trust it enough to commit.

This essay applies a Confident UX lens to Shinnecock Hills — the lens that interaction design produces when it focuses not on the interface but on the person inside it: what they're reaching for, what the system asks of them, and whether those two things align. That lens is usually pointed at the products and services people use every day. But a golf course is also a designed system, and the questions it asks of players are structurally identical to the ones any complex system asks of the people operating within it. What makes Shinnecock useful here is what makes it useful as a championship venue: it makes those questions visible.

The US Open returns to Shinnecock Hills this week — for the sixth time, and for the same reason every time. The course is one of the few in America that can reliably answer a question the championship always wants to ask: not who is the most skilled, but who is most capable of committing when the system makes commitment feel risky.

the system

Shinnecock Hills is a links course built on glacial sandhills at the eastern end of Long Island, a short walk from where the Atlantic meets the Peconic Bay. The terrain is treeless and exposed. The wind comes off the water almost constantly — prevailing from the southwest, but shifting enough across a round that no player can simply memorize the conditions. Every shot requires a fresh read.

William Flynn's 1931 routing was built around that wind deliberately. No two consecutive holes run in the same direction. The golfer who walks off one green and onto the next tee is almost never facing the same wind twice in a row. What plays downwind in the morning plays into it in the afternoon. What felt manageable on Thursday becomes a different problem entirely by Saturday.

This is not difficulty for its own sake. It is a design that ensures the course cannot be learned by the conditions alone. The player must learn the geometry — the routing, the slopes, the greens — deeply enough that the wind becomes a variable to be interpreted rather than a problem to be solved.

What the Course Asks

Every great course asks something specific of the player. Augusta asks for patience with the back nine — the ability to wait for the moment rather than force it. Pebble Beach asks for nerve on the cliffs, where the ocean is always in the corner of the eye. Carnoustie asks for endurance, a course that accumulates cost over eighteen holes regardless of how well the early holes are played.

what the course asks

Shinnecock asks for something different. It asks for familiarity deep enough that confidence is structural rather than conditional.

A player who knows Shinnecock — who has walked the routing enough times that the angles and slopes are internalized — can interpret the wind rather than simply react to it. When the breeze shifts off the right on the long par-four fourth, they know immediately which side of the fairway preserves the angle to the green. When the eleventh plays short in the swirling air, they trust the number rather than the feel.

That trust — the ability to act on what you know rather than what you're uncertain about — is what the course rewards. And it is exactly what a four-day US Open setup systematically tests.

The Confidence Profile
the confidence profile
SHINNECOCK HILLS
SHINNECOCK HILLS
·
CONFIDENT UX APPLIED
CONFIDENT UX APPLIED
DEPENDABILITY
HIGH
The geometry holds. The slopes and greens behave consistently regardless of conditions. A ball played to the right of the fourth fairway finds the angle to the green, every time. What changes is the wind — and the wind is consistent in its inconsistency. Players who know this can depend on it. Dependability, even demanding dependability, is the foundation confidence builds on first.
RESPONSIVENESS
IMMEDIATE
Shinnecock responds accurately to every shot — including the ones the player wishes it wouldn't. A slightly thin approach is redirected by the slope without appeal. Feedback is real-time and unambiguous. This is responsiveness working exactly as designed: the course answers every question the player asks, clearly and at once. The answers are simply honest about what was asked.
FAMILIARITY
VARIABLE - THE DEEPEST TEST
Flynn's routing — deliberately engineered so no two consecutive holes face the same direction — ensures that the player who learned the course on Tuesday is playing a meaningfully different course by Saturday afternoon. The wind shifts. Effective yardages change by forty yards in either direction. The course cannot be memorized. It can only be known — which is a different thing, requiring more, and taking longer.
SECURITY
LOWEST - BY DESIGN
Under US Open setup, the fescue rough, the green speeds, and the pin positions systematically reduce the margin available for recovery. The setup is designed to ensure that the cost of a mistake rises until security is no longer available as a default. It has to be earned — brought in from outside, in the form of preparation deep enough that commitment is still possible when the margin is thin.
HOLE 11 · PAR 3 · 159 YARDS
HOLE 11 · PAR 3 · 159 YARDS
Hill Head
Short in yardage. Infinite in what it asks. The green sits elevated and well-bunkered, subject to swirling wind that can shift the effective yardage by forty yards in either direction across a single round.
HOLE 16 · PAR 5 · 614 YARDS
The course's only genuine three-shot par-five, played into the prevailing wind with a twisting fairway lined by bunkers and a narrow green protected by more sand.
When the System Asks Too Much
the system
when the system asks too much

The 2018 US Open at Shinnecock Hills is remembered for two things. Brooks Koepka's masterclass — calm, controlled, structured — and Phil Mickelson's Saturday collapse, culminating in a moment that golf has been turning over ever since.

Saturday, Third Round — Hole 13

Mickelson faced an eighteen-foot bogey putt on the par-four thirteenth. He had been bleeding shots all day. The course, baked firm and running fast under a hot sun, had been pushed to the edge by the USGA's setup — pins in positions that left almost no margin for anything short of perfection.

He hit the putt too hard. As the ball accelerated past the hole and began its descent toward the runoff, Mickelson ran after it and struck it again while it was still moving — accepting a two-shot penalty rather than watch it roll off the green entirely.

What happened on that green was not a talent failure. It was a security failure — complete and visible. The security foundation — the sense that a mistake is survivable, that a bad shot does not cascade into catastrophe — had been consumed entirely. What remained was not hesitation. It was something past hesitation. The action itself became the protest.

By Saturday afternoon, the verdict among players was consistent: the USGA had lost the golf course. The setup had crossed from challenge into something else — not a test of the best players in the world, but a system that had stopped producing meaningful golf and started producing something closer to breakdown.

What happened at Shinnecock that Saturday is not unlike what happens when designers optimize for what they want the product to produce — a particular score, a particular conversion, a particular result on the dashboard — without adequately accounting for what the interaction is actually producing in the people inside it. The USGA knew what they wanted the course to yield. They had lost sight of what it was asking of the players. When the wind shifted and the greens dried, the gap between design intent and human capacity became visible to everyone watching. That is not a setup failure. It is a motivation-interaction-outcome failure. The course was no longer asking questions. It had stopped listening to the answers.

Koepka won that championship not because he played better than everyone else on Sunday. He played better than everyone else on Thursday, Friday, Saturday, and Sunday — because he arrived with security already built in. He didn't need the conditions to cooperate. He had already made them irrelevant.

The Player Who Arrives Ready
the player who arrives ready

Brooks Koepka's approach to the US Open is instructive not because of the outcome but because of the structure he brought to the event. Koepka is famous for his ability to raise his game at majors — but the more accurate description is that he arrives at major championships having already designed the security his game will need. He treats the rough and the speed not as obstacles to work around but as the system he is operating within. What the results make visible is a player who prepared until operating within that system felt familiar.

The result is a player who, when the course asks most aggressively, has already answered the question. The security is structural. It doesn't depend on the conditions being favorable. It depends on having been in those conditions enough times that the next action still feels possible.

what shinnecock teaches
What Shinnecock Teaches

Shinnecock Hills is not the hardest course in America. It is one of the most deliberately demanding ones — and the distinction matters.

The course was designed to withhold. Not carelessly, the way a poorly designed product asks more of people than it should — but deliberately, as a filter. The fescue rough, the exposed terrain, the wind that shifts direction between holes, the pin positions that leave almost no margin for error — none of this is accidental. The setup is engineered to remove every external source of confidence from the best players in the world and find out what remains.

In most systems, confidence is produced by the system itself. A well-designed product provides dependability — you trust it will behave as expected. It provides responsiveness — it reacts when you act. It provides familiarity — the patterns are legible without deliberate interpretation. It provides security — a mistake is survivable, and you know it before you commit. When those four conditions are present, confidence is an output. The person inside the system doesn't manufacture it. The system produces it.

For everyday products and services, the design target is the least prepared user — someone who arrives with a shallow pattern library, limited prior exposure, and almost none of the four foundations built in. The system has to provide everything. That is a narrow and demanding target: make the interaction work for someone who brings nothing.

Shinnecock, under US Open setup, assumes the opposite. These are the most prepared players in the world. They arrive with deep pattern libraries, practiced responsiveness to feedback, and years of internalized experience. The course can ask more of them — and does. It removes every external source of the four foundations to find out how deeply each player has built them in.

What it produces across four days is a differential. Between the players who arrived expecting the system to provide confidence, and the players who arrived having already built it themselves.

This is where the language of sport usually reaches for words like resilience, mental toughness, composure under pressure. Those words are accurate but imprecise. They describe what the outcome looks like without naming what produces it. You cannot train resilience directly. You cannot design a practice session around mental toughness. Those are containers for something more specific — and the four foundations are what's inside them.

What Koepka built in preparation was not a mindset. It was a system. He built dependability in himself — a repeatable process reliable enough to trust when the course offered nothing to lean on. He built familiarity not by memorizing Shinnecock specifically, but by accumulating a pattern library deep enough that conditions he had never seen before still had somewhere to land. A wind off the right on an exposed par-four wasn't new — it was a variant of something already solved, from Augusta, from Oakland Hills, from years of reading similar situations in similar light. That is what familiarity actually is at its deepest: not recognition of the specific, but legibility of the type. He built responsiveness by anticipating the feedback Shinnecock would deliver — honest, immediate, unforgiving — and preparing to receive it without catastrophe. And he built security not from the setup being forgiving, but from knowing that whatever the course asked, he had been somewhere close enough before.

He didn't arrive confident. He arrived having designed the conditions for confidence in advance. The four foundations were present at address — they just didn't come from the course. They came from everything that happened before the first tee.

Resilience, then, is not a fifth thing. It is the aggregate of the four foundations built inward rather than borrowed from the system. The player described as broadly resilient across many conditions is a player with a deep pattern library, a reliable process, practiced responsiveness, and security that doesn't depend on the conditions cooperating. What sport calls character, the framework calls internalized foundations. The mechanism is the same. The difference is that one is trainable in specific, targeted ways. The other is hoped for.

The rounds players carry with them from Shinnecock — the triumphs and the collapses alike — are memorable for the same reason. Not because the course was hard. Because what the course asked aligned with what the player brought. Alignment with no gap is flow. Alignment that reveals the gap is something else entirely. Both are honest. Both are remembered. The course doesn't manufacture the memory. It simply makes the alignment visible.

This is what the Confident UX lens does — it looks for where hesitation begins, and traces it back to what the system is asking of the people inside it.

At Shinnecock, the asking is deliberate. The course was designed to find the limit of confidence in the best players in the world, and it does exactly that. We have no recommendations for the course.

Most systems weren't designed this way. They were designed to support the people inside them — and somewhere between intention and experience, they started asking more than they should. For those systems, the target is clear: understand what the person brings, and design for the gap between that and what the interaction demands. That gap is where the work begins.

What is the person inside your system actually reaching for — and does your system know the difference between a fulfillment moment, a security one, and a capability one?

When the system asks more than it should — is the confidence you've built structural enough to hold?

Confident UX