Module 4
Time and Project Management
How Is the Work Organised?
Book section: Time & Project Management — How is the work organised?
Core lesson: Good organisation removes the friction of deciding what matters; bad organisation becomes a sophisticated way of not doing the work.
Learning outcomes
- Create a small, ranked project portfolio.
- Break a large project into phases and clearly defined next actions.
- Use the book's 1–3–6 Quest Method as a flexible daily guide.
- Recognise overplanning, scope creep, and hidden maintenance costs.
Lesson
1. One main project, a few side projects
The book repeatedly advises having one main project while allowing a few secondary pursuits. This balances focus with variety. Secondary work can be useful when you need a change of pace, but it must not constantly displace the thing you intend to finish. Select the current priority explicitly. Reassess it after a phase is complete rather than changing it every time something new seems exciting.
A long-running project can coexist with a smaller task that you aim to finish next. Think in phases. “Write a book” is too big to act on at once; “outline three chapters,” “draft chapter one,” and “revise chapter one” are workable units. Know the current phase, the finish condition, and the next action.
2. Use the 1–3–6 Quest Method
The book describes a daily method adapted from an existing 1–3–9 approach: one main quest, three side quests, and six mini-quests. The main quest is the essential task; side quests are worthwhile but secondary; mini-quests are optional small jobs, not commitments that must all be completed. A day can count as productive even when the optional jobs remain undone.
For example: main quest—edit a tutorial; side quests—send an invoice, choose photographs, take a walk; mini-quests—file a receipt, rename an image, reply to a message, and other small items. The method is supposed to reduce overwhelm, not create a daily scorecard of personal inadequacy.
3. Organise just enough
The book mentions switching from elaborate systems to flexible lists because improving the system had become more absorbing than the work. There is no single prescribed app or calendar. Use paper, a document, a list, or project software that allows you to see your current priority and the next step. When you catch yourself formatting a dashboard instead of building the thing, stop. Organisation has done its job when it makes action straightforward.
4. Shrink scope; consider the afterlife of the project
A project you can complete is more useful than an elaborate project that never reaches anyone. Cut features, chapters, or production elements until the core work is achievable. Also ask what happens after launch. A website with daily updates, a physical product requiring orders, or a community that expects moderation creates ongoing obligations. Choose deliberately between work that requires continuing upkeep and work that can be largely finished and left standing.
5. Practise intentional neglect
Not everything deserves equal attention. Batch minor administration, postpone nonessential chores, and choose quality over arbitrary busyness. This is not permission to ignore genuine responsibilities; it is a decision to protect a limited amount of creative attention. Some deadlines help; artificial urgency can create rushed, inferior work. Plan realistically.
Practical exercise — Build your project board (30 minutes)
List every open project. Mark one as Main, up to three as Secondary, and the rest Parked or Stopped. For the main project, write three phases, each with a concrete finish condition. Identify one unnecessary feature you will remove and one ongoing maintenance task the project may create.
Assignment — Work from a 1–3–6 list for five days
Start each day with the main quest. Keep a simple record of what was actually produced. If you fail to complete the main quest repeatedly, reduce its scope until it is an actionable task. At week's end, keep the system only if it clarified decisions and increased meaningful work.
Reflection
1. What have I been maintaining, arranging, or planning instead of finishing?
2. Which new ideas must wait so my main project can progress?
3. What would a version of this project look like with half its current scope?
Module takeaway: Use organisation to protect attention and remove choices, not as a substitute for creating.