# DARPA has no corporate vision It has a mission but not a vision. The distinction is different because it enables it to change over time depending on the circumstance. Contrast to google, where it has a constantly changing corporate vision. Like the control, the vision is pushed down to the level of the PM. This can enable you to have programs that may actually be working towards different visions of the future. It also empowers PMs because they don’t have to conform with some grand CEO vision. This may also help avoid internal politics because there is no competition to dominate the overarching vision. You could almost think of it as a federated vision. ([[Federation]]) In organizations [[There is a gap around program - level visions as opposed to product or operational visions]] - ie. Most organizations have visions at the whole-organization level and the product level. This gap means that it may be valuable for [[§PARPA]] to operate similarly just because it is an area in constraint space that is sparsely covered. ### Related * [[Program design is like performance debugging a vision]]