Thread by @tasshinfogleman

recently i've tweeted about how I'm using kanban in @NotionHQ to track my reading and writing, input and output

reading:

writing:

from my recent reading about kanban, the first step is to make the work visible. but once you do that, you are supposed to install "WIP" (work-in-progress) limits.

WIP limits have made Good Sense to me but haven't been sure how to do it in the work contexts that I'm exploring kanban in. I realized that WIP limits could really solve the throughput problems I'm experiencing with reading + writing

here are the WIP limits I'm trying for reading, based on Aristotle's three categories of friends (books are friends, amirite?) and also Jeff Bezos / my Audible subscription:

here are the WIP limits I'm trying for writing - 1 post in progress for each of the key categories I'm trying to write about on my blog and elsewhere:

i learned years ago that reading and writing in parallel is more efficient for throughput than reading one book or writing one essay at a time.

but taking @fortelabs Building a Second Brain course (input) and @david_perell's Write of Passage (output) have made my previous way of working (read and write all the things in parallel) unsustainable - a good problem to have!

i think WIP limits might just get the best of both worlds - higher throughput from parallel input/output, and the focus that comes from limits

exploring this intersection of productivity and strategy in my personal life *first* seems like a safe-to-fail way to get my learnings in. looking forward to applying those learnings to the team I manage (fundraising) and later the larger organization @MonasticAcademy

@MonasticAcademy this is not *strictly* necessary but now i can have a nice side-by-side dashboard of input and output