Aug 23, 2019
This is why it’s so important to talk to (a range of) people early on!
Loading...
seen from Congo - Brazzaville
seen from Finland
seen from Germany
seen from Vietnam
seen from Italy
seen from United Kingdom
seen from Italy
seen from Canada
seen from China
seen from United States
seen from Canada
seen from Netherlands
seen from Serbia
seen from Indonesia
seen from United States
seen from Canada
seen from China
seen from Japan
seen from China
seen from Russia
This is why it’s so important to talk to (a range of) people early on!
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Questions to ask before planning a usability test round: 1. What's the product to test: Are you onboarding a mobile app, a website filtering system, or a kiosk interface prototype? 2. What's the platform? When testing a mobile app, determine if the OS matters and if it might bias the study. If so, let participants choose the OS to test on. This approach works best since, for example, a back button on Android devices can matter a lot in the user experience. 3. What are the research objectives? One objective can be to check if users understand the passwordless registration and login. Another sees if they can easily navigate to the product detail page. Turn your high-level objectives into concrete research questions. 4. Who's the target audience? 5. How many participants do you need? 6. How are you going to reach them? How do you make sure they come from the target audience? 7. What will you give as a gratuity? (money, gift card, discount, tickets, lifetime access to your product, etc.) 8. Remote or in-person: Base your decision on the type of product, project scope, objectives and target audience. Choose the one that proves more feasible (technically and financially). When you've cleared up all the above, you can go on to write a detailed test plan. Good luck!
This one is trippy! . . . . . #uiux #webdesigner #uxdesign #website #uxuidesign #digital #appdesign #websitedesign #webdesign #uiuxdesign #responsivewebdesign #uitrends #interface #uxui #uidesign #productmanagement #ux #userresearch #behance #ui #uidesigner #design #userinterface #webdesignservices #graphicdesign #app #dribbble #userexperience #web #designer (at New York, New York) https://www.instagram.com/p/BvJ9Q7AB6hF/?utm_source=ig_tumblr_share&igshid=9l0pzn8ublq3
Signs your product team needs a discovery phase (not just more design time)
🚩 you've redesigned the same feature three times and users still don't engage with it
🚩 nobody on the team can articulate the exact problem the product solves in one sentence
🚩 feature decisions are based on what stakeholders prefer, not what users actually need
🚩 the user journey was mapped once, never validated against real behavior, and hasn't been revisited
🚩 you're about to start a design sprint without a clear problem statement
if any of these hit a little too close, it might be time for a proper discovery phase before the next design cycle.
sweet design hub covers exactly this:
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
A product that looked perfect but failed (and why discovery would have saved it)
Imagine this, a startup spends 4 months designing a productivity app. the UI is clean. the branding is sharp. the prototype looks stunning in the pitch deck.
They launch. crickets, users open it, poke around for a few minutes, and close it. retention is terrible. the "problem" the app was solving? turns out, it wasn't really a problem for the people they were targeting.
Sound familiar?
This is what happens when teams skip the discovery phase. Not the fun design work, the foundational work. the interviews. the journey mapping. the feature prioritization. the honest, rigorous process of understanding the user before designing anything for them.
A solid discovery phase would have produced:
a validated problem statement (is this actually a pain point?)
a real user journey (how do people currently approach this?)
prioritized features (what do users actually need, not what seems cool?)
a roadmap (how do we get from insight to product?) four months of rework, avoided.
A really clear breakdown of what discovery-first design looks like:
design is beautiful. but only when it's solving the right problem.
For Google Maps Users in U.S., It’s Now the Gulf of America
read more
read more
Looking back at the last 4 years.