Objective Process for Product Reviews
I watched Jeff Veen’s “Designing for Disaster” talk (below) and took away a couple of parts that I thought were really good. Some notes:
How to do Product Reviews (can be design, product, process, anything) — making an objective process out of something that is very subjective.
- Optional attendance, but mandatory participation (keeps everyone focused)
- Not a forum for expressing opinions
- Rather, a place to solve problems.
- Define in the beginning if session is supposed to be divergent or convergent.
- Divergent – I want as many ideas to solve this problem as possible – let’s talk about everything; brainstorming
- Convergent – Evaluating feasibility, acknowledge constrains. Drive towards consensus.
Driven by Purpose
- Measure momentum in days (weekly checkup of progress)
- Measure projects in weeks (figure out pace, when we will go out with the next thing)
- Measure priorities in months (“we’re going to focus on performance and distribution in Q2”)
- Measure vision in years (“organize the world’s information and make it universally accessible”)