Introduction:

Cartesi organized its first-ever Experiment Week, which brings together grantees and community members in a collaborative exploration of Cartesi technology. Over the span of a week-long online hackathon, participants collectively generated 17 innovative project ideas, marking a significant milestone for the Cartesi community.

Approach

Following the conclusion of Cartesi Experiment Week, UXBoost conducted mixed-methods research to gather participant feedback. We use mixed method approach in this research.

1. Post-hackathon survey: Received a total of 41 responses, with 40 responses usable.

2. Semi structured interview: Interviewed 11 core developers of each project, 2 participants are from the same project.

Key research objectives

To collect feedback about the format and organization of Cartesi Experiment Week.Understand the motivation and overall experience of the hackers.Understand learning experience as a hacker, documentation usage, and challenges.Understand the building experience of the hackers, including their approach and challenges.‍

“How Might We”

Drawing from the rich feedback gathered from the research, we formulate 3 “How Might We” statements to inspire improvement. These statements offer a structured approach to reframing challenges uncovered during user research into opportunities for innovation.

1. How might we foster a prototyping culture that encourages participation without inducing stress?

2. How might we support hackers to accomplish their ideas?

3. How might we expand and utilize the hackathon outcome effectively?

How might we foster a prototyping culture that encourages participation without inducing stress?

Many projects want to encourage more case studies/products built on the technology, but how do we encourage the contributors to explore and experiment without feeling obliged? There are a few key considerations when you organize your hackathon:

1. Organize experiment week biannually: To prevent overwhelming grantees and community members, consider hosting Experiment Week twice a year with advanced announcements.

2. Flexible submission schedule: While the standard duration for online hackathons is one week, implementing a more flexible submission timeline (e.g., 2–4 weeks) can enhance participation rates.

3. Partnerships and collaborations: Form partnerships or collaborations with other projects/entities to broaden the event’s scope and offerings, fostering a more inclusive environment.

4. Dedicated communication channel: Establish a dedicated channel to announce event-related information, ensuring clarity and accessibility for all participants.

5. Clear team formation guidelines: Provide clear guidelines for team formation while encouraging cross-team collaboration to cultivate greater creativity and cooperation among participants.

How might we support hackers to accomplish their ideas?

During the event, participants experiment with different areas of technology that they may or may not be familiar with. Often, there will be discussions or questions raised when they build. Similar to any other hackathon setting, a dedicated support team will be handy to offer necessary support during the event period.

1. Establishing a Dedicated Support Team: Throughout Experiment Week, ensure the availability of a dedicated support team. Informing participants of this resource encourages them to seek assistance without feeling burdensome to others, thereby boosting their confidence.

2. Document area of improvement: Additionally, the support team should diligently document inquiries, particularly those related to technological improvements and materials, for future reference and enhancement.

How might we expand and utilize the hackathon outcome effectively?

Reflecting on the hackathon outcomes, participants recognize the value of their projects for other developers, whether as examples or demonstrations of various features, concepts, or frameworks. The question is, how can we facilitate the refinement of the ideas?

1. Harnessing Project Potential: To maximize impact, encourage participants to refine their proof of concept for sharing within the community. This could take the form of learning materials or even SDKs.

2. Showcase the projects: Showcase all the projects on a dedicated site for easier access. This showcase would not only demonstrate appreciation for the project team’s hard work during events but also illustrate the various possibilities and use cases for Cartesi.

3. Continued Support for Project Development: Provide support and resources for further development in alignment with participants’ needs, ensuring ongoing project evolution and community engagement.