What a Golf Swing in Tokyo Taught Me About Managing Projects

On a recent trip to Japan, I did something I had never done before: I picked up a golf club.

Golf is enormously popular there, and driving ranges are everywhere — multi-level facilities where you hit balls into a massive net instead of across an open course. Curious, I decided to try it.

Watching golf on television, the swing always looked deceptively simple. Someone stands still, swings a club, and the ball sails off in a clean, controlled arc. How hard could it be?

The answer, as I discovered almost immediately, is: very hard.

The gap between watching and doing

Making contact with the ball at all took several attempts. Making contact with any real speed took many more. And the idea of controlling direction and distance — calculating the force and angle needed to send the ball toward a target hundreds of yards away — felt, in that moment, almost impossible.

Every part of the swing required conscious thought. Where are my feet? Is my grip right? Am I keeping my eye on the ball? Am I rotating my hips at the right moment? By the time I had run through the mental checklist, the swing was already ruined — too rigid, too calculated, too slow.

Watching the more experienced players at the range made the contrast obvious. Their swings looked effortless. Not because the mechanics were simpler for them, but because they no longer had to think about the mechanics at all. Years of repetition had moved the entire sequence — stance, grip, backswing, rotation, contact, follow-through — out of conscious thought and into what we call muscle memory. Their arms moved at the right time. Their legs shifted at the right moment. The ball went where they intended, and they barely seemed to notice the complexity of what they had just done.

The same gap exists in project management

This experience stayed with me because I recognized the exact same pattern in a completely different context: how professional services teams handle the discipline of tracking their work.

For someone new to structured project management — logging hours, updating project status, recording planned versus actual allocation — every single action requires conscious effort. What project does this hour belong to? Which client? Is this billable? Did I update the budget tracker? Did I tell the project manager about the scope change? Each of these is a small decision, and early on, every one of them has to be deliberately worked through.

The result, unsurprisingly, mirrors my golf swing: it feels slow, effortful, and unnatural. Entries get delayed. Details get forgotten. The information that comes out the other end is incomplete or inaccurate — not because anyone is careless, but because the entire process is still happening at the level of conscious thought rather than habit.

And when the underlying data is unreliable, everything downstream suffers. Budget execution becomes difficult to track in real time. Team allocation becomes guesswork instead of visibility. Profitability analysis is built on numbers nobody fully trusts. The project does not flow — it lurches, the same way an untrained golf swing lurches through its mechanical checklist instead of moving as one fluid motion.

What changes with repetition

The golf instructors at the range had a simple, repeated piece of advice: stop thinking, and let the body do what it has practiced. That advice is useless to a complete beginner — there is nothing yet to let the body do. But it becomes true, gradually, through nothing more sophisticated than consistent repetition.

The same is true for the habits that make project management actually work. Nobody logs time accurately and effortlessly on day one. Nobody instinctively knows to flag a scope change the moment it happens. These become automatic only after enough repetition that the brain stops treating them as decisions and starts treating them as reflexes.

I have watched this happen with teams over many years. In the first weeks of adopting a more disciplined approach to time tracking and project control, everything feels like friction. Entries are late. People forget which project a task belonged to. The habit has not yet formed, so every action still requires the conscious effort that a new habit demands.

Then, at some point — usually not a dramatic moment, but a quiet one — it shifts. Logging an hour becomes as unremarkable as checking the time. Flagging a budget concern becomes instinctive rather than a task someone has to remember to do. The team stops thinking about the process and simply executes it, the same way an experienced golfer stops thinking about their grip and simply swings.

Why this matters for how you choose your tools

This is also, I think, one of the most overlooked factors in choosing a time tracking and project management tool. A tool with a confusing interface or an awkward entry flow does not just create friction today — it actively delays the point at which the habit becomes automatic. Every unnecessary click, every unclear field, every moment of "wait, where do I enter this" is a small tax on the repetition that muscle memory depends on.

The best tools do not just capture data. They get out of the way quickly enough that the team can stop thinking about the tool and start simply doing the work — the same way a well-fitted golf club disappears from your attention once you know how to swing it, while a poorly balanced one keeps reminding you it is there on every single stroke.

The part that requires patience

If there is a lesson in this for team leaders, it is one about patience during the early, uncomfortable phase. When a team first adopts real project discipline — daily time entries, structured budget reviews, consistent squad allocation updates — the natural reaction is frustration. It feels slow. It feels like extra work bolted onto the real work. Team members question whether it is worth the effort.

That reaction is not a sign that the approach is wrong. It is simply the training phase — the equivalent of an awkward, overthought golf swing that has not yet become automatic. The teams that push through this phase, that keep practicing the habit even when it feels unnatural, eventually reach the point where the entries happen almost without thought, and the information the system produces becomes reliable enough to actually manage the business by.

I never did get particularly good at golf during that one afternoon in Tokyo. But I left with a clearer sense of something I have seen repeatedly over three decades of managing professional services teams: the discomfort of a new discipline is not evidence that it does not work. It is simply what the beginning of competence feels like, before repetition turns it into something you no longer have to think about at all.

---