- Jun 2022
Local file Local file
allyou’re doing is drawing on a growing library of Intermediate Packetsstored in your Second Brain.
Intermediate Packets juxtaposed with Second Brain, it would have been better if he could have given a better analogy than intermediate packets to create some parallelism with Second Brain, alas... lack of creativity?
Notice the importance he's giving to Intermediate Packets by artificially capitalizing it. An indication of attempt to commoditize and sell "note taking" as a product.
link to https://hyp.is/OKlVhPBCEeyX96cojNH8rg/www.danah.org/name.html
example of the creation of a buzz word for something not really quite necessary. It's useful to give names to things, but this is just a synonym for a note, isn't it?
definitely not as developed as "second brain"
- Nov 2020
Fourth, big projects become less intimidating. Big, ambitious projects feel risky, because all the time you spend on it will feel like a waste if you don’t succeed. But if your only goal is to create an intermediate packet and show it to someone — good notes on a book, a Pinterest board of design inspirations, just one module of code — then you can trick yourself into getting started. And even if that particular Big Project doesn’t pan out, you’ll still have the value of the packets at your disposal!
The Intermediate Packet approach make big projects less intimidating.
Big projects feel risky because the time you spend on it feels like a waste if you don't succeed. Intermediate Packets allow you to finish smaller chunks. You can use this to trick yourself to get started on bigger things.
By always having a range of packets ready to work on, each one pre-prepared to work on at any time, you can be productive under any circumstances – waiting in the airport before a flight, the doctor’s waiting room, 15 minutes in between meetings.
If you have a range of packet sizes available to work on, you can use any time block size to deliver value.
Second, you have more frequent opportunities to get feedback. Instead of spending weeks hammering away in isolation, only to discover that you made some mistaken assumptions, you can get feedback at each intermediate stage. You become more adaptable and more accountable, because you are performing your work in public.
Intermediate Packets give you more opportunities to get feedback
The first benefit of working this way is that you become interruption-proof. Because you rarely even attempt to load the entire project into your mind all at once, there’s not much to “unload” if someone interrupts you. It’s much easier to pick up where you left off, because you’re not trying to juggle all the work-in-process in your head.
The intermittent packet approach makes you more resilient towards interruptions
Because you're not loading an entire project in your mind at once, you're not losing as much context when you get interrupted.
There are different schools of thought in the realm of productivity.
The energy school focuses on optimizing your energy levels. The focus school is all about getting into and staying in flow. The efficiency school is obsessed with the logistics of work.
Tiago positions his philosophy as the value school: Making sure you deliver value after every block of work by delivering, what Tiago calls, Intermediate Packets.
He draws parallels to Just In Time production from Toyota and Continuous Integration in software development.
Intermediate Packets is continuous integration for knowledge work.