---
title: Roadmap Meeting 18-11
tags: roadmap
---
# Roadmap Meeting 18-11

The focus here is to figure out a process where we prioritise, design and spec things ahead, so that we can execute the approach we aligned on, involving priorit

We started off by looking at Adrienne's Diagram, which visualises the various thing magesmiths are taking care of.
- All the top ones are top-level navigation to create a cohesive user experience between DAOs. Main navigation includes Explore, Summon, Market, etc.
- Non-core platforms (e.g. DAObooks) will be more subdomain links and Global search should help you move from your DAO to explore, summon, etc. This Global search could potentially be customisable as a Boost

Building these separate apps forces us to build in a way where other teams can build on. From these different parts, we can have server-routed links instead of client-routed links, which should be done contextually. The experience will be consistent, but with some lag.

## Discussions on Target Audience

**Large vs Small DAOs**

Between small purpose-driven community DAOs and 1000-pax token/protocol DAOs, we leaned towards the former. A useful analogy by Spencer is startups vs enterprises. Like large enterprises, 1000-pax DAOs likely have the resources and ability to customise and build DAO platforms themselves.

**The smaller community DAOs desire an easy-to-use platform with some modularity - that's where DAOhaus can come in**. We should create a reliable and human product that gives these DAOs exposure to modularity. At some point,

**Governance-avoidant vs Governance-focused DAOs**

There are some poeple who want governance that just works in the background, avoiding the friction of governance. While the friction of governance is real, our position is that everyone should be represented and people should get shares/rewards for their efforts. By omitting governance, the community's efforts are not recognised and is not a sustainable model.

**Summoners vs Users**

We had a brief discussion about focusing on Summoners vs Members. DAOhaus can be viewed as 2 2-sided marketplace (between Summoners & Members, followed by Boost Devs & DAOs). **For this point, the network effects of increasing both Summoners & Members is crucial in achieving our vision.** Hence, both Summoners & Users are equally important in our product development priorities.

Summoning today is limited because summoners cannot really change their DAO parameters, so most summoners end up doing hardcore math in hard mode during summoning. **However, with V3, summoning is going to be less daunting as a lot of these parameters can be set after summoning.**

## Road to execution
**We will build a Summoning and core app (proposals, votes, membership, vaults) around Baal.** We will take a modular approach, but still preserve a cohesive user experience for end-users. **Executionally, we build the component libraries and hooks us to build faster.** Eventually, other developers will be able to ue these libraries/hooks to build around DAOhaus.

> Even now when we're focusing on v3, we should not forget the other efforts on V2, bolt-ons, developer stuff

## Out of scope

We had a brief discussion on what is Out of Scope, which should be continued in our next meeting on Monday. The following features were things that are considered Out of Scope

**V2 Features**
Other than Proposal Cards & bug-fixing, new features on V2 will be out of scope. Ideally, we should want someone that is in charge of v2.

**Minions**
Minions should be out of scope. Baal proposals will enable multi transactions that are configurable and enable Baals to interact with smart contracts

**Explore**
While we managed to discuss this topic, we did not have a conclusive outcome on "what is the role of Explore & Visual Discovery of DAOs?"

Some points discussed were:
- Explore is a core experience to help users navigate Web3 and discover more DAOs. It seems core, but might be something we need to collaborate with others in order to do it well.
- Should DAO discovery be more from a search engine perspective or a Services Marketplace perspective?

## Next Steps
The objective of Monday's session is to have more concrete scope definitions (both within-scopes and out-of-scopes). Till then, we should take some time to think and write down our thoughts on scope definitions.