Matchmaking "Statement of Shipping"

[phil-ociraptor]

Objective

Now that a lot of requirements have been gathered (see #11) it's time to start reviewing all of those requirements, brainstorming, bouncing ideas off of each other and identifying possible solutions to the problem. The end result should be a "Statement of Shipping".

Please consider

• 100% manual solutions where no code is used (basically what we're already doing, but better)
• Solutions that can be done in weeks
• Solutions that can be done in months

Collaborators

Matchmaking PM: @garyzhuge Matchmaking Engineers: @kdmarble @Leeoku @TadjM

This process will be driven by the PM, although this is a funny situation where the engineers have a ton of context and their input is extremely important. Then

Deliverable

A "Statement of Shipping", which is like a mini Product Spec:

1. [PM] What problem are you solving (Demonstrate a strong mastery of the customer point of view)
2. [PM] Outline each potential solution (doesn't need to be very detailed)
3. [PM] A more detailed outline of the selected solution. Include low fidelity mockups (i.e. pen + paper or better) of the proposed flows
4. [ENG] Architecture overview

After this task, Engineering can start task break down and assigning work. PM will transition to "support" mode:

• work with engineering to find alternatives to technical challenges (i.e. ok that was way more difficult than we thought, instead of doing X, would it be easier if we did Y?)
• help with UI design (might need to get help from a designer or sharpen design skills)
• think about how to have a successful rollout/launch