We don't have an holistic view of our system yet, by building this and adding in action labels we can make better design and development decisions.
Description
[ ] Create a MVE Planning board.
[ ] Map the overall process/workflow, so we can start real co-design.
[ ] Some processes are not circular (Unsolicited comments for example, that why it needs to be time-boxed with a community/team action - grade comments for example, and the results return to participations)
[ ] Detail basic Treasury Space (It runs onder user-facing spaces, also contains data-capsule)
[ ] Detail basic Discovery Space.
[ ] Index DS Actions
[ ] Detail basic Workspace
[ ] Index WS left-rail actions
[ ] Index WS Actionbar actions
[ ] Detail basic Voting Space
[ ] Index VS Actions
[ ] Detail basic Funded Projects Space
Design Look & Feel
[ ] MAKE BEAUTIFUL / FUTURISTIC USE Node based web3 design.
Event/Question driven Serious Gaming Engine on the blockchain.
Prepare for sub MVE's:
[ ] In a simplified version below the holistic (MVE3) we can plan MVE's with action labels only.
[ ] Action labels will link to another frame, where the action label is broken down.
Design discussions:
[ ] Actions work across states as well, so this need to feed into the data-architecture, perhaps we don't use it for MVP, but prepare for the future?
[ ] Our system is quite multi-perspective, this is nice for the User facing side, but for us a bit more difficult, focus on Key/Actor/Unlocked and dumb down access/features for Visitor/Guest?
[ ] Make information actionable: Guidance Cards (Category briefs, Proposal Guides, other items?)
[ ] Decide if we want to do more wireframe like approach, as action labels can be broken down on other parts of the board. (Wireframing vs action label to work towards scripts instead of pages.)
Summary
We don't have an holistic view of our system yet, by building this and adding in action labels we can make better design and development decisions.
Description
Design Look & Feel
Prepare for sub MVE's:
Design discussions: