Request for Funding: AN DAO Gitbook 1.0

@Sixto5 @luizfernandosg just confirming you have 3/3 support from the ESD to fund this project. Trust you will take into account the wealth of feedback provided by the community here and make updates to
the main proposal as @fartunov requested re: strategic alignment, once current discussions provide this clarification.


Your questions and feedback are precious because they are reminder to design with user in mind. The questions are very much aligned with my intent to orchestrate the awareness needed between the provider - say this existing project team members, and other guilds - and the users - the upcoming contributors.

Frankly speaking, these questions were with me back in August 2021. Therefore, I and we do want to clear those uncertainties through the Gitbook is the first step.

The driving force to complete the answers should come by enabling and aligning the community collaborative work force to navigate in the chaos, with confidence.

Thank you for your time and words.


I think it is exactly these questions that are difficult to answer that belong in such an onboarding document.
If you don’t find answers to those questions, don’t hesitate to ask the people that are responsible.
If this still does not lead to a satisfying answer, it might be a good idea to write that openly in the Gitbook (so that others don’t have to figure out themselves that this is an open question).

I think this has a much higher relevance than, for example, the history of the AN DAO or the product stack intro.

1 Like

AN DAO Community Handbook January Update

As the first month of 2022 is over, we would like to share with the community what has been the progress in our initiative and what our planned next steps are.

January deliverable:

Observation: the main goal of the community handbook rough draft is to give an idea to the community of what structure has been thought on and what it should include. Its content is still being developed and it will need more work. Therefore, we would love to listen to the feedback from the community.

January activities summary:

  • Team meetings occurred 3 times per week to share and discuss progress and reviews;
  • Building of a knowledge base for the handbook with actual information about Aragon and its solutions, including information mapping, curation, consolidation and structuration activities from current sources (websites and documentation);
  • Establishment of open communication channels between the initiative and AN DAO working groups;
  • Conducted participatory action research in discord channels engaging each working group to learn and understand related skills and workflow, with analysis and clustering of information in Notion;
  • DAO ecosystem collaboration assessment with Level 1 and Delicious;
  • Developing documentations through a collective writing experience to create an Aragon blog post by March 1.

Next steps

  • Research and assimilation of community feedback
  • Gitbook 1.0 Final 1.0
  • Gitbook creation and process defined for ongoing edits
  • Gitbook 1.0 published to [URL]
  • Research strategic planning & collaborations

Open workspaces

The monthly community call to listen to your feedback is planned on Friday the 4th of February from 4 pm to 5 pm CET. Look forward to it!


While we were already looking forward to the year for the AN DAO and the development of the community handbook, we were thrilled to see multiple other initiatives popping up from different fronts for the development and engagement of the Aragon community. Would love to receive your feedback on the handbook with the expectation and excitement for further collaboration in the following months.


Excellent work @Luiz and @Renzo. This documentation is mission critical to onboarding, great to see the xDAO collaboration going on. Im aware of other proposals that intend to feed into this project too. Great work guys i look forward to participating in the upcoming feedback process.

1 Like

thanks for the update, seem like excellent progress

AN DAO Community Handbook February Update

@lee0007 @daniel-ospina @fartunov

Being now more than halfway through the initiative, the activities performed in February established and maintained a feedback loop with the Aragon Community. This has allowed us to steer the development of the handbook as the initiative enters its final month.

We are keen to share with the community the progress we made in February and the plans we have for March!

February deliverable:

Observation: During the troubleshooting of the functional document, It is relevant to highlight the ongoing evolution of the community in terms of tools, growth and structure. This implies continuous adjustment of the research findings and the need for iterative feedback.

February activities summary:

  • Performance of recurrent team meetings occurring 3 times per week to share and discuss progress and reviews;
  • Planning of prototype testing and interviews across the whole community;
  • Set a design process to perform the interviews (Notion and Miro board);
  • Sorting, clustering and analysis of interview notes (Miro Board);
  • Elaboration of feedback insights summary;
  • Prioritisation of recommendations and design decisions;
  • Planning of open joint meetings with Onboarding WG.

The usability testing of the AN Community Handbook: in-depth report

Context and background

As the Aragon community begins to walk with her own legs, multiple moving pieces start taking shape: working groups formation, the exciting noise of the bounties bazaar, the development of Aragon’s ecosystem strategy, among other initiatives. During the first Handbook testing phase, our investigation into the community brought us to test how the document serves its purpose of authenticity, accessibility and inclusiveness and find out whether it works for that purpose.

We connected with the community to listen to the three profiles of contributors: Aragon Team members, core contributors - who have been active in the community since August 2021 - and new contributors - who have just recently joined it, in January 2022These diverse backgrounds provided us with views and insights that open clear opportunities to improve the handbook and understand how the DAO Academy can grow alongside the community’s needs.

What we’ve learned.

