Case study · Coaching Accountability
Make next week build on this week.
You have already learnt the GTD® methodology and built your system. This coaching accountability program helps you keep using it: someone to review the practice with, a record of your commitments and a next conversation that picks up where you left off. One owner-operator's experience helped shape how it works today.
Stephan Jenner - Authorised GTD® Master Trainer & Coach for Australia & New Zealand
LICENSED BY THE DAVID ALLEN COMPANY®
Keep the work moving between conversations
Before each weekly call, you complete a one-page Weekly Check. Last week's fixes are already there, ready to mark done or not done. You add this week's wins, losses, fixes and lessons.
We start with what happened. What moved forward? What still needs attention? What will you work on next?
Each fix has an ID and returns on the following week's form. Your commitments have somewhere to go, and a regular point at which we come back to them.
The form also gives you a straightforward way to say how things are going: on track, struggling but running, need to talk, or need to pause.
You bring your experience of the week. I bring coaching attention to the practice you are working to maintain.
What that support looked like in practice
The client was an owner-operator of a small Australian business. They had already trained in the GTD® methodology, installed a system and experienced the difference it made when it was working.
The engagement combined a monthly two-hour session to work on the system with a fifteen-minute weekly accountability call in between.
Three developments showed what was worth building on.
The client began taking the initiative. They started sending through their weekly review output without being asked, then asking questions about my own tooling. The practice was becoming something they actively worked on between our conversations.
The structure survived a change of tools. During the engagement, they moved their setup from one application to another. The structure came with them. What they had learnt remained useful beyond the application in which they had learnt it.
Written follow-up became action. After monthly sessions, I extracted the next actions from the recording and sent them that day with the transcript link. The next session was booked. The client read the follow-up, replied, asked questions and acted on the actions.
The practice also spread within the business, with others trained or brought into the system.
These were practical signs of a client using and developing their practice: initiating reviews, carrying their structure into a new tool and acting on what we had discussed.
They showed what the support could contribute. Reviewing the engagement also showed what I needed to make more dependable.
What the experience changed
Around month seven, the written follow-up stopped and monthly sessions shifted to every second month. Neither of us had deliberately chosen that reduction or recognised it at the time. The program now includes a month seven checkpoint, where we read the record together and explicitly decide whether the engagement continues.
The weekly calls had been useful, but they left almost no written record. I had designed a process for carrying commitments forward in earlier work and had failed to build it into this engagement. The Weekly Check and returning fixes now make that continuity part of every week, rather than something that depends on my memory.
The scope had widened too, taking in IT migrations, tool builds and recruitment support. The accountability work now has a written scope that I am responsible for holding. Additional work remains available through a separate conversation.
The record also shows unanswered follow-ups and sessions cancelled without rebooking. There was no agreed pause, and the engagement faded without a review session or written summary. The weekly form now gives the client a way to signal that they need to pause, and close-out is a defined step to complete.
Those gaps were mine to address. The useful work deserved a delivery process that supported it consistently.
Put ongoing support around the practice you already have
The value in this example is concrete. A client began reviewing without prompting. Their structure travelled with them when their tools changed. Written next actions were read and acted on.
That is the kind of practical work this program supports.
Today, the weekly process gives us a record to return to. Your commitments stay visible. You can flag when something needs attention. We have a regular opportunity to review what happened and decide what comes next.
You have already done the work of learning and setting up. Give yourself support for the work of keeping it useful.
An anonymised account drawn from the engagement record.