What Leaders and Managers Can Learn from Getting Things Done
Trying to hold every open commitment to your team in your head, rather than capturing it in a trusted external system, is a specific, correctable source of the background stress leaders often mistake for the normal cost of the role.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 3 selected
The core lessons, applied to you
Capturing every open commitment to your team
A follow-up you owe someone from a one-on-one, held only in memory, consumes background mental bandwidth and risks being forgotten entirely, while capturing it externally frees that bandwidth and protects the commitment.
A leader forgets a follow-up promised in a one-on-one because it was never captured anywhere, and the team member notices the commitment was never honored.
For the next week, capture every commitment you make to a team member the moment you make it, in one trusted place.
Clarifying the next physical action for a vague commitment
"Figure out the reorg" is too vague to act on and creates resistance; "draft the three reorg options and send to my manager by Friday" is concrete enough to act on immediately.
A leader's list is full of vague items like "handle the team structure," which get avoided week after week because there's no single clear next action defined within them.
Pick one vague item currently on your list, and rewrite it as a single, concrete next physical action.
Organizing actions so you can choose confidently
Sorting your next actions by context (conversations to have, decisions to make, emails to send) lets you choose what to work on in a given moment with confidence, rather than anxiety about what you might be forgetting.
Group your current open next actions into two or three simple contexts, and work from those groupings for a week.
A weekly review to keep your system trustworthy
A leader's system of commitments to a team only stays useful with a regular review; without one, promises made in passing get quietly dropped and trust erodes.
Moving fast on urgent team needs and maintaining a complete capture system aren't opposites — a trustworthy system is what actually lets a leader move fast without dropping quieter commitments made along the way.
Name one thing, honestly
Name one commitment you've made to a team member that you're currently holding only in memory. What would it take to capture it externally today?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Group your current open next actions into two or three simple contexts, and work from those groupings for a week.