We have run interviews with nine Community members, each interview lasting roughly 40 minutes. Based on the current dynamic context, we have gleaned multiple learnings. Below are some relevant ones that will give direction to the next phase.

Visual content & communication.
The modern readers seek easy to understand content and strive for time management for their attention span. Charts, tables and videos could enhance those needs, creating more accessibility and fun in understanding the AN DAO community.
More spice and diversity in the language. The language of the gitbook should be more concise and adapted to the modern reader. Elements such as bold, italics and TL;DR should be included throughout the documentation. Also, Aragon is a global community and can improve its accessibility and dynamic global impact by translating its content to different languages.

Aragon Product Stack: foster how to create a DAO.
It could be beneficial to present solutions with similar purposes together, such as Client + Govern and Voice + Vocdoni. Then the difference between them should be made clear. How-to guides can be added for how to create a DAO. It is important for Aragon contributors to have familiarity with its solutions.

The importance of supporting a personal experience with emotional aspects.
Handbook must improve the personal and emotional experience with support for new and current contributors in the community. Current and new contributors need to perceive a clear direction and guidance and to know what to expect, which could be addressed by the contributors’ journey with more details. One example is to have clear descriptions of meetings and an explanation of the calendar with a clear call to action.

A potential barrier is the understanding of working groups and guilds.
A better definition of what guilds and working groups are should provide an open and light decision process for new contributors on where and how to participate. We observed that we should assess if guidance to working groups - due to its transient aspect - would still be relevant to foster active contributors, as bounties are starting to serve this purpose.

There is not much clarity on the reward systems.
Sourcecred might be explained as a temporary solution. The reward system portfolio needs more exposure mentioning, for example, the Coordinape experiments and considering including information about bounties. Another important insight is about ‘how to make a proposal’. Financial proposals with a quick start guide should be included in the rewards systems section, with its process clearly and visually described.

Cultural values need a reinterpretation to generate a cohesive community approach.
An alignment and discourse might support one course or approach that unifies the collective intent around the culture and values of the Aragon community in relation to the Manifesto and Charter. This entails that there is a challenge to activate collaborative dialogues about its future and values as it continues to evolve.

The impact of these learnings and their consequences

A particular insight came to our analysis, which is the legacy of the documentation and the consequences of this product, the service it provides to the community. With a potential speed of change, it requires data stewardship in the near future, a commitment that should match the innovative drive of the members. This demands an engagement plan with the various implications in each area of the current handbook and which mirrors the community culture and values.
If future accountability will not be addressed, the handbook content and structure might not be relevant in 6 months’ time.

A glimpse into the AN DAO current evolution

An overarching insight, gathered in this first usability testing and analysis, is an important shift in the engagement flow with structured experiments to unlock a step-by-step decentralisation in the AN DAO. One clear indication comes from the bounties as a decentralisation and coordination mechanism for delegating roles and responsibilities to the community.

This comes from the nature of DAO itself as a new emerging organisational design with its decentralisation and autonomous impact. This awareness is crucially connected with the learning agility needed to practise as a whole community with empathy and knowledge coordination. The handbook documentation wants to capture the momentum and help the readers, the members to achieve their goals in the community, reducing frustrations and friction in the experience of joining the AN DAO.

Next steps

  • Create the handbook repository on Gitbook and define its maintenance and update processes;
  • Update the content of the handbook with the input and feedback from the community gathered from low fidelity prototype testing in February
  • Transfer the feedback loops into the high-medium fidelity prototype (Gitbook)
  • Plan and run the final prototype test
  • Set up official Gitbook link and plan its promotion
  • Complete the collective writing experience (Luiz and Renzo) for the blog post on the handbook initiative experience to be published (post)

Open workspaces

The monthly community call to share our design research process and listen to your feedback is planned on Friday the 5th of March from 4 pm to 5 pm CET. Look forward to it!


Thanks for the comprehensive reporting from last month’s research. Great to see the wealth of insight this surfaced for the projects.

Is there is governance section that this would fit better under? I am averse to the idea of incentivising proposals as a means of reward, and feel like including them under reward mechanisms aligns them along that line as opposed to their place in the DAO (decentralisation of) governance process.

I would love to see a series of facilitated community workshops to progress this work and re-establish the Manifesto as a guiding set of values for the AN DAO journey

Look forward to seeing Gitbook v1.0, on the understanding that it would not need to incorporate all the current feedback within the next month. Agree, stewardship of this documentation should be ongoing and expect that subject matter experts will arise so that its upkeep is an ongoing, collaborative undertaking.

Nice statement of purpose
Thanks for modelling the DAO way in the development of this documentation


Thanks for the report Renzo. This seems to be progressing very well

1 Like

AN DAO Community Handbook March Update

@lee0007 @daniel-ospina @fartunov

