---
# System prepended metadata

title: 'Product WG Call #1'

---

# Product WG Call #1
### About this call

Moderated by Luis Ivan, facilitated by Javi
Additional members attending this call: Maria, Pierre, Yalda

Date: 26 September 2019
Time: 14:30 - 15:15 (CEST)

#### Agenda

* Review the Product WG definition and its scope
* Review the Aragon product roadmap and main priorities
* Discuss mechanisms to improve coordination between Flock teams

#### Notes

* Focusing on the third agenda topic today
* Defining the difference with other working groups
    * Product WG to aim for a more practical focus
    * First half an hour focused on roadmap alignment
    * Remaining time reviewing specific topics: design, user research, other product topics (i.e. comms)
* Reviewing the current roadmap [on the website](https://aragon.org/project/roadmap)
    * Autark planning Open Enterprise mainnet launch at Devcon
    * Coordinate on Profiles and Organization Identity between Aragon One and Autark to find best fit for release
        * Coordinating changes from Open Work Labs and Aragon One allocating some time for review
        * Current design from Autark needs a design revision from Aragon One to coordinate (add this to next meeting's agenda) update
        * Want to integrate Profiles with the top-right user section for appropriate accessibility to the user's profile
        * Ideally released by end of October / early November
    * Aragon One priorities for Q4:
        * Aragon Network and integration of the client using the services of the Aragon Network. Proposal Agreements and integrating into Voting, and building an interface for jurors
        * Small iterations over 0.8 and review support
* Need better coordination around planning releases
    * Cadence for releases will be every two weeks
* Lots of feedback and thoughts around Flock this week, discussing changes
    * Unfair resource sharing and support between teams
        * Aragon One working more closely on Fundraising support due to the nature of the origin of the app
        * Shipping as a major criteria factor for a team's public evaluation, critizing delivery may not be productive
    * Defining expectations for custom client implementation development when trying to be agile and under low support bandwidth
    * Making roadmaps clearer, making proposal goals clearer and evaluation metrics over time
    * Giving more feedback in public -- otherwise tokenholders have no way to review this information
    * More structured way to offer criticism between teams
    * Shaping up the role of the Aragon Association
        * Defining feedback and performance processes
        * Better understanding their role in Flock
    * Evaluating equity deals between evolved teams and the Aragon Network
    * Thinking about the next version of Flock