Strategic Recommendations
Based on the discussion from the Project Steering Committee meeting, here are the October strategic recommendations for each key project. Note these are recommendations, if a project feels as though these are unfounded or off-base, let’s discuss why and where to go instead. If you have questions or want further clarification, ask and the Insights team will provide it.
Codex
- Revamp milestones to focus on user acquisition and shipping usable parts of the software
- CAL (Corey, Afri, Leonard) to collaborate with Jacek and Codex team on reframing Codex, focusing on understanding users and use cases
- Identify timeline for development of roadmap alternative (Jarrad’s suggestion as backup)
- Deliver clear timeline and definition of plausible deniability and censorship resistant features
- Identify current software’s performance boundaries (“persistence” and “altruistic” modes)
- Start “Mainnet Release Agreement” similar to what Nomos has begun.
Nomos
- Allocate resources to wallet development (hire, not current resources), critical for testnet
- Leonard to provide engineering manager support to Alvaro and Daniel
- Finalize “Mainnet Release Agreement”
Status L2
- Define clear purpose and justification for partnership development effort
- Set tangible metrics and goals for testnet to guide development
- drive clarity on intent via milestone mapping, user identification, testnet definition
Status
- Volo to provide strategic recommendation by mid-November
- Align Leonard/Volo and Jarrad/Volo strategy work
Keycard
- Clarify purpose and direction (GTM) - include Grace
- milestone mapping, website requirements and resourcing
Nimbus
- Improve visibility
- Identify potential target revenue streams to align “out-of-business-as-usual” efforts
- Understand current plans / progress of Nimbus fleet management (Jakub and Kaushal). Ensure strategic alignment with Devlp’s purpose and mode of operation (e.g. Jacek’s previous suggestions).
Waku
- Proposal for js-waku client collaboration, needs to include justification.
- Continue prioritization of Status as client for nwaku/go-waku.
General
- Ensure high-fidelity milestones with clear measurements for board meeting in 45 days
- Use Insights for primary communication
The key themes are:
- Clarifying purpose and validating with target users
- Focusing milestones and development on delivering user value quickly
- Improving communication and alignment
- Defining clear success criteria and metrics
Implementing these recommendations over the next 45 days should help get the projects on track strategically and set them up for a successful board review. The PSC should closely monitor progress and provide guidance to project leads to ensure the recommendations are put into action effectively.