Why Coaching Works Better When It Runs Like a Project

On a wet Tuesday in Manchester, a product designer I will call Elena opened her laptop for our session and stared at a colour-coded calendar that looked, at first glance, like evidence of maturity. There were blocks for strategy, blocks for deep work, blocks for exercise, blocks for inbox triage, and a noble green rectangle labelled personal practice. By Thursday most of it would collapse under two client revisions, one school call, a delayed train, and the slow leak of cognitive fatigue that no calendar app can display. “I keep building a beautiful week,” she said, “and then I seem to meet the real one.”

The line stayed with me because it describes the failure point in much personal development advice with unusual precision. Adults do not usually break down for lack of aspiration; they break down at the handoff between intention and coordination, when too many moving parts compete for the same hour, the same working memory, the same finite willingness to begin. After two decades of coaching people through attention problems, overloaded jobs, and domestic logistics that would strain a municipal transport authority, I have become less interested in whether someone is motivated than in whether their practice has a system sturdy enough to survive a normal week.

That word, practice, is often treated as though it belonged to yoga mats and notebooks, to something private and vaguely elevated. In reality, a personal practice, whether it concerns writing, study, exercise, emotional regulation, or recovery from chronic overcommitment, behaves much more like a project with recurring constraints. It has scope, dependencies, maintenance costs, hidden stakeholders, and failure modes that repeat so reliably one could almost schedule them. The coach who ignores this usually ends up dispensing encouragement where operational design is required.

Researchers have been circling this territory for years, though often under different names. Roy Baumeister’s early work on self-control, later revised and debated, helped popularise the idea that mental effort has limits, while Sophie Leroy’s research on attention residue at the University of Washington gave language to a phenomenon clients had long described without jargon: after switching tasks, part of the mind remains stuck to the previous one. Daniel Kahneman distinguished between fast and slow thinking, but what matters in a practical week is that both systems are affected when the day becomes a badly managed portfolio of obligations. If your personal practice depends on spare concentration appearing by magic at 8:30 p.m., you are not running a practice; you are running a lottery.

What most productivity advice misses is that adults rarely fail in one dramatic place. They fail by accumulation: a meeting that starts late, a message that demands an answer because silence feels risky, a task sized for an ideal brain on an ideal day, and an evening routine designed as though no one had ever had a headache. The coach, in that context, starts to resemble a project manager for human attention, someone whose job is to reduce friction, sequence work, surface constraints, and protect the critical path from wishful thinking.

That comparison can sound cold until you watch what happens when people stop treating their own commitments as moral theatre. Shame recedes, because the discussion moves from character to design; the question becomes less “why can’t I be consistent” and more “where does the system ask for a kind of effort I cannot reliably produce on demand.” For readers who have spent years being told to become more disciplined, this shift often lands with the force of common sense rediscovered.

There is a reason project managers obsess over visibility. A hidden dependency can wreck a launch; in personal life, hidden dependencies do the same, only they wear friendlier clothes. The morning study block depends on sleep, the sleep depends on ending work, ending work depends on defining done, and defining done depends on resisting the fantasy that one more hour tonight will rescue the week. Barbara Tversky, whose work on mind in motion has shown how deeply thinking is shaped by action and space, offers a useful frame here: cognition is not sealed inside the skull, and so the architecture around a task matters more than people imagine.

I have seen this most clearly with clients whose schedules look manageable on paper because paper does not register transition costs. A consultant in Bristol, whom I will call Marcus, wanted to rebuild a reading practice after years of fractured attention. He had assigned himself forty-five minutes every evening, which sounded modest until we tracked what happened between 6:00 and 9:00 p.m. There were handoffs with his co-parent, meal decisions, the emotional static left by Slack, and the peculiar exhaustion that follows a day of performing competence for other people. Once those transitions were visible, the reading problem ceased to be a question of will and became a question of placement.

Marcus had been trying to read at the point in the day when his executive function was already paying interest on earlier decisions. We moved the reading to a café near Temple Meads twice a week before his first call, reduced the target to twenty pages, and made the cue physical rather than aspirational: the book lived in the bag with his headphones, not on a bedside table where it represented a better version of himself. Within a month he was reading steadily, not because he had become virtuous, but because the system no longer demanded a heroic start from a depleted brain.

There is a lesson in that modest success that coaching circles sometimes resist. Personal change does not become less meaningful when it becomes more operational. On the contrary, adults often regain dignity when they can see the machinery clearly, when they understand why a practice keeps stalling and which component is under-designed. The work is intimate, but the method benefits from the same disciplines that keep complex projects from drifting into expensive confusion.

The problem with Sunday-night planning

Sunday night is the hour when many intelligent people produce plans they have no realistic chance of inhabiting. The children are asleep, the inbox has gone quiet, and the week ahead still appears as a clean geometric object rather than a sequence of interruptions, negotiations, and bodily states. In that calm, people overestimate available time, underestimate recovery needs, and assign difficult work to slots that belong, in reality, to transit delays, low blood sugar, or the aftermath of a contentious meeting. The plan looks rational because it has not yet met Tuesday.

This is where the coach who thinks like a project manager becomes useful. Instead of admiring the plan, we stress-test it. Which blocks require unusually high initiation energy; which tasks have hidden prerequisites; where are the buffers; what can slip without infecting three other commitments; what happens if the first deep-work session is lost by 10:15 a.m. Those are not pessimistic questions. They are the questions people ask when they intend a system to remain functional after contact with reality.

