Designers are biased toward best-case scenarios, whereas developers instinctively consider all the ways something could go wrong, then test for it. Designers often critique their work mainly for design issues (e.g., “this color combination doesn’t pass accessibility”) without digging into potential implementation issues (e.g., “what happens if this table doesn’t load?”). While developers inherit a history of robust error-testing practices, there isn’t much of an analog in design. Thoughtful empty state examples from Empty States. Yet it can also prevent designers from accounting for all of the ways in which a product can fail its users: interactions that don’t fire, content that doesn’t load, mistakes a user might make, or even simply accounting for all possible empty states, an often overlooked aspect of UI design. This optimism keeps them - and their teams - motivated when they encounter the inevitable challenges that arise in product work. They’re bringing something new into the world, whether an entire platform or just a feature, which requires a determined focus on ideal usage scenarios so that key aspects of a product perform as well as possible.
Product designers are invariably optimists. Using Figma variants for better error handling design Brandon Dorn Follow Brandon Dorn is a senior product designer at Dwell Magazine, where he focuses on prototyping, design systems, and information architecture.
0 kommentar(er)
