Web URL for this note
Comment on this note
The distinction between areas, programs, and projects
Program design is a coordination tool
The value of planning is inversely proportional to the cost of experimenting
Program design is like creating the lego instruction book
Instead of planning not working as well as people in the past thought, as a society we’ve become worse at technological planning
Physical experiments are expensive
How do you measure real progress in research?
What role does scenario planning have in technological program design?
Maps help you figure out possibilities
Top of mind
Efficiency biases systems towards false negatives
Explaining things like I’m five helps avoid the Einstellung Effect
The tech tree model suggests that explicitly drawing out tech trees is important
A predictably successful idea is composed of known unknowns that that a team can execute against
Planning to Start vs Planning to Finish
Say ‘X is more important than Y’ instead of ‘X is important’
What are the different kinds of bottlenecks?
Is there a way that python collab notebooks could be integrated into program design and roadmapping?
Top of Mind Questions
Hunting vs Farming Ideas
What are the pieces of a roadmapping architecture?