--- tags: v3, project management, process --- # Discovery Phase - What do we need to add to this process? - Description, Use Cases, Considerations, Future Considerations, Details - Inputs into Design - Dragons can start this process, and then we get together to pair and fill out some of the details - Uncover things as we walk through and meet - Specific UX thinking around certain things that are surfaced - Chance to talk through key areas of the feature/app - Things are surfaced that will want to be on design's radar even if it's out of the current scope - Testing/Prototyping - How do we want to systemitize this? - Another meeting? This would be the focus of our time together as Dragons, and then our pre-planning meetings can become more streamlined - Proposals will have metadata via the Poster contract, so a DAO could set an expiration for proposals (DAO wide) ## Inputs Into Design - This format is a great input for design for building a prototype - Next step: Wireframes focusing on UX - Would we want to include a high-level user journey/flow? - Should go into Design right away or stay in Discovery? - As long as we know what Design is working on? - Low fidelity wireframes showing the user journey through the app/feature - Flows -> Views -> Features - **Flow** is the User Journey - Zoom in specific **View** in User Journey - **View** then contains multiple **Features** - Views can be reused throughout the Journey ## Invisible Suburbs - Getting into a good spot with the Board -- some may need a bit more details added in, but we're in a good - Who are the *types* of users that we're writing stories for? - Focus on Discovery and prioritize what's coming up in the next few weeks -- what can we keep doing to move things through the system?