Summary/Abstract - This proposal, the final in the POrtfolio of bets strategy, formalizes framework, sizing, and feature lists on the portfolio of bets for the rest of the quarter.
Abtsract Motivation
If the product goals set up mental models, frameworks for collaboration, and an overarching portfolio of bets, this proposal explains the details of bets with timelines of now, next, and later.
For simplicity's sake, framing initiatives or features as one of three things:
Rocks
- Rocks are big and heavy, they form the basis of our portfolio and will get the priority focus for product and engineering until we have them placed.
###Pebbles
2. Pebbles are easier to manage but still slippery. Getting them right right requires a few loops. However! the rigor with better long form and mini specs we introduced in the past two months is encouraging. By speccing, spiking, and exploring within the discovery and definition phases, it will be easier placing the pebbles and sand around the rocks.
Sand
- Sand are all the little tasks that donât quite fit in a mini spec but are just quality of life, polish, and simple additions that make experiences better for users and developers.
Now we have a formula: {the specs give the what and why[ name & business case]} + {the size of the work [rock/pebble/sand],} + {the when [now next later]} + {statuses [draft, discovery, definition, hand off/execution]} = Shipping.
SpecificationâNorthstars
Marching towards our north stars means planning our roadmap around those three types of work / tagging them as now, next, and later. Adjusting in real time will happen every Monday, as usual. On this spreadsheet and evenutally on our board in Github.
- Get the API to market and get customers paying (25 best case | 3-5 base | 0 failure)
- Weekly active transactions goes to 300
- Monetizeable Volume goes above 500K
- Trading volume gets to 750k.
- Cumulative transactions goes up ( 70k best 30k base 25k failure)
Critical note: A roadmap should be considered a âpoint in timeâ artifact instead of a contract for the quarter. Things will and do change. This will be updated with living retros as touchpoints along the way. The product workstream lead will aim for biweekly reporting, around office hours.
Specification â Portfolio of bets
We have bandwidth for around one big rocks running in parallel with a few pebbles, per month. We donât want to fracture our efforts on shiny sand that take up bandwidth without results. Let's try just 20 things, with most already rolling and see how we improve at allocating human capital towards our bets.
Weâve color coded the spreadsheet with green [in progress/complete], orange [still speccing], red [no consensus] features inside the roadmap sheet note that 4 are in progress/complete and 10 are speccing already. Product's goal is to have bets articulated and specced to high quality by EOQ as a base case, and shipped to production as a growth case.
API bets
- Get API into market & iterate
- Get API docs good
- Iterate APi with customers
- Infrastruucture Optimization
- Dogfood API into /web
Interface bets
- Portals (swaps)
- Portals (defi)
- Kill splash screen
- FOX Rewards Spec then Pilot
- CANNY Feature with hella upvotes
- Missions
- WC v2
- Thorchain
- Cosmos & Osmosis re-evaluation
- Monetize Defi
- Donations
-stETH
Obligations bets
- Arkeo (POC & claim page)
- MM Snaps
- Frontend and node maintenance
Benefits -
- Ships the portfolio
- Aligns workstreams
- Allows us to iterate and learn how to improve process and bandwith
- reduces the product workstyream renewal wall of text
- gives us goals to refine and report on
Drawbacks -
- Does not tie into revenue well enough (we're working on it!)
- Is a living document
- Not all of these will finish shipping by end of September
Vote -
For - Formalizes the community is âforâ the details outlined in this proposal including the high level POB framework and the items herein. Also acknowledges the flexible nature of dynamic market conditions, that this is not a binding contract, the quarter is already started, and the need for alignment above all
For with changes â Acknowledges the roadmap and points out constructive solutions with concrete suggestions. Chatgpt subposting will be ignored.
Against - Formalizes the community is âagainstâ the proposal.
