HAPPY OHMIVERSARY
Quick note: Have been pretty vocal during the internal crafting of this RFC amongst Strategos + Core.
My position: Community Stratego
First of all, I'd like to preface things by saying that I'm happy we've managed to push out the first actionable step towards steering Olympus back on track. I've only been in the Stratego role for a little under a month now and one of the main reasons why I was moved into this role is that I took my frustrations, being;
. the constant flux-state that the DAO had appeared to be in.
. the lack of high-lvl vision, cohesive branding, and narrative maintenance
. obvious accountability/responsibility disconnect at the top of the food chain (core<>stratego misalignment)
and started asking questions, plugging holes, and proposing solutions for problems that appeared to be circular.
One thing I realized after being thrust into the role, is how -EV things really were at a high-lvl. Core had unintentionally consolidated a lot of the protocols power and the day-2-day executors - Strategos - who essentially run all departments, had very little power
. Core has pOHM, Strategos don't have vested packages.
. Core controlled most MS infra, Strategos didn't.
What's worse, this power actually translates into accountability & responsibilities, or the lack thereof. This has been a key misalignment at a high-lvl and the flow-on effect throughout the entire DAO has attributed to a lot of the execution issues that the Community end up sensing -> which translates into uncertainty -> people lose conviction in the vision -> ensue the last 2-3 months.
For a protocol that minimizes arbitrary decisions at a mechanism level, it was quite ironic to see these human coordination failures firsthand, yet sad to see my inkling reveal a truth that no one quite knew how to deal with.
This might appear to be highly critical but I think it's also worth noting how much transformation Olympus has undergone (positive transformation). Accolades and achievements are as follows - Olympus has only been around for a year (:
- 0 -> 3.3b -> ~ 400m Treasury
- ~ 80,000 Holders
- Forked 100 + times
- 50-75 part-time/full-time contributors
- Sprawling Econohmy (moat)
Let me now outline some things I both like/dislike about this RFC:
LIKES:
- Clear and concise OKRs that are realistic and can be used to craft effective budgets for departments & WGs.
- Assistance in the case of any legal issues that may arise.
- Council roles have highly specific responsibilities
DISLIKES:
Some council member responsibilites are too broad and this will likely lead to execution failures
Echoing FoxMaison thoughts, i don't feel like we have anyone on this council who will;
Maintain brand across Olympus products
Enhance public image and reputation
Lead DAO values and culture
Lack of clarity around Zeus' responsibilites on the council.
Amongst the roles & responsibilites, i don't see anything honing in on and prioritising transparency.
I'll leave things there - overall, I'm leaning towards two separate proposals as some people have been suggesting. On the other hand, the proposed members are highly capable and likely the best people for these roles (bar a few responsibilities). Need to see more discussion before voting on this RFC