Productivity System Principles

Build the mental model

Every lesson in this course has been building toward ten principles that hold the whole system together, independent of which app you use.

• Capture quickly — write it down the moment you notice it, or the idea gets lost
• Organize only when it is useful — organizing is a tool, not a goal
• Every task needs one clear next action, not a vague description
• The calendar holds only time-specific commitments
• Notes must be retrievable — a note you cannot find might as well not exist
• Knowledge should connect to real use
• AI output requires human review — non-negotiable
• Tools should serve the system, not the other way around
• The system stays simple enough to actually maintain
• Review regularly — this is what closes the loop

Notes must be retrievable, and knowledge should connect to real use — the notes/knowledge lessons and the learning workflow and Feynman technique lessons built directly toward these two principles.

THE PRODUCTIVITY SYSTEM: FULL LOOP
----------------------------------
THE PRODUCTIVITY SYSTEM: FULL LOOP
------------------------------------
capture -> clarify -> organize -> prioritize
                                        |
                                        v
   improve <- review <- connect <- learn <- execute
      |
      v
 (loops back to capture)

Connect it to a real scenario

Turn the ten principles into a short audit — for each one, ask a single yes-or-no question instead of a vague feeling.

• Did I write it down within a minute of noticing it?
• Does every open task have one clear next action?
• Does my calendar hold only things tied to an actual time?
• Can I find a note I wrote three months ago in under thirty seconds?

Run this audit monthly — a system that once matched these principles can quietly drift away from them without a single deliberate decision.

• The ten principles are the synthesis this entire course has been building toward
• Most failures trace back to a missing habit, not a missing feature
• Run a monthly audit to check the system still matches the principles

Try the working example

function checkPrinciples(system) {
  const checks = [
    {
      principle: "review regularly",
      pass: !!system.hasReviewCadence,
    },
    {
      principle: "one task has a clear next action",
      pass: !!system.taskHasNextAction,
    },
    {
      principle: "keep the system simple enough to maintain",
      pass: system.toolCount <= 4,
    },
    {
      principle: "notes must be retrievable",
      pass: !!system.notesAreSearchable,
    },
  ];

  const satisfied = checks.filter((c) => c.pass).map((c) => c.principle);
  const violated = checks.filter((c) => !c.pass).map((c) => c.principle);

  return { satisfied, violated };
}

const mySystem = {
  hasReviewCadence: true,
  taskHasNextAction: true,
  toolCount: 7,
  notesAreSearchable: false,
};

const result = checkPrinciples(mySystem);
console.log("Satisfied:", result.satisfied);
console.log("Violated:", result.violated);

Satisfied: [ 'review regularly', 'one task has a clear next action' ]
Violated: [
  'keep the system simple enough to maintain',
  'notes must be retrievable'
]

toolCount: 7 exceeds the threshold of 4, so "simple enough" fails; notesAreSearchable: false means "retrievable" fails too.

Wikipedia: Getting Things Done — Productivity Systems