Introducing v2 of the Steward Council & future plans

Hey all!

Thanks for putting this together, I think it’s a really great starting point. One thing I noticed that the current council only reflects a couple of workstreams (mainly FDD and DAO Ops) and misses quite a few highly active stewards. As @kyle noted some folks are also no longer working for the DAO although they may have been when the snapshot was taken.

Especially given that we’re talking about this council being in place for a relatively long period (180 days) I’d like to propose an amended selection process, based on the success we’ve seen in CSDO and other governance bodies. In fact, we could view “SC” as principally guiding strategic decisions while “CS” guides tactical ones. Take this as just one option as we continue to iterate towards the best possible stewards council.

Step 1: Workstream Nomination. Each workstream nominates (via any process they see fit, one lead for each meeting (monthly). They are required to have prepared a list of key strategy questions (e.g. fraud might ask ‘should we have an open data service that helps us streamline Sybil data analysis’; PGF might ask ‘what kinds of rounds should the program run that it isn’t thinking about and why’; GPC might ask ‘how do we ensure we’re building best with the community’). Workstreams risk slashing if they don’t come through with these questions consistently.

Step 2a Steward Nomination, Each workstream nominates at most 3 stewards to go into a pool. Each steward must be a non-active workstream member (i.e. an “independent” member). This allows us to bring in folks that can provide strong external guidance and relevant domain expertise that might not be present internally. We can also require that selected stewards meet some threshold of activity or delegation.

Step 2b: Steward Nomination. Chosen stewards go into a QV, and workstreams nominate 3 members each to vote. We can even dogfood our own quadratic voting site for this.

Step 3: Ratification. We elect that council in a forum post + snapshot vote as usual. Crucially, if at any time someone needs to step down we can simply use the previous vote rankings to determine who might take their place.

IMO this wouldn’t take very long to organize and might yield better results than relying mainly on the health cards. For context, I originally designed the health cards as a way to track total steward engagement, but didn’t necessarily intend for it to be used in this kind of election process when I first conceived of it (though I think it’s a good input). Would love any thoughts and feedback on this approach.

7 Likes