X1 Pod Sense-Making next steps - and its importance

tl-dr:
I recommend that gov-naut produce a case study of a DAO’s journey to adopting a pod structure. This would serve as the concluding task for the X1 Pod Sense-Making workstream. Achieving this is a critical priority. In fact, the more Sonar Labs prioritizes support for this work, the sooner we can move to open beta without it being a disaster.

Longer version:
The most recent pod sense-making session between gov-naut and SL highlighted that SL is undertaking a lot of socialware work with DAOs to help them make the best use of pods. This is important work, yet difficult to scale. Scaling this work requires 3 critical elements:

  1. Attracting enough capable people to provide the supply of on-boarding support sufficient to meet demand
  2. Ensuring those people have sufficient knowledge and credibility to meet that demand in a way acceptable to DAO interested in adopting pod structures
  3. Managing the adoption lifecycle for the DAO

In private beta, SL can deliver on all 3 of these in a straightforward way by limiting the funnel of demand entry so it is manageable with their internal resources and whatever self-service resources are in place. By definition, this approach cannot be used in a public beta that accommodates all market demand without queuing. There appears to be consensus that SL could not accommodate a public beta launch today without significantly degrading the on-boarding experience, and that demand for the product greatly exceeds what can be accommodated with current resources (so the backlong of demand is growing). Thus, I see a tradeoff of 3 elements for Orca Protocol regarding public beta:

  1. Improvement of the product and the self-serve resources to reduce the burden imposed by adopting DAOs
  2. Additional skilled resources to support DAOs in adopting pod structures
  3. Delay in the start of public beta

In theory, either 1 or 2 alone could reduce 3, but given socialware is by definition not easily codified, it does not seem feasible that 1 by itself is possible within any reasonable time frame. Thus, the faster we can add skilled resources to help DAOs adopt pod structures, the sooner we can get to public beta.

While SL can likely increase its capacity to some degree via hiring and freeing up internal resources as they complete other project work, there are 2 issues with doing so.

  • First, hiring staff take a lot of time and effort to ensure they are capable and get the knowledge they need to be effective in this work. This may in fact lead to an increased delay in how long it takes to get to public beta.
  • Second, doing so would further centralize Orca Protocol, making it more difficult to decentralize in the future and directly contradicting one of SL’s stated goals for the long-term evolution of Orca Protocol.

Thus, it would be ideal if the Orcanauts could contribute more to this work in order to reduce the delay until public beta. In fact, the -naut structures are well-suited to meet the scaling needs initially outlined:

  • nav-naut has already created a laudable approach to identifying potential members and helping them on-board successfully
  • All the nauts have aims and domains related to increasing the knowledge and credibility of the Orcanauts to do this work
  • gov-naut has aims and domains to support DAOs in their adoption lifecycle

The primary constraint at this point for increasing Orcanaut support of DAO onboarding is lack of access to information to increase knowledge, and lack of access to participation to increase credibility. Undertaking the case study effort as part of this work stream will clarify where the gaps are in knowledge, and producing this will bolster the credibility of the Orcanauts in being able to work with DAOs to adopt pod structures.

This issue cannot be address without Sonar Labs explicitly making this a priority. Thus the reason for statement in the tl;dr that the more Sonar Labs prioritizes support for this work, the sooner we can move to open beta without it being a disaster. While this work would impose some burden on SL, it would only be a fraction of the burden that internal hiring would pose, as the community could then take on much of the work to attract more people and train them on how to support DAOs in on-boarding pod structures.

I view this work as a critical test of the community’s commitment to decentralization and enabling DAOs to achieve their full potential, and look forward to working with everyone in Orca Protocol to achieving this vision.

3 Likes