Restructure Documents to map Deliverables to Effects #51
+201
−175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After mulling over the three documents several times (Vision, Strategy, Roadmap) I came to the conclusion that the Vision actually read more like a Mission Statement, the first part of the Strategy read more like a Vision, and the remaining parts of the Strategy plus the Roadmap put together made both the Strategy and the Roadmap depending on how short/long term the deliverable is.
Largely speaking the Core KPIs at the top of the Strategy were all aspirational effects or desired outcomes, but very little that is actionable. In my mind, a "strategy" should be more of a how-to guide on achieving the steps laid out in our Vision. IMHO those very effects ARE the Vision largely because we have virtually no direct control over any of them. I.e., how exactly do we get more transactions on chain? That itself is the million dollar question.
So what I did is I renamed the old Vision to be a Mission Statement and then refactored the Strategy and Roadmap into a 2030 Vision based on the EFFECTS KPIs, a 2030 Strategy based on long-term deliverables, and a 2026 Roadmap based on short-term deliverables. Note that these deliverables are still not completely prescriptive, but they should map cleanly between the different categories. This gives us the flexibility to ensure funding and accountability line up with ecosystem objectives.
For example:
Vision -> Operational Resilience
Strategy -> Develop at least 1 alternate node
Roadmap -> Pragma building Amaru, Harmonic Labs building Gerolamo, Blink Labs building Dingo, etc.
Additionally, I have added tags to each of the effects listed in the Vision to allow us to cleanly map deliverables to the desired effects. To re-use this example, the desired effect for Operational Resilience is
[E-RESILIENCE]and any deliverables designed to produce that affect share the same tag. This also shows that there are some deliverables that were written down that don't necessarily support the Vision objectives, so those are left blank.This is of course just my own opinion on how things could be improved. Generally speaking I think we could also benefit from trying to identify the absolute highest priority deliverables/categories and then focusing more specifically on those, because I think it is still too broad.
Feel free to accept or disregard whatever changes you all feel is necessary. I think all of you on the product committee are doing a fine job, so it is not my intent to be overly critical. I just think it is imperative that we get this right.
For ease of viewing, here are direct links to readable versions of the files with my changes:
Mission
2030 Vision
2030 Strategy
2026 Roadmap