In Part VII, I argued for the importance of interacting with information, instead of just passively consuming it. Interaction results in better learning at the same time as it creates valuable deliverables.
But incorporating all these new ideas about how work is completed – flow cycles and intermediate packets, downscoping and evolving deliverables, interaction over consumption – can be a little overwhelming. You may be wondering, “how do I know which of these techniques I should be doing at any given time?”
There is a very simple model drawn from Design Thinking that is helpful when thinking about abstract work. It is called divergence and convergence.
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.