Plan Without Planning
No rigid framework, no methodology homework. Capture first, and let structure emerge only where you need it.
Draft: outline only. Structure below; prose to come.
The framework trap
- Productivity systems that demand setup before use: projects, contexts, labels, reviews
- The maintenance tax: when organizing the system replaces doing the work
- Abandonment cycle: elaborate setup, falling behind, guilt, new app
- Finalist's bet: the daily list on a notepad was already the right shape
Capture first, structure later
- The whole entry flow optimizes for speed: tap below tasks, type, done
- Natural language over forms: "Call Sarah at 2pm"; the sentence is the metadata
- Capture from anywhere: share sheet, widgets, dictation, Capture (type, paste, or photograph)
- Rule: never let a thought wait for a form
Three moves, whole system
- Write it down, do it and check it off, or punt it
- Everything else in Finalist is optional elaboration on this loop
- You can use Finalist fully and never touch a setting
Structure that earns its place
- Headings, when a day needs sections
- Lists, when a project outgrows the day
- Tags, when your eyes want color (5–7, not a taxonomy)
- Day segments and time blocks, when the hours are contested
- Each is opt-in, each is one gesture, none demands maintenance
Growing without ceremony
- Week one: tasks only. Later: habits, journal, time blocking, when you feel the pull rather than because the system demands it
- The app meets you at your level of chaos
- A planner should fit the life you have, not prescribe another one
Related: One Day at a Time · Adding Tasks · Coming from Other Apps