Version 1 of my new Productivity Pyramid. We'll discuss it tomorrow 9am PST on our Q&A call for the new coaching program fortelabs.co Register for call here: zoom.us
A few observations: each block represents a capability, built on and depending on the levels below it. Blocks have to be developed independently, but their power is only fully unlocked when the complete level is in place
Each level is also an extension and distinction of level below it. I.E. entire PARA level exists in proto form in "Organize" block two levels down. Entire JIT PM block exists in proto form in "Projects" two levels below
Capabilities tend to skip a level because each level is an "interface" between levels above and below it. I.e. Project List interfaces between basic GTD workflow below, and PARA above. Prog summarization plugs into PARA below, and makes info available on demand for JIT above
Pyramid grows "up", each new level becoming distinguished from the ones below it only as you approach it, like a mountain that looks like a single peak from far away, but as you climb it the hills and valleys emerge
I'm working now on distinguishing what are the "components" of Just-in-time PM. What are layers of abstraction, mediation, and dependency as one ascends the value stack? Asymptote is creative process itself, which we can approach but never fully proceduralize
Loading suggestions...