General Overview
“We can artificially create supply, but we can’t artificially create demand.”
Q4 has been full of learnings. Understanding demand better, has been the most impactful one.
The centralized offering enabled quick seed node deployment and direct user engagement, providing insights into system interactions. These interactions challenged many of our initial assumptions:
- Compute and content retrieval are commodies with consistent demand - RSN is not offering a comodity.
- The true value lies in the service itself and what it allows the users to achieve.
- User experience gaps posed significant barriers to adoption, particularly for organizations.
We found that Continuous Integration was a major area of interest, prompting us to expand our offering to include it.
This exposed the new hurdles such as identity management and code review.
Users are expecting higher levels of abstraction and service - a refined experience that justifies the cost, rather than merely hosting technology - which means we still have work to do to meet these expectations.
As we learned that developer tooling is not comparable to commodity services like compute and content retrieval, we further understood that demand greatly depends on the product.
High product expectations and effective alternatives highlight the need for more differentiated value to drive adoption.
Increasing adoption and offering the service only make sense when we can adapt the service to the needs and expectations we learn about.
We are taking the learning into the new Radworks Product Org.
Quarterly Objectives
-
Launch centralized service for a larger number of community members and gather further feedback
[DONE]
We successfully launched the centralized service to more community members, providing valuable insights into user needs and pain points. -
Measure and collect performance and adoption metrics
[NOT FULLY ACHIEVED]
Low adoption limited metrics collection, reflecting strong alternatives and current gaps, though qualitative feedback was invaluable. -
Develop missing components based on user feedback
[DONE]
We expanded our offering to include third-party CI, addressing one of the key gaps identified by users. More gaps were identified (User management, Code Review flow etc.) -
Refine centralized offering in alignment with user feedback
[DONE]
The CI integration was a step forward, but there are still gaps to address, including user management and workflow optimizations. -
Publicly release revised design of the centralized offering & transition plan
[POSTPONED]
Delayed to prioritize generating demand first. -
Prepare for gradual decentralization in Q1 by developing & deploying a testnet
[POSTPONED]
Delayed to prioritize generating demand first.
Budget
Avoiding hiring maximized learning and ensured efficient resource use. As development moves to the newly created Radworks Product Org, we are now looking at returning the remaining RAD from the RSN Org to the DAO.