Metadata
- Authors: Jake Knapp, John Zeratsky, Braden Kowitz
- Full Title:: Sprint
- Category:: đź“šBooks
- Finished date:: 2023-02-02
Highlights
Solve the surface first (Location 378)
you can work backward to figure out the underlying systems or technology. (Location 381)
turning these potential problems into questions makes them easier to track – and easier to answer with sketches, prototypes, and tests. (Location 679)
your map will show customers moving through your service or product. (Location 694)
individuals working alone generate better solutions than groups brainstorming out loud. (Location 1193)
These discussions are frustrating, because humans have limited short-term memory and limited energy for decision-making. When we jump from option to option, it’s difficult to hold important details in our heads. (Location 1366)
Instead of meandering, your team’s conversations will follow a script. This structure is socially awkward, but logical – (Location 1373)
It’s okay if some parts of your prototype don’t work. You can have buttons that don’t function and menu items that are unavailable. Surprisingly, these “dead ends” are generally easy for customers to ignore in Friday’s test. (Location 1666)
the sprint is great for testing risky solutions that might have a huge payoff. So you’ll have to reverse the way you would normally prioritize. If a small fix is so good and low-risk that you’re already planning to build it next week, then seeing it in a prototype won’t teach you much. Skip those easy wins in favor of big, bold bets. (Location 1689)
Make sure the whole prototype can be tested in about fifteen minutes. (Location 1696)
Building a façade may be uncomfortable for you and your team. (Location 1756)
Don’t prototype anything you aren’t willing to throw away. (Location 1763)
you’ll be falling deeper in love with a solution that could turn out to be a loser. (Location 1765)
You want to create a prototype that evokes honest reactions from your customers. You want it to be as real as possible, while sticking to your one-day timeline. (Location 1775)
If the quality is too low, people won’t believe the prototype is a real product. (Location 1777)
There’s a good chance that your team’s regular tools are not the right tools for prototyping. (Location 1939)
We know it sounds crazy, but we’re 90 percent sure you should use Keynote to make your prototype. (Location 1947)
for many physical-product sprints, you may not need to prototype the product at all. One of our favorite shortcuts is the Brochure Façade: Instead of prototyping the device, prototype the website, video, brochure, or slide deck that will be used to sell the device. (Location 1960)
So Nielsen analyzed eighty-three of his own product studies.fn2 He plotted how many problems were discovered after ten interviews, twenty interviews, and so on. The results were both consistent and surprising: 85 percent of the problems were observed after just five people. (Location 2071)
A great series of context questions starts with small talk and transitions into personal questions relevant to the sprint. If you do it right, customers won’t realize the interview has started. It will feel just like natural conversation. (Location 2156)
“There are no right or wrong answers. Since I didn’t design this, you won’t hurt my feelings or flatter me. In fact, frank, candid feedback is the most helpful.” (Location 2178)
Good task instructions are like clues for a treasure hunt – it’s no fun (and not useful) if you’re told where to go and what to do. (Location 2190)
you have to be careful not to ask leading questions. (Location 2248)
DON’T ask multiple choice or “yes/no” questions. (Location 2264)
DO ask “Five Ws and One H” questions. (Location 2265)