Thanks for writing this post @kevin.olsen ! I am generally in favor of this move to split GPC into two separate workstreams to gain the accountability benefits you mentioned.
I also agree w/ @safder that we should reconsider how we approach operations if we plan to have more thin workstreams as a DAO. This is something I previously proposed in @kyle’s future essential intents & organization post. I see more disadvantages than advantages in having decentralized operations. Decentralization of certain things like holding power, is essential, but I don’t think we should decentralize everything w/o considering the pros and cons of doing so. If we centralize workstream operations to DAO Ops, or some other to be created workstream, a key feature needs to be the ability for workstreams to opt out of that structure if it doesn’t fit their needs.
@safder also mentions another option for solving the operational challenge posed by having more thin workstreams.
IMO, a both and approach, not one or the other, is the best way for us to evolve operations as a DAO. We need to have core teams working on hard problems and we need to continually experiment with having bounties/composable scopes of work (CSOW) to augment those teams and to solve one off problems. As @Viriya mentions here under the Brand, Design & Creative section, there are certain scenarios where a core team of contributors is very important and much more effective than taking the bounty/CSOW approach. I agree w/ @safder that the bounty/CSOW approach is full of challenges and think it will take a long time for us to perfect this approach. I believe we need to focus on streamlining operations in the thinner workstream paradigm while also running experiments in the bounty/CSOW approach so we can continuously improve at involving our community in the work we are doing.
Finally, I want to call out that one big operational pain point, that is felt by all workstreams, will not be solved by any of these proposed operational changes. Seasonal budgeting is a very involved process that any workstream has to undertake regardless of how thin or fat it is. Thinner workstreams will likely be the most negatively impacted by the budgeting process, because a higher percentage of the workstream’s contributors will have to be dedicated to the process. Hopefully the budgeting work that is already happening can address this problem.