Chapter 9 · Operations

Daily system and weekly review

You can leave this chapter when tomorrow’s block is on a calendar, not a mood, and you know the three numbers you will write down on Sunday.

Talent does not compound. Blocks do. If the reply block is “when I have time,” you will have time on January 1 and never again.

BlockTimeOutputSkip rule
Write15–20 minOne original, or noneSkip if it does not map to a job
Peer replies15 min8–12 Column A / CDo not skip
Reach replies15 min5–8 Column B with an addSkip if you would only cheerlead
Answer5–10 minEvery useful commentDo not skip. Mutual-reply weight.

If you only have 30 minutes, cut Write, keep Peers + Answer.

IST timing for English-speaking builders

The X log, five lines

  1. Date and minutes actually spent.
  2. Replies that passed the standalone test.
  3. Authors who answered.
  4. Original shipped (job name) or “none.”
  5. Profile visits and follows from Analytics.

Sunday: which reply earned a visit? Which original earned a follow? Which name goes on Column C? Which name leaves A? One kill. One keep. Ten names refreshed.

Habits that keep the system cheap

Printable daily card

DATE: ________ BLOCK 1 (15 min): __ peer replies author replied back: __ BLOCK 2 (15 min): __ reach replies author replied back: __ ORIGINAL TODAY: [ ] explainer [ ] scoreboard [ ] proof [ ] opinion [ ] none FOLLOWERS start / end: ____ / ____ PROFILE VISITS: ____ ONE THING I'LL REUSE TOMORROW: ____________ ONE THING I KILL: ____________
Drill · 15 minutes

Put a 45-minute event on tomorrow titled “A/C block,” not “content.” Create the log. Fill yesterday from memory.

← Ch 8Chapter 10 →