# The Road to ETHD 2024

## Instructions for Participating in Topic TCR (RG Members Only))

Hello Raiders! You can now claim voting points proportional to your DAO member shares and participate in the `Road to ETHD 2024` signaling session. **Please cast your vote by EOD Wednesday**, as the session will close before the Thursday Raider Roundtable meeting so we can review the results.

1. [Navigate to this link to find the signal vote.](https://signal.daohaus.fun/0x64/0xf02fd4286917270cb94fbc13a0f4e1ed76f7e986#/0x64/0xf02fd4286917270cb94fbc13a0f4e1ed76f7e986) Click on the `Road to ETH Denver 2024` TCR
2. Claim your voting points. 1 RG member share = 1 point.
3. Browse the topic cards and distribute your votes according to what you think the guild should prioritize.
When you are finished distributing your points, click the `Update Stake` button at the bottom to save your changes.
4. If you want to add your own topic (and you are encouraged to!) click the button and fill out the form.
5. If you want to revise your vote to a single topic, click the `Release` button. To reset all of your votes, click the `Release All` button at the bottom.

---
---

## Session 2 Outline

- **Challenges with DAO Decisions**:
- DAOs can be chaotic.
- Ideas often only get halfway executed.
- Suggestion to delegate responsibilities to teams for better organization.
- **ETH Denver Experience**:
- Last year's experience lacked organization.
- Treasury funds are underutilized.
- Goal: Present a more organized outline at the next meeting.
- **Hackathon Perspective**:
- Last year's hackathon was last-minute and lacked organization.
- Suggestion for an internal hackathon manager.
- Form teams in advance for better preparation.
- Consider stipends from the Treasury for hackathon members.
- Importance of well-organized teams for better chances of winning.
- Opportunities arise even for teams that don't win.
- Need for RaidGuild support and coordination.
- **Value Recognition**:
- Need consensus on how to evaluate and recognize the value of individual categories.
- Importance of understanding the highest impact areas.
- Concern about mismatch of skill set to tasks.
- Need for a vetting mechanism to match skills to tasks.
- Past experiences had enthusiastic members but lacked execution due to skill mismatch.
- **Budget Considerations**:
- All activities could fall under a marketing budget.
- Suggestion: RaidGuild should consider spending up to 20% of the treasury on marketing initiatives.
- Unclear consensus on budget allocation.
- Need to account for other marketing efforts throughout the year.
- Importance of compensating members for high-value initiatives.
- Need to determine available budget before encouraging proposal submissions.
- **Responsibility**:
- Concerns about selecting the right skill set for each initiative.
- Potential for a point person responsible for their budget.
- **Money Allocation**:
- Deciding budgets for initiatives.
- Question of who decides the budget amounts.
- **Hackathon Coordination**:
- Importance of having a lead or coordinator.
- Need for a mechanism to ensure qualified individuals take on responsibilities.
- **Prioritizing Tasks**:
- Importance of consensus on priorities.
- Need to decide on high-value initiatives first.
- **Process Proposal**:
- Treat the task allocation like an RFP process.
- Use signaling sessions to rank tasks.
- Invite members to submit proposals for prioritized tasks.
- Use a vetting mechanism on the front end to avoid awkward situations later.
- Propose a light proposal template for ease of submission.
- **High-Level Strategy**:
- Need for a broader conversation on marketing strategy.
- Consideration of whether the strategy needs to be decided before diving into tasks.
- **Sales Funnel Perspective**:
- RaidGuild operates more like a high-touch sales funnel.
- Importance of meeting and explaining RaidGuild to potential clients.
- Potential misalignment with generic marketing strategies.
- **Dashboard for Metrics**:
- Desire for a dashboard to track metrics like unique page visits and conversion rates.
- EC Wireless mentioned integrating site analytics.
- Importance of understanding the entire sales funnel.
- **Marketing Concerns**:
- Fear of allocating resources to non-impactful areas.
- Desire to evaluate the effectiveness of marketing strategies.

### Process

- **Process Proposal**:
- Add marketing evaluation to the list of tasks.
- Use a TCR signal vote to prioritize tasks.
- Each member receives an equal allocation of voting tokens.
- Members can allocate their tokens to the tasks they prioritize.
- After signal vote, a lightweight proposal template is used to define scope, problem, and approach.
- Proposals are evaluated and commented on by members.
- Economic considerations need to be addressed in the following weeks.
- **Signal Vote Details**:
- Tasks are put up for a signal vote without a well-defined scope or budget.
- After the vote, tasks with clear signals are further defined.
- Tasks without signals are disregarded.
- **Proposal Submission**:
- Interested members fill out a lightweight proposal template.
- Proposals include goals, strategy, team size, and budget.
- Multiple proposals can be submitted for the same topic.
- Proposals are evaluated, possibly through emoji voting or other simple mechanisms.
- Competition is encouraged, but collaboration on proposals is also possible.

### Budgeting

- **General Budget Considerations**:
- The group discussed the challenge of determining a budget for the marketing initiatives.
- The idea is to base the budget on the guild's earnings from the past year, which would be bear market earnings.
- The group discussed the importance of being conservative with the budget, especially considering the unpredictability of events like eath Denver.
- The group also discussed the need to avoid subjective magic numbers and instead base decisions on past data and initiatives.
- **Evaluating Past Marketing Efforts**:
- The group discussed the importance of evaluating past marketing efforts to determine their value and the amount spent.
- This would involve looking at the efforts of the spring brigade and reviewing the history of rips and treasury payouts.
- **Value of Initiatives**:
- The group discussed the challenge of determining the value of various initiatives, such as booths at events.
- They noted that while some initiatives may seem expensive, they can lead to high-value clients or other benefits.
- The group discussed the importance of allowing sentiment to emerge through a decentralized signaling process rather than relying solely on individual opinions.
- **Reviewing Past Efforts**:
- The group discussed the importance of reviewing past marketing efforts to provide context for future initiatives.
- They noted that it's essential to understand what has been funded in the past and what value those efforts have brought to the guild.

## Session 2 Notes

Goal is to fund teams and then let them execute with the alotted budget.

Some initial concerns:
- how we decide what is most valuable across the guild: how we orchestrate this conversation
- what: signal vote on below teams

- delegating to teams: ensuring that the right skills are assigned to the right tasks, how we define metrics and accountability
- how we spend the funds and how much: how we identify this number, where it comes from, how to allocate this before inviting teams to submit proposals
- how much: backward-looking marketing budget

**Other questions:**
- How much did we spend on ETHD23? (shirts, raidbrood in-kind booth, portfolio initiative)
-
### Revised Topics
* **Team: Booth Responsibilites (The Trusty Shopkeeps)**
* Responsibilities: Booth design, manning, printed promo at booth.
* Goals:
* Strategies:
* Team Size:
* Budget:
* **Team: Swag (The Artisan Weavers)**
* Responsibilities: Unique merch, design, push and sell.
* Goals:
* Strategies:
* Team Size:
* Budget:
* **Team: Hackathon Prescence**
* Responsibilities: Coordinate hackathon teams, projects, incentives...
* Goals:
* Strategies:
* Team Size:
* Budget:
* **Team: Stage (The Bardic Troupe)**
* Responsibilities: Arrange RG presence as featured speakers at EthDenver
* Goals:
* Strategies:
* Team Size:
* Budget:
* **Team: Vibes/Events**
* Responsibilities: Coordinate any cross organization collaboration. A meetup sponsored by Raid Guild? maybe at that country club?
* Goals:
* Strategies:
* Team Size:
* Budget:
* **Team: Messaging/online printed matter (The Master Scribes)**
* Responsibilities: Coordinate all twitter/online presence announcing all of the above leading up to and during EthDenver.
* Goals:
* Strategies:
* Team Size:
* Budget:
* **Marketing Metrics/Oversight**
* Responsibilities: Dashboard of marketing numbers/analyze performance
* Goals:
* Strategies:
* Team Size:
* Budget:

---

## Session 1: Topics to Consider

### **Curation of the Booth:**
- **Three Distinct Value Propositions:**
1. Strong visual presence for branding and social credibility.
2. Recruiting new clients and formulating partnerships.
3. Attracting new members to the guild.
- **Printed Matter for the Booth:**
- A manifesto or statement of vision and values (chapbook, magazine, or flyer).
- One-pager for clients (QR code pointing to the website or private chat).
- Recruiting content tailored towards desired members.
- **Swag:**
- Discussion on the type of merchandise (free vs. paid).
- Design considerations (cool designs vs. turning humans into billboards).
- Internal funding considerations for merchandise.
- **Scripts:**
- Scripts for Hunters to lock in deals.
- Recruiting scripts to set expectations for potential members.
- General evangelism scripts, including comparative references to other service DAOs.

### **Stage Presence at the Convention:**
- **Two Different Strategies for Speaking Engagements:**
1. High-level cultural representation to evangelize Raid Guild.
2. Technical workshops or demonstrations of projects.
- **Preparation:**
- Different skill sets required for different types of presentations.
- Need to define the perceived value returns for each type of presentation.
-

### **Participating in the Hackathon:**
- **Team Formation:**
- Strategically form balanced teams of Raid Guild members well in advance to maximize our presence in the sea of faces.
- Balance teams with technical and non-technical contributors.
- The whole guild should swarm to support these builders with our social channels to raise awareness and increase potential for recognition.
- **Partnerships:**
- Support hackathon teams in attending events hosted by blue chip organizations like ConsenSys, Polygon, etc.
- Help them to be in the right place at the right time for the right exposure.
- Ensure Raid Guild representation is in the best light: scripts

### **General Support and Vibes:**
- **Social Media Preparation:**
- Update the website for ETH Denver to make us look our absolute best.
- Make the portfolio consistent and updated with current significant work.
- Prepare social media announcements (Twitter threads, blog posts, AMAs, guild town halls conducted in public specifically about how we will show up to ETHD).
- Requires a strategy for recording, archiving, and sharing content. This is a very different skill set that organizing and hosting the content. Should not all be by 1 person!
- **Hosting a Live Event: RaveGuild, Hacker House, or Otherwise**
- Determine the value proposition of the gathering first.
- Consider partnerships for event sponsorship well in advance.
- Potential for hosting speakers or workshops: intentionally recorded and evangelized.
- Consider economic support for Raid Brood to brew a custom beer for the event: members only? Not mass distribution but low key.
- Consider partnering with other organizations for event setup so we don't host it alone: bring 2 or more communities into converation.

## **Proposed Structure for Deciding Priorities and Taking Action:**
### **Provisional Roadmap:**
- **Phase 1 (Now Until Mid-October):** Capture the list of topics in the forum.
- **Phase 2 (3rd and 4th Week of October):** Formalize topics onto a signal vote or TCR for decentralized prioritization.
- **Phase 3 (All of November):** Individuals step forward to own topics, form teams, create proposals with justified budgets, integrate guild feedback and criticism, and finalize strategies.
- **Phase 4 (1st Week of December):** Funding proposals go on-chain and voting. Budget allocated before the end of Q4.
- **Break (Mid-December to 1st Week of January):** Historically dead, but teams can of course get started early.
- **Phase 5 (2nd Week of January to 2nd Week of February):** Action phase with work completion before the convention on February 23. Followed by knowledge sharing, celebration, and last-minute planning.

---