Even presenting work in a single, plausible scenario can focus the type of feedback you get from teammates and can help you uncover new ways to improve your final design. Prototyping is time consuming and it’s impossible to catch every scenario. For example, if a user is installing Dropbox right after being invited to a folder, maybe the onboarding should point out that new folder. Questions about what a user is experiencing before, during, and after they encounter your designs can help you prioritize.
⏭ After: What distractions pull them away from installing Dropbox? Were they mid-way through the onboarding flow when a Calendar alert reminded them to call a client call in 5 minutes? ⏸ During: What applications do they need to access when they install Dropbox? Do they need to switch between Safari and Finder to complete the onboarding?
⏮️ Before: Why are they installing Dropbox? Did an impatient client just email them a link to a Dropbox folder and they are installing Dropbox to access the folder? Working on the Dropbox installation flow, here are a few questions we need to ask: What happens before, during, or after a user interacts with an interface is almost as important as the actual interface. While the added context helped, we found it was missing a crucial aspect - ⏰ time! Adding the dimension of time This Sketch template made it dead-simple for designers to drop their designs into a believable macOS or Windows desktop environment before printing it out for design critiques. A Sketch template to make it easy to simulate desktop environments.
0 kommentar(er)