The late psychologist Peter Gollwitzer, known for his work on implementation intentions, showed that specifying when and where an action will happen improves follow-through. Yet the popular version of that finding often strips away the condition that matters most: the plan has to be plausible in the context of the actual day. “After lunch I will work on my thesis” is less robust than “At 1:30, in the library, after I refill water, I will draft one ugly paragraph before opening email,” and even that may fail if lunch regularly turns into problem-solving for half the office. Precision helps, but only after honesty.

In sessions, I often ask clients to plan from energy before they plan from time. Linda Stone’s phrase “continuous partial attention” remains painfully relevant here, because many adults are not entering a task from a neutral baseline; they are entering from a state of low-grade alertness in which the nervous system is already scattered. A calendar that treats all hours as cognitively interchangeable will punish them for being embodied creatures. Once the day is mapped by likely energy, the work can be distributed with far less drama: admin into the trough, drafting into the rise, and anything requiring judgment kept away from the hour when resentment masquerades as laziness.

Where the matrix fails on a real Tuesday

Classic prioritisation tools have their uses, but they often flatten the lived texture of work. Urgent and important are useful categories until a dentist appointment, a parent’s text, a software outage, and the need to eat lunch all arrive in the same three-hour window. On a real Tuesday, what matters is not merely rank order; it is sequence, task size, emotional load, and the cost of re-entry after disruption. A coach who borrows from project management learns to ask a more practical question: what can this person start, finish, or safely pause under current conditions.

That distinction matters especially for practices people claim they value but rarely protect. Writing, language study, exercise, meditation, portfolio work, and therapy homework all tend to be scheduled as though they were decorative extras appended to a serious life. Then they are displaced by anything with a sharper edge. In project terms, they have no defended resources, no agreed scope, and no contingency plan. The result is familiar: the practice survives for five days, disappears for three weeks, and returns burdened with guilt.

Several years ago, in a coaching room off Gray’s Inn Road in London, I worked with a barrister named Nina who wanted to maintain a daily reflective practice after a period of burnout. She had bought an elegant notebook, chosen a fountain pen, and promised herself twenty minutes every evening. By the third week she had missed nine days. “I keep thinking the problem is commitment,” she told me. “By nine o’clock, I can barely decide what yoghurt to buy.”

We rebuilt the practice as though it were a small recurring project. The notebook moved to her chambers; the daily unit shrank to five lines written before she checked overnight emails; the prompt was fixed for the week so she did not have to invent a question under pressure; and, crucially, we defined what counted as complete. If she wrote five lines and dated the page, the task was done. Six months later she had not written every day, but she had written often enough for the practice to become part of the working week rather than a referendum on her character.

That phrase, what counts as complete, deserves more attention than it usually gets. Projects derail when completion criteria are vague; personal practices suffer the same fate. “Work on my essay” is not a unit of action but a cloud of obligation, and clouds are poor cues for initiation. “Revise the opening paragraph for twenty minutes and leave a note for tomorrow” gives the brain a ledge to stand on. Adults who struggle to begin are often trying to begin something too large to perceive, which is one reason so much advice about discipline feels insulting rather than useful.

The quiet work of protecting a system

The most underrated part of coaching is maintenance. People are often willing to make a plan in a bright hour; fewer are prepared for the repetitive, slightly unglamorous work of keeping that plan alive when novelty has worn off. Project managers know this instinctively. They do not assume a timeline will defend itself, and they do not confuse a kickoff meeting with execution. In personal practice, maintenance means reviewing the week before it becomes a blur, noticing where friction accumulated, and making one or two structural changes before the same snag turns into a personality story.

For adults with complicated lives, this maintenance has to be gentle enough to survive bad weeks. A system that requires perfect tracking, immaculate categorisation, or nightly introspection will eventually become another source of debt. I have seen far more progress from low-friction structures: one trusted capture place, a daily ceiling on meaningful tasks, calendar blocks sized to real attention rather than fantasy attention, and a short shutdown ritual that tells the brain work has ended even when the list has not. None of this is glamorous, which is precisely why it works.

There is also the matter of emotion, which management language can obscure if used carelessly. People do not avoid tasks only because those tasks are large or poorly placed; they avoid them because tasks carry memory, identity, fear of exposure, and the residue of earlier failures. The coach has to be able to hear that layer without surrendering the practical frame. When a client says, “I keep putting off the application,” the useful response may involve both logistics and grief: the application needs a smaller first action, and it may also represent a life the person once expected to have by now.

That is why the project-manager analogy helps most when it remains porous. It brings rigour to scheduling, scoping, review, and risk, while leaving room for the fact that human beings are not software rollouts. They get ill, they care for other people, they lose momentum after criticism, they need transitions longer than they think they should, and they often require external structure before internal confidence catches up. A mature coaching practice accepts these facts without romanticising them.

The adults who make durable changes are rarely the ones with the most elaborate systems. More often they are the ones who learn to build for recurrence: recurrence of low energy, recurrence of interruption, recurrence of overestimation, recurrence of hope itself. They stop asking a weekly plan to prove they are serious and start asking whether the design can be repeated under ordinary strain. That is a quieter ambition than self-optimisation, though in my experience it is the one that alters a life.

If moinaki is useful, it will be for this reason: it treats learning and change as things that need structure, not slogans.