I finished the Airtel Hyderabad Marathon a few years ago. 42.2 kilometers. I was not fast. I was not elegant. At kilometer 35, I was having a detailed internal argument with myself about whether I had, in fact, made a mistake.
I finished.
What running is not
Running is not where I solve product problems. I've tried that. At some point around kilometer 12, my brain stops being useful for structured thinking and starts producing a stream of loosely associated images, anxieties, and song fragments. This is not the state you want for strategic planning.
Running is not a productivity hack. The time I spend running is not "recovered" through better focus later. I lose the hours. I give them to the pavement. This is fine.
Running is not a metaphor for resilience in the way it's usually presented — the idea that finishing a marathon teaches you that you can do hard things. I already knew I could do hard things. The marathon didn't teach me that. It taught me something more specific.
What running is
Running is the only activity I've found where progress is completely honest with you.
In product work, it's possible to be busy without making progress. It's possible to generate activity — meetings, documents, decisions — that doesn't move anything forward. The output is real. The progress is illusory.
Running doesn't allow this. Either you ran the kilometers or you didn't. Either your time improved or it didn't. The feedback is immediate, specific, and unchallengeable. You can't argue with your GPS data. You can't produce a deck that reframes a slow run as fast.
That honesty is uncomfortable and necessary. I spend most of my professional life in environments where success is ambiguous and causation is contested. Running gives me a regular experience of clear feedback, and I think that's kept my calibration honest.
The kilometer 35 problem
Here's what I learned at kilometer 35 of the Hyderabad marathon: your mind lies to you under sustained physical stress. It manufactures urgency, tells you the problem is unsolvable, presents quitting as the reasonable thing.
The lie is very convincing. It feels like rationality. It feels like you're doing an accurate assessment of the situation and reaching a logical conclusion.
But the conclusion is wrong. The assessment is made by a brain that is depleted and motivated to stop. It is not objective.
I think about this constantly in product work. When a product initiative is in its hardest phase — when the first experiments aren't working, when the team morale is low, when the stakeholders are asking questions — the internal voice that says "maybe this approach is wrong" is not always wrong. Sometimes it's right. But it's operating under the same conditions as the kilometer 35 mind: depleted, motivated to stop, not objective.
Learning to hear that voice and evaluate it clearly — rather than automatically trusting it or automatically overriding it — is the thing. Running has given me more practice at that than anything else.
On finishing
The marathon finish line is not a triumph. It's an arrival. There's a difference.
A triumph is a competition with an opponent. An arrival is just the completion of a journey you chose to take. I wasn't competing with anyone at Hyderabad. I was just trying to get to the end of something I started.
That framing — starting something, committing to the distance, and completing it without drama — is the thing I run for. Not the medal. Not the story to tell. Just the simple, honest experience of finishing what I began.