---
# System prepended metadata

title: Buddy System MVP and a Travii Use Case
tags: [Buddy System]

---

---
###### tags: `Buddy System`
---

# Buddy System MVP and a Travii Use Case

![](https://i.imgur.com/oxyVXJQ.gif)

### BS Overview

The Buddy System is a great tactic for getting new contributors up-to-speed, identifying synergies, helping each other grow, bridging silos in the DAO, and identifying gaps in our individual and collective understanding. On the cultural side, the Buddy System cultivates conviviality and offers checks and balances to ensure ongoing cultural alignment to make sure we are building the right things in the right ways in the right order for the right reasons.

### BS Problems

- How might we gather ideas on how we can bake-in the prioritization of problems into our culture before jumping to solutions?
- How might we move towards defining a clear peer review process while restraining to impose restrictive structure?
- How might we make these learnings available for the wider DAO community to benefit from collectively?
- How might resolutions arise organically as local emergence without requiring the full attention/distraction of the greater DAO?
- How do we ensure culture fit and ideological alignment with new contributors?
- How might we clarify the difference between onboarding to the DAOhaus community and contributing to Warcamp?
- How might we help individuals understand how they can maximize impact, best apply their skillset, and play to their strengths?

### BS Method

Travii's's have had (and continue to enjoy) great success with our pairing. We simply want to extend the details of this experience so others might choose to adopt the practice or formalize these ideas into policy. Here is our minimally viable buddy system that we continue to employ to this day:

1. **Daily calls**, 4x per week. Instills repetition and personal reliability.
2. Allow each other to **vent** in a manner that doesn't fit in other meeting spaces.
3. Ask each other for **feedback** and have reflexive conversations about DAO priorities.
4. Extend a **direct line** to ask questions about how the DAO and sub-DAOs work. 
5. Collaborate in **identifying gaps**, and then working together to document them for the benefit of the whole DAO.
6. Share divergent experiences and **cross-disciplinary training**.
7. Challenge each other to get explicit about **where we are personally trying to get to**, in relation to where the organization is trying to go.

### BS Rage Report
The Travii's's humbly put forth an outline of our experiences while working together 1:1 since January of this year. [You can view a **Rage Report** of our personal experiences here.](https://hackmd.io/@daohaus/Travii-Buddy-Rage-Report) TL;DR=

1. Feedback loops are important.
2. Talking through complex problems is important.
3. Accountibility to each other is important.
4. Synchronicity for inter-circle knowledge sharing is important.

### BS Next Steps

- Share your own buddy collab, onboarding, or orientation experiences in the comments below.
- Fork the Travii's's BS Rage Report and experiment with your own BS.
- Find a buddy! Step into the wonderful BS!
- Critique the shit out of our BS so we can all collectively learn and improve upon our BS.


*Sincerely with love,
T+T* 💩

![](https://i.imgur.com/zFn8YMN.png)