I want to share my thoughts on this topic. Thank you @lkngtn for starting this conversation. It was much needed. I donāt want to go over the high-level discussions about the program (that are important too). I want to point out the things that I donāt see are working right now.
We were naive about the initial expectations of the program. Independent teams that could take care of the project, if something would happen to the others. Also, teams that would ease the workload from A1. There is a lot of work. We wanted all these things from day one. These expectations have not been met yet. Because the reality is that building a team takes time.
To put concrete examples:
- OE apps. We have been waiting for these apps on mainnet for quite some time (Iām excited to learn they will reach mainnet soon). Yet, we approved their last proposal without addressing openly this issue before.
- Fundraising. We have been waiting for this also. I understand it is hard and it is coming. A1 is involved in important part of the work. The AB team has no UX designer/dev yet. It seems A1 advised AB not to hire a UX dev/designer. I donāt understand the reasoning here. This is hard and key work. Also, the documentation is not in good shape
- Discovery platform. Same as above. A1 will probably have to be very involved as well. It is quite urgent, at least the initial PoC. Has AB the manpower to fully take it? How long would it take for us to expect this?
Iām not talking about collaboration here. We all have to collaborate. This is for sure. But in the context of Flock teams, I donāt understand collaboration as having to be directly involved. What is the point of the program then? The issues above are solvable but we need to address them and this is a good start. Iām not pointing them out to criticize but to show that our expectations were naive and donāt match the reality. Yet, it is a very expensive program. We are giving huge amounts of money, ANT (vested) incentives included, right from the start.
The Aragon project has a concrete purpose. Build the best governance tools for blockchain-native and community-driven organizations to flourish. You can say that the purpose is subjective. But, applying common sense can help decide if something is aligned with that purpose or not. The main things Autark (roadmap: I01 to I05 and I08) and AB (roadmap: I01 to I03) are building are very aligned with the purpose. They take hard work and need the right people to work on them. Teams should take the time to mature, build a shipping cadence, and then expand from there. But, expand always according to the projectās purpose and current needs. This applies as well for the roles in the different teams. Does the project need 4 community managers, for example? Does it need 4 blogs? We are not just funding a team. We are funding teams that āmatchā the project.
The ecosystem needs a lot of things but we canāt take everything into the projectās wings. We are pre product-market-fit. Teams need fewer distractions and focus. It has been a process for us (A1) as well.
When we launched Flock, we knew it will need a lot of trial and error before getting it right. None of us have done this before. Clear feedback and performance review processes are key for a program this new. I donāt see them established yet. But, we are already approving second proposals by the new teams.
Also, Iām noticing we need more concrete rules on the proposals. What are they? Should they be the teamsā wishlist? Should we require the subjects listed on those proposals to be connected with the current priorities of the project? I would say, yes, please! The AA team can help with this and it should be one of their priorities. I donāt consider this centralization. I know you are just 2 people.
I love the say from Theodore Roosevelt that is applicable here. āKeep your eyes on the stars, and your feet on the groundā Yes, we need to dream, be ambitious, have a shared vision. But, without forgetting to keep reality in check.