Books · systems · stories

A weekly review for small projects

A short written review can keep a promising idea connected to a real result.

Begin with the last promise

Open the note from your previous review. What did you intend to finish, and what evidence would have counted? Answer those questions before creating a fresh list. A project can feel busy while its central question remains untouched.

Write one concrete observation: a page was finished, a test failed, an interview changed the brief, or a task never started. Keep the observation separate from the story you tell about it. That makes the next decision easier to assess.

Find the smallest unresolved decision

Many projects stall around a decision that has not been named. It may be which audience to serve, which source to trust or which feature to leave out. Put that decision into one sentence, then list the information required to make it.

Choose the cheapest useful way to obtain that information. Sometimes it is a conversation or a small prototype. Sometimes a deterministic checklist or script is enough. The purpose of the next task is to reduce a specific uncertainty, rather than add activity to the calendar.

Leave a clear handoff to yourself

End with a single next action, a rough time allowance and a checkable result. Write where the relevant source or file lives in your own private notes. A future version of you should be able to begin without reconstructing the entire project.

This journal connects reading with practical systems. Todd's related work at 2 Solutions explores software and business projects; YouSucceed is another owned project in the same wider portfolio. Those are related destinations, not independent reviews of this site. The free reader worksheet is a small place to begin your own review habit.