Module 7 · Level 2 · 15 min
Run your week from the map
The difference between a map you admire and a map you work from is about six clicks. Here they are.
Make the lines that are work look like work
Turning a node into a to-do is one action, and the app tells you what it buys: “it feeds the kanban and the gauges”. From that moment the line exists in three places at once — in the map where you thought of it, on the board where you move it, and in the gauge that tells you how much is left.
Seeing only what matters right now
- Filter the cards. The board's filter reads the text, the note and the parent branch — so filtering on a client name finds their cards even when the name is only on the branch above.
- Group by branch. The same board, cut by project instead of by status. Useful the moment you are running more than one thing.
- Time per column. Each column can show the time tracked on the cards it holds — which is how you find out that “quick admin” is four hours a week.
Getting the decisions back out
| You want | Do this |
|---|---|
| Just the actions, as text | Export the action items on their own — they paste straight into an email or a follow-up message |
| The board in a spreadsheet | Export the kanban as CSV, which opens in Excel |
| A picture for a message | Module 8 — image, PDF, or the file that carries the app |
| A link your client can open | Module 9 |
A rhythm that survives a busy week
- Monday, ten minutes. Open the map, tick what is really this week's work, date anything with a deadline.
- During the week. Live in the kanban. Move cards, add the ones that appear.
- Friday, five minutes. Read the map, not the board — the map is where you see what you learned, which the board throws away.
The map is the memory, the board is the week. They are the same document, which is why this costs fifteen minutes and not an evening.
Your turn
Build next week now: one map, every task ticked, three dates, and the board filtered to what is actually yours.
Then publish it to whoever waits on you — a partner, a manager, a client. A visible plan gets fewer “where are we?” messages, which is the real return on this module.