We are still shaping the design methodology. Please be flexible and constructive.

Currently, we have two Active Design Projects. The other one is . It is hard to have two active projects at the same time, but we want to unblock with this one so he can start working on the cryptography and backend.

A Design Project is different from a Development Project, which we have been using all these years. A Design Project involves deep design work, every team member is expected to participate, and it is usually composed of more than one Development Project.

Our Design Process follows Google's Design Sprint Methodology. The goal is to provide a mix of methods for meetings and async work. We can use different techniques depending on the Design Project. However, we should always be aware of the 6 phases. It is very probable that every time we skip a phase, we will end up having to come back and redo it, because the outcome won't work.

Below are the 6 phases applied to the current Identity System Design Project. Each document should be a method output. Let's see how we operate async!

Everybody is expected to:

Review the Understanding Materials.
Review the Outcome and Story Map.
Share inspiration products that you like. (here)
Share sketches with quick ideas. (here)

Phase 1: Understanding

Phase 2: Define

(everybody needs to review the Outcome and Stories)

Phase 3: Sketch

(everybody must share inspirations)

(everybody must share ideas with quick sketches)

Phase 4: Decide

(Bea must share more than one Solution Sketch, everybody else can share a Solution Sketch, optionally)

Phase 5: Prototype

(Bea puts together a prototype that we must validate)

Phase 6: Validation

(Bea with help will run them)

Project Tasks