- Edited
To start off with some context: I joined the DAO at the end of December into the Community Dept. Upon joining I did find there was a lack of structure in the DAO and processes. Most projects (whether product, platform or general operations) were completed in silo groups which didn't necessarily make use of the structure of the different dept's which were already apparent. There did seem to be a culture of getting things done but less was done on the planning side or attempting to choose the right resources/skill sets to deliver on the project. Despite the somewhat less normal corporate environment I've been used to, there is no doubt that product was delivered, work was done and more processes were put in place to enable better effeciency.
- Context for the proposal, including a brief explanation of the challenges facing the DAO, and the key strategic initiatives we are currently pursuing;
For one of the few who was quite vocal for having better alignment and the need for strategic objectives, I totally agree with the need for these to ensure we are aligned with what we are aiming for in the short-term, medium-term and long-term. This will not only ensure we can pull on the right resources to deliver on the objectives but also ensures we can measure our success based on these targets. Contrary to this, our current setup encourages anyone with a good idea to run with it, try to gather people to support it and if it is delivered then it is compensated for - this did create conflict around priorities especially when most projects demanded more capacity from certain departments.
- An articulation of the roles, responsibilities and delegated decision authority for key individuals within the DAO, including Core Team, Functional Stewards, the Policy Team, and Internal Contributors;
I agree with the need to articulate roles and responsibilities (all all levels of the DAO) but not necessarily delegated decision authority (will explain after) for all members of the DAO (including Core, Functional Stewards, Policy Team and Internal Contributors). This ties in with the objectives point so the DAO can really ensure it has the appropriate skill set to deliver on the necessary objectives and can also measure and manage it's operational budget based on what it needs to deliver. For individuals, I can only speak for myself as an internal contributor. Responsibilities are important to ensure specific tasks are carried out by those who have been identified as having the relevant skillset to complete the task effeciently or with higher success - avoiding the situation where anyone has the right to try to run a project. It also allows myself to know what the DAO is asking of me, I can measure my worth based on the time, experience and success of meeting those responsbilities and expect an appropriate compensation.
On the point around delegation, I do believe there are risks around centralising decision rights to Core Team and Functional Stewards. While I agree it does help us move at pace (a small group or individual making decisions vs a decentralised approach of voting) the risks are amplified for internal contributors due to little progress or solid commitment to improve transparency from Core Team and Functional Stewards. As an example, transparency was requested around allocations across the DAO - this resulted in allocations being shared for internal contributors but no Core or Functional Stewards (maybe 1/2) were shared. While there are concerns around doxxing wallets if Core/Functional Stewards are shared, this raises concerns around different rules applying at different levels. Ultimately, I feel centralising decision rights is the way to go in our current journey to move faster however the transparency needs to be worked on more to mitigate the risks to internal contributors prior to formal agreement - we can work on this quite quickly but there is certainly a lack of trust looming at all levels (internal contributors, functional stewards AND core).
To note also, since there has been nothing formally confirming the decision rights one may argue that Core are currently assuming specific decision rights (known as status quo).
- A proposal to establish a working group dedicated to building out a decentralization roadmap for the DAO.
100% agree with this approach with establishing a working group to build out an appropriate DAO for KlimaDAO. However this is dependent on the mitigation of risks around the proposal of formalising the current centralised approach.
My overall stance is that I will go with the majority vote regardless and will continue to work on or promote changes to work towards what I believe will help the DAO succeed it's objective/mission while establishing a working environment that I would strive and enjoy. To me, none of the change requests are necessarily red flags or against my morales but certain options will require more trust which should warrant more accountability and responsibilities from those asking for it.