More formally, I propose that as a DAO, we first need to clarify the following aspects before we can implement and ratify a resource allocation framework:
-
Product vision – The product vision defines an aspirational end state of a product. It defines what the product will achieve and the value propositions for end users and serves as an anchor point for how we assess the funding of new features, functionality, and products. We should look to establish a product vision based on an understanding of end-user needs and the market landscape. While ideally, we want to set a single canonical product vision, there may also be several product visions we may want to consider, explore or attempt to validate. Nonetheless, they should be initially defined first as a starting point. A product vision establishes the necessary clarity around Safe DAO’s motivations (the ‘WHY’) around tactical goals and surrounding strategy.
-
Product goals – These are specific tactical objectives that help achieve Safe DAO’s product vision. Goals should acknowledge the constraints of our available resources and the existing position/state of Safe DAO. With each product vision, there will be its own respective product goals that are nested under each. Product goals allow us to understand what we need to accomplish immediately (the ‘WHAT’). While typically product goals generally are coupled with a strategy on how to execute them, we want to enable the community to participate in bottoms-up ideation on the ‘HOW’ via OBRA. We expect many of OBRA’s strategy proposals to revolve around our established defined product goals.
-
Product metrics – Product metrics are data points that allow us to establish a picture of the current, past, and future state of Safe DAO’s progress toward goals and its product vision. Metrics aim to guide and inform, not necessarily be optimized at all times. A single metric alone will not provide the full state of reality, nor will a full set of metrics achieve that. Metrics should always be understood via the lens of qualitative assessment. Our initiative proposals should be measured against product metrics as much as possible.
We want to ensure a resource allocation framework supports the execution of the community’s outcomes, goals, and direction as opposed to working against it.