Hi @mikemetagov, thanks for making time to review these preliminary findings.
For those short on time, I’ve put together an AI-powered reader that lets you query the preliminary findings directly → https://retrospective-frontend.vercel.app
My thoughts:
On a Masterplan Group
While I appreciate the intent behind a 12-month Masterplan group, the environment ENS operates in may not complement this approach. As noted elsewhere, the current coordination structures impose unwarranted overhead relative to ENS’s importance in the market environment.
Adding a standing design body on top risks compounding the very overhead the retrospective aims to eliminate, rather than reducing it.
A stronger case may be for a time-boxed body with a narrow mandate — not an elongated design process, but a sprint focused on translating the retrospective’s findings into actionable frameworks before any structural decisions are locked in.
Such a body would not be a standing committee but a permanent advisory council, convened to provide ongoing formal input to whatever accountability structure the DAO adopts — informing decisions without making them.
Transparency Infrastructure
The DAO already has templates for its governance process (Governance Process | ENS Docs). Although seldom surfaced, these remain valid documents that developers can use to understand and navigate the working environment.
With respect to establishing a Governance Repository and Transparency, several frameworks already exist and are in development (ENS Pulse, the DAO Newsletter).
Flattening the existing Working Group structure and allowing a community-informed Board to serve as the accountability layer appears more efficient than establishing a myriad of funding and initiative pathways.
On Delegate Accountability
The reality is that the ENS protocol requires technical expertise to exercise judgment on both the consideration and execution of proposals. The fact that there are (give or take) 10 delegates capable of putting forward executable proposals may be a feature, not a bug.
Regarding a delegate health dashboard, tools such as Anticapture - ENS DAO may already fulfill that role and are more focused on protocol security, which, by extension, reflects delegate health.
Notwithstanding, educating tokenholders on ENS is not implicitly part of the culture. The assumption is that most are committed to doing their own research (especially with the advent of AI on the ENS documentation page itself), and thus delegates should adopt a caveat emptor approach when engaging with ENS.
On Treasury Oversight
This is not a slight on any current, future, or prior steward; rather, the reality is that real-world companies typically assign this responsibility to trained professionals (i.e., FP&A teams).
Managing a million-dollar multisig is a considerable responsibility and creates liability for the unassuming—both in terms of financial risk and decision-making under uncertainty. I speak from experience.
I am not optimistic about creating spend-to-outcome pilots and delegating them to untrained individuals, especially in the current market environment. I feel more comfortable allowing professional teams to manage and administer budget allocation.
Moreover, the DAO has already contracted two teams to oversee its treasury and endowment; any structure that replaces the current one would benefit from borrowing established best practices.
Graduated Sanctions
Admittedly, I am scant on any opinion in this matter. I think a graduated sanctions framework is hopeful, but will be hard to enforce in reality.
Again, the real-world parallel is a separate human resources or compliance department, whose sole organizational responsibility is to oversee such matters.
Due to the nature of distributed work, I don’t see the urgency in establishing such a group, and I believe any financial or organizational discipline/responsibility can be managed by a narrower body or team.
Conclusion
Regardless of my stance, I’m hopeful that the retrospective will deliver a cohesive framework that can then be delegated to a team for execution.
Originally, I argued that the @Meta-Gov_Stewards should own and execute this, but with the potential winding down of Working Groups—or at the very least, their restructuring—the open question is how these findings will be actioned and who will be responsible for doing so.