What Athletics Taught Me About Building Products

Athletics and product work look unrelated from a distance. One happens on a track, the other often happens around screens, documents, data, and conversations. But the longer I work across both, the more I notice that they demand many of the same habits.

The most important one is simple: improvement is usually less dramatic than people expect.

Progress is built in ordinary sessions

A competition gives you a result. It does not show the weeks of repetitive work behind it—the sessions that felt excellent, the sessions that felt average, or the days when showing up was the achievement.

Product work has a similar rhythm. A finished feature or a clear presentation might be the visible result, but most of the work happens earlier. It happens while understanding a problem, organising incomplete information, asking better questions, testing assumptions, and revising something that was not quite right the first time.

Neither process rewards impatience for very long.

Feedback is information, not identity

In sport, a distance, time, or score is honest. It tells you what happened on that attempt. It does not decide what you are capable of becoming.

I try to treat feedback in technology and product work in the same way. If an idea is unclear, a workflow is awkward, or an explanation does not connect with someone, that is useful information. The goal is not to defend the first version. The goal is to understand what needs to improve.

This mindset makes iteration feel natural. A first version is an attempt, not a final statement.

Different events require different strengths

Training across multiple track-and-field events teaches adaptability. Speed, technique, coordination, strength, rhythm, and patience do not always develop at the same rate. A method that works in one event may be completely wrong for another.

Technology is similar. Researching an unfamiliar topic requires a different kind of attention from analysing data or documenting a product workflow. Some problems need technical depth. Others need empathy, structure, or the ability to make complexity easier to understand.

Being adaptable does not mean changing direction randomly. It means recognising what the situation actually demands.

Pressure exposes preparation

Competition makes preparation visible. When there is limited time and one attempt matters, it becomes difficult to rely on motivation alone. Routines, fundamentals, and previous practice take over.

That lesson applies beyond sport. Deadlines and unfamiliar problems become easier to handle when the basics are organised: clear notes, dependable processes, honest communication, and enough preparation to make good decisions without panic.

Confidence is useful, but prepared confidence is better.

The work is never completely finished

There is always another technical detail to improve, another movement to refine, or another way to communicate an idea more clearly. That can feel frustrating, but it is also what keeps both fields interesting.

I do not see athletics and technology as two separate versions of my life. They continually influence each other. Sport gives me a practical understanding of discipline, recovery, pressure, and repetition. Product work gives me new ways to think about systems, people, and useful outcomes.

Both keep teaching me the same thing: meaningful progress rarely arrives as one perfect moment. It is built by paying attention, making the next adjustment, and returning ready to work again.