Conversation

Replying to
2/ Once u have to choose what to do, you can start killing two birds with one stone, postponing or advancing, outsourcing and parallelizing, down and upscoping, using different forms of leverage
1
24
3/ What you accomplish can only become more than the sum of its parts if you’re exercising agency in choosing the parts, and their sequence
1
18
4/ I suspect this rises exponentially; the higher the ratio between [what you could do] and [what you do] the greater the opportunities for strategic thinking and acting
1
17
5/ The number of combinatorial sequences of tasks explodes geometrically, as each task links to (thus potentially enables) more and more other tasks
1
11
6/ This is the basic problem with “pulling back” or “simplifying” your workload when you feel overwhelmed. The first commitments you kill are the highest leverage ones, because they’re furthest out on an exponential graph
1
9
7/ What makes this difficult of course is you have to handle emotional consequences of completing smaller and smaller % of what you could theoretically do. Feels like you’re getting less and less productive at first
2
15
8/ You have to make the switch from quantity to quality of actions completed. Once you get good at choosing quality ones, you ramp back up on quantity again (and also outsource, collaborate, crowdsource lowest complexity tasks)
1
13
9/ Next step is to get really good at meta tasks: packaging up projects w/ clear deliverables, influencing outcomes w/ quick light touches, inspiring and motivating ppl who don’t have to work for you, creating extraneous opportunities for ppl who work with you beyond $
1
15
20/ Curent frontier I’m at: how to outsource project GENESIS to contractors, while holding quality standards, dividing income from project, and giving them access to core company functions (like newsletter, blog, budgets) w/out making too big of mistakes
3
11
21/ Staying in constant communication seems necessary, which is a challenge to my usual long work sessions of deep concentration
1
14
Replying to
A) what happened to points 10-19? B) much of what you’re talking about seems to be operations scaling, not strategy per se. It turns into strategy when positive spillover exceeds direct effect. An example is doing what you said but with a view to unleashing a network effect.
Replying to
Whoops. I must’ve skipped...9. I see ops and strategy so deeply intertwined, maybe bec of TOC. It’s like I’m trying to create network effect in a small world subnetwork by scaling number of nodes (tasks) almost arbitrarily, instead of collaborators (which is way more expensive)
1
1