Processing Over Memory: A Task System for the Overwhelmed Manager
Write everything down at the moment it's owed, groom into logical chunks, and free your head for thinking not remembering.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 85%
Charles, in back-to-back meetings from 10 to 6, keeps a robust-but-simple task system whose whole aim is to free headspace for processing rather than memory. He memorizes almost nothing and writes everything down—at the end of every meeting, exactly who owes what and by when—then grooms tasks into logical chunks and builds the next day's calendar around them.
Origin
Geoff Charles at Ramp, describing a system he built independently that Lenny notes closely mirrors David Allen's Getting Things Done (which Charles hadn't read).
Core principles
- 01Free up headspace for processing, not memory—spend almost no time memorizing anything
- 02Capture at the moment of commitment: log tasks the second a meeting ends, while they're precise
- 03Write tasks clearly and concretely, not as vague notes, including when each is due
- 04Systematize retrieval (searchable docs) so you can pull anything up quickly instead of holding it in your head
How to run it
- 1
Capture at the end of every meeting
Immediately write down the tasks you owe and the tasks others owe you—clearly and concretely, with due dates, not vague fragments.
Watch out Don't defer capture—waiting means you'll spend time grooming and reconstructing what was actually said.
- 2
Keep one running list
At the end of the day, maintain a single page (Charles uses Notes) of everything you need to do and everything others owe you.
- 3
Groom into logical chunks
Group tasks: tactical versus strategic, important versus less important, and by what other people owe you. Slack people reminders of what they owe and by when, so it's out of sight and out of mind.
Pro tip Set the reminder on the other person's deadline so their obligations stop occupying your attention.
- 4
Build tomorrow's calendar around the groups
The next day, create your calendar aligned to the goals you set the day before—cluster the tactical tasks together and carve out separate space for strategic deep thinking.
In the wild
Charles logs what other people owe him, then Slacks them a reminder timed to when it's due, so those items leave his head entirely.
→ His mental bandwidth stays free for processing and thinking rather than tracking outstanding items.
Common mistakes
Relying on memory
Trying to remember dates or what someone said consumes the exact headspace you need for processing and thinking; write everything down and make it searchable instead.
Capturing tasks vaguely
Logging a vague fragment instead of a clear, concrete task with a deadline forces you to spend time later grooming and re-deriving what you actually committed to.
Is it for you?
Best for
Managers in back-to-back meetings who feel overwhelmed by the volume of incoming obligations.
Not ideal for
People with light, low-volume workloads where a formal capture-and-groom system is overhead.
From the transcript
“I try to create or free up headspace for processing not memory and so I just basically spend very little time memorizing anything”
“at the end of every meeting I would write down the tasks that I owe and the tasks that someone else knows”
“I would write them down like as clearly as possible not like some vague thing but a very clear thing”
“the next day creating your calendar aligned to the goals that you've set for yourself the day before”
From the episode
Velocity over everything: How Ramp became the fastest-growing SaaS startup of all time
Geoff Charles (VP of Product)