VDP-137: Hiring a Chief Scientific Officer (CSO) for VitaDAO

Proposals
21

The builder squad has made amazing progress. Just look Matrix sat around for almost 2 years under the author of this proposal (there is only ONE author of this proposal). Then the new builder squad launched it within weeks, negotiated IP agreements, CRO contracts, and we are about to get our first dataset. Let that sink in. The builder squad should be deciding who to hire and involved in the decision making process.

9 Likes
22

For the past two years, I have been seeing the same picture over and over again – attempts to centralize a thing that’s supposed to be decentralized, autonomous, open. VitaDAO has become DeSci’s Golden Child and at the same time its biggest disappointment (for me) – because I don’t see how it’s different from a VC fund now if it surely operates as one. We already have the SAB, investors (a.k.a. “strategic partners”), Big Pharma liaisons. The Big Boys’ Club. We keep recreating obsolete forms when there’s a chance to build a new world. Why limit ourselves to a CSO? We might as well appoint a CEO next and just call it quits on the whole “DAO” nonsense. I guess some people are just not ready for the future. And they clearly don’t belong there.

4 Likes
23

Agree with most comments here that we probably shouldnt have this today, and should rather build a more decentralized structure of strongly empowered scientific teams that advance specific projects, on a project by project basis. The power lies in the decentralization of having multiple research efforts vs one CSO overlooking all of them in my view.

8 Likes
24

After reading all the comments here and attending the last lwg meeting, I agree with some of the viewpoints made from both sides and that the builder squad has made great progress.

However, I still disagree with the proposal currently.
Recommendations if the need for this position arises in the future and if the budget can support the agreed upon salary:

  • Have the proposal include the job description, revamp the job title to reflect the job tasks and include hire&termination details that the community debates and votes on.
  • In continuing to uphold the decentralized principles of keeping things autonomous and transparent, I think it can be learned from this situation: all authors of a proposal have to agree upon the proposal before it is posted or can choose to remove themselves before it is posted if they do not support it.
5 Likes