# §Program Design * [[What are the goals of the program design process?]]]==needs work== * [[Program design is like creating the lego instruction book]] * [[Program design could be thought of as creating a causal graph of blockers and hypotheses about how to mitigate those blockers]] * [[The crux question of program design is when to commit]]==needs work== ### Hypotheses * [[The first step of roadmapping is frontier mapping]] * [[A roadmapping framework may make the ARPA model more effective]] * [[Talking to experts can expose bad equilibria, the moves necessary to get out of them, and considerations for doing them like cost constraints]] * [[You can create a framework for talking to people that makes it easier to generate a roadmap]] * [[You could build tools to make program design more efficacious]] ### What are roadmaps * [[What are the properties of maps?]] * [[Roadmaps have two pieces - the map and the path]] * [[Roadmaps are a theoretical construct to escape inadequate equilibria]] * [[List of Roadmapping Examples]] * [[Most roadmaps suck]] * [[Most roadmaps are not execution oriented]] ### Why Roadmapping * [[Instead of planning not working as well as people in the past thought as a society we’ve become worse at technological planning]] * [[Roadmapping could be thought of as backwards-chaining together a series of conception-only heuretics]] * [[Roadmaps can enable faster progress than blind exploration]] * [[Technological roadmapping can give an idea of where technological evolution can go and how to get there]] * [[A roadmapping framework may make the ARPA model more effective]] * [[Program design is like performance debugging a vision]] And of course we need to look at the possibility that this is all BS * [[The roadmapping process is heavily context dependent and there may not be a generalized roadmapping process at all]] ### Building better roadmaps * [[Design for roadmapping system]] * [[Person targeted questions for roadmapping]] * [[What are the eight steps of Wigmore analysis translated to science?]] * [[Technical Planning Principles]] * [[Good roadmaps work backwards from a goal]] * [[Good Simulations could be the ‘why now’ of roadmapping tools]] ### Glossary * [[Areas programs and projects are distinct but often confused]] * Bottlenecks -> Roadmap -> Execution * Language * Binding Constraints * Affordances * Dependencies * Project * Program * Area * Causal graph of blockers * Capabilities * Steps * Frontier Mapping * Finding the right people * Comparing different paths * Goal setting * Finding serious contexts of use * Different institutional ‘moves’ * Respectability cascades * Spending curves ### References * [[And Suddenly the Inventor Appeared]] * [[Wigmore Guide - Paper]] * [[vincentTradeoffCentralConcept2017]] * [[zwickyNewMethodsThought1967]] <!-- #index --> [Web URL for this note](http://notes.benjaminreinhardt.com/§Program+Design) [Comment on this note](http://via.hypothes.is/http://notes.benjaminreinhardt.com/§Program+Design)