This is about the shape of accomplishing things. There's time versus scope. There's projects versus areas. There's broad versus narrow. Then there's the fundamental block of work. One fundamental distinction: - Are the triggering mechanisms associated with the accomplishment of scope or the passage of time? - [[My Obsidian-Based Project Management System]] is excellent for **scope**. Projects and areas. but handles time very poorly. - My [[Calendars are the Most Important Productivity Tool|calendar]] and [[iOS Reminders App]] are excellent for time, but suck at tying that back to **scope**. - **Neither system handles the [[Index Card Sized Productivity|Work block]]** A work block exists in time. It ties to a project and/or an area (which is essentially the same thing as saying it could be tied to [[OKRs]] and/or [[KPIs]]). Claude suggests the distinction is *wanting* versus *doing*. I'm not sure I buy (or possibly just don't understand) that. It's to do with the why and the how. I guess that makes some sense - scope is measured in *why*. How takes place in *time*, I guess. There are also distinct types of time-based things to do. Some are absolute (Taxes due March whatever), and some are relative to scope (Change oil after X months or Y miles). Actually that "oil" example is not a bad one. It's both. And that's why it's tricky. It could be needing changed due to time, or relative to work accomplished (i.e. miles travelled). Both affect each other, somewhat dependently and somewhat independently. It's [[Simplicity|Complex]]. > [!tldr] **** # More ## Source - ![[Untitled for now... 2026-06-19 11.50.02.excalidraw.svg]] %%[[Untitled for now... 2026-06-19 11.50.02.excalidraw.md|🖋 Edit in Excalidraw]]%%