✳flâneur — a map of the web's best reading

Google Testing Blog: Communicate Design Tradeoffs Visually

testing.googleblog.com · 1,125 words · saved by 1 readers

A goal of any written design or project proposal is to present and evaluate alternatives. However, documents that include multiple solutions can be difficult to read when the qualities of each solution are not clearly expressed. A common approach to simplifying proposals is to use “pros and cons” for each alternative, but this leads to biased writing since the pros and cons may be weighed differently depending on the reader’s priorities. In this example, can you quickly tell how this option would measure up against others? Option 1 - Optimize Shoelace Untangling Wizard in ShoeApp UI Pros Shoelace Untangling Wizard UI will use 10% less CPU Less than one quarter to implement Users will see 100ms less UI lag Cons Security risk (shoelace colors exposed) until ShoeAppBackend team fixes lacing API ShoeAppBackend will be blocked for 3 months User documentation for Shoelace Untangling Wizard UI has to change This format requires the reader to remember many details in order to evaluate which op

Google Testing Blog: Communicate Design Tradeoffs Visually Testing Blog Communicate Design Tradeoffs Visually Thursday, September 21, 2023 Google Labels: Tim Lyakhovetskiy , TotT    Labels  TotT 113 GTAC 61 James Whittaker 42 Misko Hevery 32 Code Health 31 Anthony Vallone 27 Patrick Copeland 23 Jobs 18 Andrew Trenk 13 C++ 11 Patrik Höglund 8 JavaScript 7 Allen Hutchison 6 George Pirocanac 6 Zhanyong Wan 6 Harry Robinson 5 Java 5 Julian Harty 5 Adam Bender 4 Alberto Savoia 4 Ben Yu 4 Erik Kuefler 4 Philip Zembrod 4 Shyam Seshadri 4 Chrome 3 Dillon Bly 3 John Thom

Explore this link on the map →

related reading