Ideation and product vision
From idea to minimum product: the five steps of design thinking, divergence and convergence, brainstorming, the product vision statement, the minimum viable product, the build-measure-learn loop and the roadmap.
- 22 cards
- 5 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Questions
- Sort and link
- Scenarios
- Understand
A few cards from the deck
Design thinking: what is it?
Show the answer
A user-centred approach in five steps: empathise, define the problem, ideate, prototype, test.
You start from people before proposing solutions, and go back when a test disproves an idea: the steps form a loop, not a line.
During a brainstorm, a participant says an idea would cost too much. What does the session's rule say?
- Write it down anyway and judge later
- Remove it at once, since cost is an objective criterion
- Put it to a vote before moving on to the next
- Keep it only if its author can put a figure on it
Show the answer
Write it down anyway and judge later
Judgement is deferred to convergence. An idea that is too costly can inspire an affordable one, and a climate of criticism silences participants.
Each diamond of the double diamond starts with a … phase, where options are opened up, and ends with a … phase, where one is chosen.
Show the answer
Each diamond of the double diamond starts with a divergence phase, where options are opened up, and ends with a convergence phase, where one is chosen.
The first diamond explores the problem (discover, define), the second explores solutions (develop, deliver). Mixing up the two phases means sorting too early or never concluding.
Brainstorming: what is it?
Show the answer
A group session that looks for many ideas in little time, deferring all judgement, aiming for quantity and building on each other's ideas.
Criticising during production silences unusual ideas. Sorting comes afterwards, in the convergence phase.
The team spends a year building a full app that nobody adopts. What is the cause, and what should be done for the next product?
- The code was poor: hire more experienced developers and rebuild the application
- Advertising was insufficient: fund a wider launch campaign among students
- The product was not rich enough: add features before relaunching it to the same audience
- No hypothesis was tested: build a minimum viable product and loop build, measure, learn
Show the answer
No hypothesis was tested: build a minimum viable product and loop build, measure, learn
A year without user feedback bet the whole product on assumptions. A minimum viable product tests the riskiest one at lower cost, and each turn of the loop corrects the direction.