Design Sprints

Table of Contents

1. Suggested Format
2. Sprints Planned

Suggested Format

Suggested format loosely based on GV Sprint book consisting of six steps:

0. Assemble - final-decider/tie-breaker is appointed. A design sprint team assembled.
1. Vision - an actual visualization of success.
2. User journeys - list out all the user journeys
3. Feature poker - tease out the features from the journeys - stake weighted voting on features
4. Mocks - wireframes of each step in the journeys
5. Planning - milestones - issues

At every step, participants create on their own version of that steps work, present their version, unify their version with everyone elses (voting/deciding as needed), then get expert feedback, mod based on feedback as needed.

Getting everyone to do their own work then merging maximizes ideas and inclusion/interest. Getting expert feedback at every step possible (even if it's just one person per stage) adds useful perspective.

Useful steps to insert for this project (we could do them as step 3 and a half):

• A - Incentivzation analysis for all actors - incentivization spreadsheet - previously covered
• B - Economic design - an economic data flow diagram - do we need intermediate units of account?

Sprints Planned

TBD - July 27, 2017

If you have the time to chug through a week straight of work as a team - and can schedule experts to come in - then more power to you - that's the best way to go.

As we may not have that kind of time, an alternative is to chug through individual work online, then meet once a week to unify the work, and each meet with as many experts on our own, returning with feedback.