John Wooden, Socks, and the Hidden Cost of Bad Product Process

The Small Things That Decide Big Outcomes

If you’re a Product Leader whose organization is on a journey to become Product-led, this article is for you.

My goal is to “put the Productivity into Product” by helping your organization turn theory into practice while defining your Product Process in a way that makes it effective and repeatable.

There is a scene in Ryan Holiday’s Discipline Is Destiny that feels almost absurd on first reading.

At the beginning of each season, legendary basketball coach John Wooden would gather elite college athletes — players talented enough to compete for national championships — and teach them how to put on their socks and shoes.

Not metaphorically. Literally.

He explained how to smooth the socks properly to avoid wrinkles. He showed how to lace shoes carefully. He walked through the process step by step with the seriousness of a surgeon reviewing operating procedures before an operation.

To modern ears, especially in a world obsessed with optimization, scale, and strategic vision, it sounds almost comical. Imagine a CEO opening a quarterly business review by teaching senior employees how to use a stapler.

But Wooden understood something that many organizations only learn after expensive failures: catastrophic outcomes are often the accumulated result of tiny process flaws that seemed too obvious to deserve attention.

A blister is small.

Missing the championship is not.

Product Failures Rarely Begin Dramatically

In Product Management, we often imagine failure as something dramatic. We picture the wrong roadmap, a visionary competitor, a disastrous launch, or a market collapse. In reality, most Product failures begin with something far less exciting: poorly executed fundamentals.

A vague customer interview. A weakly defined problem statement. A roadmap item approved because the loudest stakeholder spoke first. A feature request accepted without evidence. A survey question written in a leading way.

None of these feels fatal in isolation. That is precisely what makes them dangerous.

Product organizations rarely wake up one morning and consciously decide to build products nobody wants. Instead, they gradually drift there through dozens of seemingly harmless shortcuts. Like wrinkles in socks.

The Seduction of Advanced Product Thinking

There is a peculiar irony in Product Management. Organizations are often eager to discuss sophisticated concepts — AI strategy, portfolio optimization, platform thinking, growth loops, innovation frameworks — while simultaneously lacking disciplined approaches to the foundational mechanics of Product work.

It is the equivalent of designing a Formula 1 race strategy while ignoring whether the tires are attached correctly.

This is partly because foundational work feels unimpressive. No one gets promoted for running clean discovery interviews. Few conference talks celebrate well-structured evidence repositories. Executives rarely announce, with theatrical enthusiasm, that the organization has finally standardized how product teams evaluate market signals.

Yet these mundane operational details determine whether strategic decisions are grounded in reality or illusion.

These practices may appear administrative on the surface, but they shape organizational cognition. They influence how people interpret reality.

The organizations that consistently make good Product decisions are rarely magical. More often, they are systematic. They develop disciplined ways of capturing evidence, evaluating uncertainty, separating problems from solutions, revisiting assumptions, and structuring decision-making so that intuition is challenged instead of blindly trusted.

None of this is glamorous work.

Neither is properly putting on socks.

The Danger of Delayed Consequences

One of the most dangerous aspects of poor Product Process is delayed consequences. If a basketball player puts on socks incorrectly, the pain may not emerge immediately. The blister forms later — during stress, friction, fatigue, and repeated motion.

The same pattern exists in Product organizations.

An unclear customer insight may appear harmless during a roadmap discussion. But months later, after engineering effort, go-to-market coordination, executive reporting, customer training, support documentation, and opportunity cost accumulate around that weak insight, the consequences become substantial.

The original flaw becomes difficult to trace.

This creates a dangerous illusion. Teams begin believing the issue was execution.

“The launch failed.”

“The messaging was weak.”

“The timing was wrong.”

Sometimes those things are true. But often the real failure occurred much earlier, in the quiet procedural moments nobody considered important enough to formalize.

The wrong customer problem was identified. The evidence was anecdotal. The assumptions were never tested. The team confused stakeholder urgency with market importance.

By the time the organization feels the blister, it is already limping.

Discipline Is a Habit, Not a Switch

There is another layer to Wooden’s lesson that is especially relevant for Product leaders. Teaching socks and shoes was not merely about footwear. It was cultural conditioning.

Wooden was teaching his players how to think.

He was signaling that discipline is not situational. It is habitual.

You cannot suddenly become rigorous only when the stakes become high.

Organizations often behave as though discipline should activate selectively. They tolerate weak evidence gathering during discovery but expect precision during prioritization. They allow ambiguous requirements but expect engineering predictability. They ignore process consistency but expect strategic alignment.

But disciplined decision-making is not a switch.

It is a system of repeated behaviors.

The teams that make strong strategic decisions are usually the same teams that document assumptions carefully, structure meetings intentionally, maintain operational clarity, and establish consistent evaluation methods. These practices may appear administrative on the surface, but they shape organizational cognition. They influence how people interpret reality.

Product Process as Risk Management

One of the reasons Product Process is underestimated is because it is frequently framed as bureaucracy. Templates, checklists, workflows, and documentation can feel procedural and restrictive. In poorly designed organizations, they often are.

But effective Product Process is not about maximizing administrative activity. It is about reducing avoidable risk.

A good Product Process protects organizations from scaling weak assumptions. It helps prevent teams from confusing internal opinions for market evidence. It reduces the likelihood that important context disappears between teams or that prioritization changes wildly depending on who happens to be in the room.

In this sense, Product Process resembles aviation more than artistry.

Pilots use checklists not because they lack expertise, but because expertise alone is insufficient protection against complexity.

The more experienced an organization becomes, the more dangerous overconfidence can become. Experts are especially vulnerable to skipping fundamentals because familiarity creates the illusion of immunity.

“We already know how to do discovery.”

“We’ve launched products before.”

“We understand our customers.”

Possibly.

But even championship teams still put on socks incorrectly sometimes.

The Myth That Discipline Slows Teams Down

Many organizations resist process standardization because they fear slowing down. This concern is understandable. Process can absolutely become bloated and performative.

But the absence of disciplined process rarely produces true speed. More often, it produces hidden rework.

Teams move quickly into development, then spend months correcting misunderstandings, rebuilding features, resolving alignment conflicts, revisiting assumptions, and recovering from preventable mistakes. What appears fast at the beginning becomes painfully slow later.

Wooden’s lesson is fundamentally about friction.

A few extra minutes spent carefully preparing prevents far more painful interruptions later.

The same principle applies to Product organizations. A well-structured discovery process may initially feel slower than immediately building. But compared to six months of wasted engineering effort, it is extraordinarily fast.

Mature Organizations Respect Repeatability

Immature Product organizations tend to romanticize inspiration.

Mature organizations learn to respect repeatability.

This is one of the least glamorous but most consequential transitions in operational maturity.

At first, teams depend on heroics: a brilliant PM, an intuitive founder, a charismatic executive, or an exceptional engineer. Over time, however, organizations discover that sustainable excellence cannot rely entirely on individual talent.

It requires systems that allow good decisions to happen consistently across teams, situations, and time horizons.

That is the deeper lesson inside Wooden’s socks-and-shoes ritual.

Championships are not won only during visible moments of performance.

They are shaped earlier, in ordinary routines that establish reliability under pressure.

Likewise, strong Product organizations are not defined solely by launches, strategy decks, or keynote announcements. They are defined by the quality of the invisible operational decisions that happen long before the market ever sees the product.

Final Thought

There is something deeply humbling about the fact that one of the greatest coaches in history devoted precious time to teaching elite athletes how to wear socks.

Not because the task itself was profound.

But because consequences compound.

In Product Management, organizations often search for transformational frameworks while overlooking the procedural weaknesses quietly undermining their decision-making.

The irony is that many expensive Product failures begin in places that feel too small to matter.

A poorly framed interview.

An undocumented assumption.

An inconsistent prioritization process.

A roadmap decision unsupported by evidence.

Wrinkles in the socks.

And eventually, somewhere much later, the organization wonders why it cannot run properly when the pressure finally arrives.

If you’re looking for guidance in building effective product processes, I’d love to chat. Feel free to connect with me on LinkedIn.