3 ms·

For small/solo projects I prefer to use a notebook with the first few pages reserved for an index. I complement it with a kanban board on the wall (post-it note

For small/solo projects I prefer to use a notebook with the first few pages reserved for an index. I complement it with a kanban board on the wall (post-it notes). What I like about it: No procrastination in a management tool (over-planning, formatting, etc). No illusion of order (technology/computers have a tendency to make you appear disciplined, or to pretend you will be more disciplined by using them… I think it's bullshit. Discipline is a core skill, not the ability to use a tool). No software can provide the feel of moving a post-it note to the "Done" column. Physical data (pages) is also supposed to help memorization.

mrslave 9y ago
> No software can provide the feel of moving a post-it note to the "Done" column. Physical data (pages) is also supposed to help memorization. I tear mine into little squares. Occasionally I throw them at my colleagues (very small, very intense, on-site dev team) assuming they were somehow involved in creating the issue, and we are aligned on sense of humor.
a3n 9y ago
> For small/solo projects I prefer to use a notebook with the first few pages reserved for an index. You might consider starting your index on the back page, and let it grow "backwards" toward the content, sort of like stack and heap do in memory. I think I first saw this suggested by the Humphrey/PMP people, where a notebook is (used to be?) a prominent tool. https://en.wikipedia.org/wiki/Capability_Maturity_Model https://en.wikipedia.org/wiki/Capability_Maturity_Model