Playbook 07
How I manage multiple tasks and workflows
How I keep many lines of work moving without dropping one: a ranked list, one board each, state written at every stop, and AI doing the background work.
The short version
- Rank the lines of work. Park the rest by name.A parked item with a name stops asking for attention.
- One board per line of work, and the board is the truth.Every item has an owner, a next step and what it is waiting on. If it is not on the board, it is not happening.
- Write the state down at every stop.The next session starts from a note, not from memory. That is what makes switching cheap.
- Every customer touch ends with a next step and a date.Logged in plain verbs: Called, Emailed, NOT sent.
- Decisions go on record with a date.A reversed decision stays visible with a line through it, so nothing gets argued twice.
Rank the work, park the rest
I am an Account Executive. My first line of work is the job: closing deals and growing the customers I have. Around it sit the pipeline that feeds those deals, the software behind it and the admin. No one holds all of that in their head. The system holds it, and my hours go to customers.
I keep one short ranked list of the lines of work that get my time. Everything else goes on a parked list, by name. Parked does not mean dead. It means decided: it gets no time until I open it myself.
Ranking works because attention otherwise goes to whatever shouted last. Parking by name works because an idea with a home stops asking.
Inside every line of work the order is fixed too:
- Revenue that exists. Customers paying now, deals about to close.
- Revenue that is close. Quotes out, warm conversations, renewals.
- What compounds. Content, lists, systems that keep producing.
- Infrastructure. Last, and only when it unblocks one of the 3 above.
Example. 2 free hours on a Tuesday. The list says deals first, and inside deals a quote that is out beats a new email sequence. The hours go to the customer holding the quote, not to rebuilding a dashboard.
The mistake: a list where everything is priority 1, and infrastructure built for work that has no customer yet.
One home, one shape
Every line of work lives in one folder tree, in plain text, under version control.
| Part | What lives there |
|---|---|
| Core | How decisions get made, the ranked list, the record of reversed decisions |
| One folder per line of work | Its charter, its board and its context: research, customer notes, plans |
| Shared machinery | Anything 2 lines of work both need: outreach, lead lists, ads, quotes, content |
| Archive | Parked and finished work, kept as a record and never reopened by accident |
Every line of work has the same 3 parts in the same places, so switching costs nothing. I never have to remember where something is, and neither does the AI: it loads only the folder for the task in front of it.
Example. A check written for one email campaign moves into shared machinery the day a second campaign needs it. One fix then reaches both.
The mistake: a different tool and a different layout for every project. Every switch then starts with finding things.
The board is the truth
Each line of work has one board. If it is not on the board, it is not happening.
- Every item is one action with an owner, a next step and what it is waiting on.
- What blocks money sits at the top.
- The board moves when the work moves, not on Friday from memory.
- A finished item keeps its date. The done list is the record of what happened.
- Dates are written as dates. "Next week" means nothing when the note is read a month later.
- Counts come from the source. I never quote a number from memory or from an old note. I count it again.
Example. Weak: "Follow up with the buyer." Strong: "Send the revised quote. Waiting on their unit count. Chase Thursday."
A board that lies is worse than no board, because I will trust it. So the system audits itself: it compares what the files claim with what is really there and reports every mismatch.
The mistake: using the board as a wish list. An item with no next step and no date is a wish.
The loop: open, work, close
- Open with the state loaded. The session starts from the last close note and the boards: what happened, what is blocked, and one next move per line of work, in rank order. Each move has a first step I can start in 60 seconds. Hard dates are listed with the days left.
- Name the line of work and the task. The system loads only that folder.
- The work runs. Research, drafts, builds, analysis. On internal work the system acts without asking.
- It stops at the line. Anything that sends, publishes, spends or commits me to a person waits for my yes. The full list is in How I put AI to work.
- Close at the task boundary, not at the end of the day. The board is updated, a close note is written, and everything is saved to version control.
The close note is what makes the next session cheap. 5 lines: what was done, where it stands, the next move, what it is blocked on, and what not to redo.
Example. "Done: revised quote drafted. Stands at: not sent, waiting on the unit count. Next move: call Thursday for the count. Blocked on: the customer. Do not redo: the 3 phase option, already ruled out."
The mistake: stopping when you are tired, with the state in your head. Tomorrow starts by rebuilding it.
Every customer touch ends with a next step
This is the rule that matters most in sales, and the system enforces it for me. After any customer touch, 2 things are written before anything else:
- What happened, starting with the fact. Called. Emailed. Texted. Met. A draft that did not go out is logged NOT sent. A plan is never logged as a call.
- The next step, with a date. If there is no better date, it is the next working day.
"Followed up" does not say whether the email went. And a deal with no next step is not in the pipeline. It is a memory.
It costs me one sentence. After a call I say what happened. The system writes the log line, sets the task and updates the CRM I built, in the background. My time goes to the next call.
Example. "10 Nov. Called. Wants the quote split into 2 phases. Next: send the revised quote by Thursday 12 Nov."
The mistake: logging the plan instead of the fact. "Will send quote" reads as sent a week later.
Decisions and reversals
Every decision is written when it is made, with the date and who made it. When one is reversed, the old line is struck through, the new one is dated beside it, and the reason is written down.
Example. Quotes go out as a PDF. Reversed 3 Nov: quotes go out as a link, because buyers open them on a phone.
That record is read before anyone fixes something that looks odd. What looks like a mistake is often a decision made for a reason nobody wrote down. It matters more with AI: a model that finds something odd will fix it, unless a file says the oddness is on purpose.
The mistake: deleting the old decision. A deleted line gets argued again. A struck line does not.
6 files to copy
Type a line of work and your name. All 6 templates fill in, and each Copy button copies the filled version. They are plain text: paste them into a notes app, a document or a repository. Anything still in double braces is yours to replace.
# Focus, ranked
1. {{line of work}}: {{what a good week looks like}}
2. {{second line of work}}: {{what a good week looks like}}
3. {{third line of work}}: {{what a good week looks like}}
Order inside every line: revenue that exists, revenue that is close, what compounds, infrastructure.
## Parked: no time until I open it
- {{name}}, parked {{date}}: {{why}}
# {{line of work}}: charter What it is: {{one sentence a stranger understands}} Who it serves: {{the customer, or the person who depends on it}} A good week: {{the number or result that says it is working}} State: {{live, building or paused}} as of {{date}} ## Decisions: dated, newest wins - {{date}} {{decision}} ({{your name}}) - ~~{{old decision}}~~ Reversed {{date}}: {{reason}} ## Never - {{the thing this work must not do}}
# {{line of work}}: board Updated {{date}} ## Blocking money - [ ] {{action}}. Owner: {{your name}}. Waiting on: {{who or what}}. Chase: {{date}} ## This week - [ ] {{action}}. Owner: {{your name}}. Next step: {{the first thing to do}} ## Waiting on others - [ ] {{what}} from {{who}}. Asked {{date}}. Chase {{date}} ## Done - [x] {{date}} {{what was finished}}
# Close: {{line of work}}, {{date}} Done: {{what was finished}} Stands at: {{the state now, as a fact}} Next move: {{one action, and its first step}} Blocked on: {{who or what, or nothing}} Do not redo: {{what was tried and ruled out}}
{{date}}. {{Called, Emailed, Texted, Met or NOT sent}}. {{what was said or sent, as a fact}} Next: {{one action}} by {{date}}. Owner: {{your name}}
# How to work with {{your name}}
Read first: the focus list, then the charter and the board for the line of work I name. Load only that folder.
Do without asking: research, drafts, analysis, building and testing, updating boards and notes.
Ask me first, every time: sending anything to a person, publishing, spending money, committing me to a date, a price or a meeting, changing anything live.
Never invent a number, a name, a price or a quote. If you do not know, say so.
When I state a decision, write it in the charter with the date. If it reverses an old one, strike the old line and add the reason.
After any customer touch, write the log line and set the next step with a date.
Before we stop, update the board and write the close note.
Start this week
- Write the ranked list. Park everything else by name.
- Make one folder per line of work with a charter and a board. Same shape for each.
- Move every open task to a board. One action each, with an owner and a next step. What blocks money goes on top.
- Log every customer touch as a fact, with a next step and a date.
- End every session with a close note. Then keep doing it.
What this is built on
I never stop learning. This playbook is built on the people below, then tested in my own work.
- Jeb Blount, Fanatical ProspectingProtect the golden hours. Selling hours go to selling, and admin, building and reporting fit around them.
- David Allen, Getting Things DoneEverything goes on the board, nothing lives in my head, and every item has a next action.
- Cal Newport, Deep WorkHard work gets long blocks with nothing else in them. The daily loop is built around those blocks.
Want to compare systems? Message me on LinkedIn.
I am an Account Executive first. The system keeps the rest moving in the background so my hours go to customers.
Ali Hamou · London, Ontario · This is the system I run every day. The examples are illustrations, not customer records.