We are thrilled to share the final step of the fast and intense journey to deliver the Aragon Handbook. Through this three-months initiative we explored the DAO to know how to simplify complexity to new joiners. Then we developed the material and structure of the handbook, connecting with the community to gather its feedback and input.

While doing it, it was noticeable how the fast growth and evolution of the DAO already made necessary updating the material. For this, we believe the handbook should be continuously developed as a tool for self-discovery of the DAO and its exposure to the community, involving different “regions” and experiences of the AN DAO. With the release of this first version of the handbook we invite DAO members and the wider Aragon community to help us with the further evolution of the handbook.

March deliverables

  • Based on the medium fidelity prototype, we completed the second loop of research and translated the community feedback from the March Interviews;

  • Publishing of the first official version of the handbook on Gitbook:
    Please note that link might not be ready as we write right now. We will share an update as soon as the official domain will be activated. For this specific task, special thanks to Brent, Carla and Mathias for their prompt support.

  • Collaborative writing experience: a blog post about the Handbook and team culture.

Observation: During the Gitbook design process, it is relevant to highlight the ongoing evolution of the community in terms of tools, growth and structure, specially with the end of season 0 and the start of season 1 This implies continuous adjustment of the research findings and the need for iterative feedback.

March activities summary:

  • The recurrent team meeting occurred 3 times per week to share and discuss progress and reviews;
  • Planning of high medium prototype testing and interviews with four Aragon members across the whole community;
  • Connected with multiple members to assess final documentation edits information (e.g. DAO2DAO);
  • Set a design process to perform the second interviews loop (Notion and Miro board);
  • Sorting, clustering and analysis of interview notes (Miro Board);
  • Elaboration of feedback insights summary;
  • Prioritisation of recommendations and design decisions;
  • Development of the structure and of the handbook on Gitbook;
  • Planning of open joint meetings with the Community Experience (onboarding) squad;
  • Planning the publishing and distribution of the Gitbook.

The usability testing of the AN Community Handbook: 2nd feedback loop

Based on the previous report and feedback loop, we have intensively embedded the input and crafted the official handbook. The method we applied is concept and testing prototype.

With a second feedback loop, we tested the high fidelity prototype asking questions to validate the previous design decisions. Specifically we articulate questions to investigate how to improve our focus on the following objectives:

  1. We wanted to address a reinterpretation of cultural values and how to generate a cohesive community approach.

  2. We wanted to bring clarity on the reward systems, and how to make the journey to get compensated more accessible.

  3. We wanted to lower the barriers about understanding of working groups and guilds activities and how to join in.

  4. We worked on the product description and presentation to make it as easy as possible to digest, with a less ‘marketing’ and more ‘user centric’ language.

  5. We enhanced the importance of supporting a personal experience along with emotional aspects with step-by-step journeys.

What we’ve learned.

The vital importance of the Handbook legacy: if the Aragon community wants to embrace consistently better coordination, the handbook should be constantly maintained and updated with the collaborative community presence.

Next steps

  • Expand the learnings of the handbook initiative with the formation of the Learning and Experimentation squad, to be part of the People Guild;
  • To publicise the Gitbook and expand its accessibility with a video Loom as tour of the Gitbook

Open workspaces

  • Notion - Handbook Initiative workspace
  • Miro - Research plan and timelines
  • Notion - Collective writing blog post

The monthly community call to share our design research process and listen to your feedback is planned on Friday the 8th of April from 4 pm to 5 pm CET. Look forward to it!


Good work folks

Would be great to also see a future proposal for maintaining this :wink:


It’s LIVE! thank you for opening with Video. I’m on page 1 and already hooked,

ESD General Meeting Monday 4 April UTC 1900: Unanimous agreement to complete funding on the release of a LIVE Gitbook You totally delivered team! well done.

Although not in any way subject to the funding of this proposal we would love to hear

  1. Where and how this document will be shared across the community
  2. How it will be refined and maintained ongoing, ideally within ongoing workstreams.

Look forward to hearing more from this team. Please share a link to any future proposal here

1 Like

@Sixto5 I’ve already added this to the Start Here on Discord. This is so awesome, great work @Sixto5 and @luizfernandosg :slight_smile:


Congrats to the team on this. It looks fantastic and we all appreciate your outreach across the community that has led you to this great outcome.

To @lee0007 point am very interested in how we keep sharing and raise awareness on it - can’t wait to see it shared more


Thanks @Shawncubbedge - That’s a good initial place on Discord to let the community delve into it.

Thanks @lee0007.

For now, we will definitely pin the Handbook in the DAO Academy channel, we will share this on Twitter through the Aragon channels.

In the next proposal, we will develop processes with ongoing workstreams.

Thanks @daniel-ospina!

We surely want to expose further the legacy of this document.

Thanks @b3n - Hopefully, we aim to expand the flow of co-creation to empower the community as much as possible with the Learning & Experimentation proposal.