Yuna Akazawa, Product Designer at Braze. Quickly build, share, and gather actionable data from users to support wider product team needs fast. Collect actionable, quantifiable insights to inform go-to-market strategies and product decisions.
Democratize testing and research across your organization to empower product teams with the tools to test early and often and make informed product decisions. User testing designed for product teams. Get started free. Talk to Sales. Remote Testing. Maze Report. Try it now. Get user insights you can act on instantly. Concept Testing. Get feedback on ideas and concepts by asking real users before you start designing. Prototype Testing.
Validate your prototypes with real users and launch with confidence. Content Testing. Validate messaging and copy ideas with your target audience before you launch. User Surveys. Deepen your understanding of users and their needs, and collect feedback frequently. Quickly build, share, and gather actionable data from users to support wider product team needs fast.
Collect actionable, quantifiable insights to inform go-to-market strategies and product decisions. Preparing a Figma prototype that lets you do 1. For 1. Big Figma file means a slow loading time of your Maze.
In extreme cases, it might cause your Maze to crash. The reason? Maze loads up all the visuals in the file regardless of whether they're in the prototype or not. Trust us on this: If you have two or more intersecting flows, participants will find it and cross to the part of the product you didn't want them to see yet. In Maze, there's no "Restart task" button, so if participants got stuck somewhere and can't get back to the current task's flow -- they ARE STUCK and can't get back to the current task's flow.
They'll need to give up on that task. How to tackle that? Separate flows in the prototype. Maze let's you set a different starting screen for each task, so participants won't know that you got three homepages. You're not testing users' recall of task instructions, but whether or not they can perform these tasks. It might make sense to give participants a little hint about what they're supposed to choose among different options on some screens.
Make your hints distinct so that users to confuse them for part of UI. Most participants won't notice your designs aren't pixel-perfect, but they'll see illogical amounts, names, and changes from screen to screen. People get fixated on these things, which makes their feedback less useful. Try to check these three boxes: - Consistent information on all screens names, phone numbers, payment amounts, language, etc.
Sometimes you'll want to test if people can find some information in the app. Maze needs people to tap on something to recognize it as a task completed. You'll need to account for that: create a success screen in the prototype a simple thumb up will do that's triggered when the user taps on the information on the screen.
You'll need to create a new project. If we've reached the limit of active projects, ping colleagues in the maze Slack channel and check which projects can be archived. It will take Maze a few moments to load everything app, and you're ready to roll. Steps in creating a mission 1. Add a new mission block 2. Define task's title.
Write a description that gives users some context or data they'll need to input create hints in prototype if necessary. Choose your starting screen 5. Click through the prototype to define the ideal path s of completing the task. Maze counts those as "direct successes". Your prototype might allow users to get to the final screen using a different path, and that's ok -- these will be "indirect successes".
When participants get to path's final screen, they'll get a "Well done" message within 0. Don't put any important information on that screen because it will leave participants hanging.
0コメント