[SCP-195] - Addition of KPIs (success metrics) as a requirement of features, campaigns, and programs

Summary This proposal presents a standard for KPIs and success metrics for DAO products and initiatives.

Abstract This proposal explicitly presents the introduction of requirements in success/failure metrics for features, campaigns, and programs initialized by the DAO. This proposal is in the spirit of Agile development, allowing Workstreams to make data-based decisions around success metrics related to features.

Should this proposal pass, it will take effect immediately, and apply to all new features, campaigns, and programs the DAO passes after this proposal, as well as giving permission to Workstream Leaders to apply the same success metrics to currently active features, campaigns, and programs.

This proposal does not define specific success metrics but instead proposes that each new governance proposal based around a new feature, campaign, or program come with defined success metrics to be defined, debated, and set.

Future proposals and ideation posts presented on features, campaigns, or programs not explicitly outlined in Workstream proposals without success metrics will not be implemented by the DAO as the governance requirements (set forth here) will not be met.

Current initiatives without success metrics are subject to newly required metrics at Workstream Leader’s discretion (if they’re already not clear).

Motivation All resources and programs that create impact on the runway should be eligible for modification, maintenance considerations, optimizations, and deprecation. Changes should be objective, derived from analytics and performance metrics.

This proposal seeks to formalize data-based decisions in resourcing for DAO engagements.

New features like og.shapeshift.com have been launched without any success metrics, but with resourcing allocated. Our team is considering a future of building AI agents services alongside the app which will cost lots of time, effort, focus, and thus limited DAO financial resources. Letting features and or programs go on without any ability to reconsider, update, or change course will lead to unnecessary spending of increasingly vital resources as we navigate Market uncertainty, product-market-fit, and our monthly spend to keep the lights on.

Specification KPIs for new proposals While the specifications of each KPI will be circumstantial to the proposal being presented, The addition of a section labeled KPIs will now be required to be added to all eligible new proposals in ShapeShift DAO governance.

The new required KPI section should be included in the section labeled ‘Specification.’ This section should present the success metrics tailored to the specification of the proposal being presented.

The description of the Specification section of the SCP template will be updated to read as follows: " Specification

Describe the “meat & potatoes” of the proposal. Go into deep detail around the changes that will happen both on a technical and social level. Be specific and avoid ambiguity. A sub-section titled KPIs should be included in this section presenting success metrics of the proposal in question. The more detail, the better."

Resourcing The only additional resourcing required after the passing of this proposal will be on Workstream Leaders to collaborate and create new KPIs on active features, programs, relationships, and services that have outcomes affecting DAO revenue. The eligibility of current services for KPIs will be entrusted to current Workstream Leaders, but should always be based on analytics and strategies enacted based on data.

Budget There is no cost associated with the passing of this proposal.

The rest of this proposal is over the Snapshot character limit but can be read in full in the Forum post associated with this proposal.