In Part 14, we looked at the potential for massively increasing our bandwidth by creating “personal productivity networks.” These networks are made up of packets of work that move between “nodes” where some kind of intelligence is applied, whether human or software-based.
But what does it look like to operate such a network in our day to day work?
Through multithreading, a term borrowed from modern computing. While multitasking is switching rapidly between tasks, and is absolutely not a good idea, multithreading is switching rapidly between projects, and is essential. They may seem similar, but in fact require completely different approaches.
To view this post, become a Praxis member.
Members get access to:
- Instant access to the full archive of past members-only posts
- 1–3 new exclusive posts per month, including in-depth tutorials, deep dives into new ideas, guest interviews, and virtual workshops
- Members-only comments and responses in a private discussion forum
- Early access to new online courses, books, and events
Click here to learn more about what's included in a Praxis membership.
Already a member? Sign in here.