It’s exciting to see that our first proposal has gone live (and is officially out of the timelock / is open for voting today). Given some of the comments that have come up, I wanted to both speak to a distinction between projects and programs, and to briefly talk about what the user research program at Scroll might entail beyond this first project.
tl;dr: this proposal focused on research to inform a builder support strategy is just one part of a broader program that will entail many user research related projects.
Project vs. Program: Key Differences
A project is a focused, temporary effort aimed at achieving specific objectives within a defined timeline. Projects are self-contained and have a clear set of deliverables. For example, our current research project is dedicated to uncovering insights to better support builders, enabling them to thrive within the Scroll ecosystem.
On the other hand, a program encompasses a collection of related projects and activities that are coordinated to achieve broader strategic outcomes over a longer period. The program takes a holistic view, ensuring that individual projects align with overarching goals and contribute to long-term success.
ChatGPT produced a pretty useful breakdown of this distinction in more detail, which I decided to include below.
How This Applies to Scroll’s User Research
The builder support strategy proposal is a project within a much larger program of user research being undertaken by the Scroll Foundation. This program is designed to evolve continuously, exploring diverse user needs, behaviors, and pain points across regions, industries, and contexts. Each project within the program contributes to a comprehensive understanding of the ecosystem and informs our decision-making processes.
A few delegates have commented about the fact that this first project is not region specific, or have signaled that it might be good to have others partake in doing some user research in the future. These are very valid points and from the Foundation perspective, we definitely want to see region specific user research programs in the future and we very much hope that more groups (delegates or external parties) will choose to get involved in the future.
We really appreciate Daniel and RnDAO kicking off the user research program at Scroll, and the Foundation will work with them (and with anyone who chooses to propose future iterations) so that we can get a deeper understanding of builders in the space broadly, builders in the specific regions we want to prioritize, and potential users on the ground in said regions.
Future Directions for User Research at Scroll
To provide clarity and a sense of scope, here are examples of other potential user research projects that could emerge as part of Scroll’s broader program:
- Country-Specific Explorations:
- Investigating user needs and behaviors in the initial priority regions (Brazil, Kenya, Malaysia, and South Korea) or other regions that may emerge as DAO priorities over time
- Industry-Specific Studies:
- Exploring verticals like payments/DeFi, DeSci, and any others that prove of interest to our community to understand how Scroll can better serve these industries
- Beyond Web3:
- Engaging with non-Web3 users in the aforementioned countries to identify ground-level needs and pain points
- Using insights from these studies to ideate new product opportunities that can address significant challenges and serve broader populations
By pursuing these initiatives, Scroll’s user research program ensures a well-rounded understanding of both current and potential users, enabling us to design solutions that are inclusive, innovative, and impactful.
Addressing Concerns and Setting Expectations
We understand that some have expressed concerns about the scope of the current proposal and whether it addresses all potential areas of interest. It is important to emphasize that this project is not the entirety of our user research efforts but a stepping stone in a wider journey. Each project serves a purpose within the program, and together, they form a cohesive strategy to enhance our ecosystem and serve our global community.
This project, as I see it, will serve as a solid foundation for the program. It would provide a general understanding of what builders across a few ecosystems are thinking, and will provide learnings that will be relevant for other proposals we hope to see in February, March, or beyond (such as the first grant programs, local node strategies, and non-financial builder support, to name a few).
As mentioned, the Foundation will work with the RnDAO team and with any other teams that may propose other user research programs in the future to ensure that they truly exist as part of a single user research program (as opposed to having a lot of discrete and disconnected projects).
A Call to Action
As we continue to expand our user research program, we invite community members and stakeholders to share their ideas, feedback, and insights. Your contributions will help us prioritize and shape future projects, ensuring that our efforts align with the needs of our diverse user base and the broader Web3 community.
Together, we can build a robust ecosystem that empowers users and drives meaningful innovation.
ChatGPT’s explanation of projects vs programs
The difference between a project and a program lies primarily in their scope, purpose, and structure:
1. Scope
- Project: A project is a temporary, focused effort undertaken to create a unique product, service, or result. It has a defined beginning and end, specific objectives, and clear deliverables.
- Example: Developing a new software application, organizing a conference, or constructing a building.
- Program: A program is a collection of related projects and activities that are managed in a coordinated manner to achieve a broader, long-term goal or benefit.
- Example: A program to improve organizational digital transformation might include projects for software implementation, staff training, and IT infrastructure upgrades.
2. Purpose
- Project: A project focuses on delivering specific outputs or results. It addresses particular objectives within a defined time frame.
- Key Question: What are we creating or delivering?
- Program: A program focuses on achieving strategic outcomes and benefits. It aligns multiple projects to contribute to overarching goals.
- Key Question: What outcomes or value are we delivering?
3. Duration
- Project: Temporary with a fixed timeline.
- Example: Launching a marketing campaign for a product (3 months).
- Program: Ongoing or long-term until strategic objectives are achieved.
- Example: A program to enhance community health through nutrition, fitness, and mental health projects.
4. Management
- Project: Managed by a project manager who focuses on scope, budget, schedule, and deliverables.
- Program: Overseen by a program manager who coordinates multiple projects to ensure they align with the strategic goals and maximize benefits.
5. Complexity
- Project: Less complex, as it deals with a single initiative.
- Program: More complex, requiring integration and interdependency management among various projects.