# Gitcoin Allo PM UX/UI Raid
###### tags: `allo`
[Spec doc](https://docs.google.com/document/d/1yniob8Zt8dU2iTMYpznsFXMQNCE8Uhr6bfQSS7FqPNk/edit?usp=sharing)
[Allo docs](https://docs.allo.gitcoin.co/getting-started/introduction)
[Raid notes on Charmverse](https://app.charmverse.io/raid-guild/page-712045406966141)

### Goals:
- Intuitive flow
- Engagement on voting
- Payouts
- "simple and transparent" to ensure "accountability and opportunity" to token holders
- tracking project success
- linking to other events related to the project
- attraction and retention of builders
- time efficiency
- automation
- simplicity
- streamlining
### Mentioned Features:
- automated porting between different tools: permission to streamline this? or should we maintain as is?
- communication across DAO: in the app or integrating to other comm channels (Discord, Discourse, etc.)? What tools are currently in use, internally and externally?
- multiple phases of voting: permission to streamline this? or should we maintain as is?
- progress reports on phases/milestones
- scheduling (community updates, AMA, application interviews): can this be an integration of existing tools? if so, are there preferred tools?
- moving applications to Snapshot should migrate all original data, but still remain editable as needed.
- notifications: triggered on each application status change, dormany/unresponsive after X days/weeks
- prioritization of applications: high to low
- notes on applications: added by admins
- Discourse integration for Snapshot votes
### User Personas:
- Epic: Organizations running a grants program (on Google forms, Airtable etc.) with at least $1MM to distribute over a minimum of 2 years.
- Users: Committee members
- User: Token holder
### Stories:
- As an applicant I want to apply for a generic grant or a specific RFP.
- As an administrator I need to assign specific grant reviewers from various teams.
- As an MMG token holder I want to upvote/downvote applications to help prioritize new builds.
### Flows:
1. Application submitted by applicant: project creation/submission through Builder.
2. Admins assign grant reviewers.
3. MMG token holders vote on applications.
4. Applications are flagged.
5. Flagged applications move to Snapshot #1: Leadership Committee Space
6. Successful vote #1 moves application to Snapshot #2: Full DAO Space
7. Successful vote #2 triggers Gnosis Safe txn to send funds to address on application.
8. Gnosis Safe txn also triggers an email notification to applicant.
9. Payments are recorded and tracked in the UI, viewable to admins.
10. Project status updates are submitted by project teams via the Builder UI.
### Example Application Statuses:
- Waiting For: Secondary Review
- Waiting For: Snapshot Vote
- Rejected: Do Not Move Forward
- Rejected: Failed Vote
- Approved
### Questions:
- Goal: porting between different tools - is this necessary? Are you open to us streamlining the UX and backend to simplify the process or should we maintain the stack currently in place?
- "Showcase to the community which grants are at what stage, and encourage participation in prioritizing which grants to review or fund" - how do you imagine this feature existing?
- Snapshot: is this a mandatory, preferred, or just suggested voting tool? Are you interested in other on- or off-chain voting solutions?
---
## UX Proposal Details
### UX Scope
#### Weeks 1-6
- Get familiar with the first usecase - 1hr
- Form personas - 2hrs
- Generate user stories - 3hrs
- Identify red-routes to build sitemaps - 3hrs
- Generate low-fidelty prototype - 6hrs
- Generate interview script, typeform - 2hr
- Schedule and conduct user interviews - 8hrs
- Compile data to justify/ammend assumptions - 3hrs
- Generate a backlog of for devs - 4hrs
#### Week 7-12
- Iterate on UI design system - 4hrs
- Test UX of iterative build - 8hrs
- Bug hunt, generate bug reports - 8hrs
- Generate user documentation - 8hrs
- Final QA - 4hrs
### Budget
- 2 raiders
- ~12 hrs/week/each x 6 weeks @ $150/hr = $20k
- ~6 hrs/week/each x 6 weeks @ $150/hr = $10k
- Total = $30k
---
### Notes in Prep of Final Proposal
We got a long way to go and a short time to get there
#### Phase 1:
- Week 1-2
- E2T: Prepping for interviews
- Schedule
- Write script
- TW: Prepping flows: clarifying dev research
- integration of current apps
- clarifying the interface
- Both: Comparing notes, co-repping
- Week 3-4
- Conducting interviews
- Documenting insights
- Week 5-6
- Raging on the protoype
- Raging on the backlog
- Prepping to present a status update to Kevin/Gitcoin
- Make the "pivot or perservere" decision
= $54k
#### Phase 2: VERY TBD
- Week 1-2
- Testing part 1: validating with client
- Begin skinning the brand assets to the prototype
- Week 3-4
- Iterating to itegrate feedback/learnings
- Continuing QA
- Week 5-6
- Testing part 2: validating with external users
- Iterating to integrate feedback/learnings