Go to website
Creating your maze
How to create your Maze test.
Best practices for writing mission descriptions
A list of best practices to help you write clear mission descriptions.
How to introduce your maze to testers
Introducing your maze and product to testers is important for creating a good testing experience and getting valuable results. The concept of prototyping and user testing may be unfamiliar to some testers and occasionally they may find themselves confused by the testing process. Customizing the Welcome Screen and using a Context Screen where necessary will help y
How to change the order of blocks in a maze
Change the order of missions and questions in your maze.
Give instructions with a Context Screen
A Context Screen is a simple way to communicate with your testers during their session. Learn how to add a Context Screen.
The Welcome Screen is the first screen your participants will see when they start testing your maze. It’s a great place to make a good first impression, explain who you are, and more. Every maze includes a Welcome Screen by default. The Welcome Screen shares a welcome message with your testers to introduce them to the test. Default Welcome Screen. You can customize the left side of the screen(https://storage.crisp.chat/users/helpdesk/website/2df0219a3cda7c00/customizewelcomescreen_
How to duplicate blocks in a maze
Use the duplicate feature to create new copy blocks in the same maze. Here’s how to proceed in four easy steps. Log in to Maze Open the maze with the block you want to duplicate Hover over the block you want to duplicate Click on Duplicate this block That's it 👌 How-to video Duplicate blocks in a maze
Thank You Screen
Every maze ends with a Thank You Screen. It’s a nice opportunity to say thank you to your testers for their time and feedback, and redirect them to your website if necessary. Default Thank You Screen. You can customize the part on the left How to customize the Thank You Screen Open your draft maze
How to change the name of your maze
If you have more than one maze tests inside a project, you might want to give your mazes a name to differentiate between them. Here’s how you can do this. Instructions Open the Maze project Hover over the maze test which name you want to change Click the Change name icon Type your new name Click on the checkmark or press Enter And that’s it! 👌🏻 How to change the name of your maze(https://storage.crisp.chat/users/helpdesk/website/2df0219a3cda7c00/ezgifcom-crop-1_cvuyub
How to let testers skip questions
Questions are required by default. Find out how you can let testers skip the questions in your maze.
Design Surveys: How to show images and questions side by side
Here is how to create design surveys by displaying an image and a question side by side. Collect valuable user feedback by testing designs with users.
How to preview a single mission
Use the Quick Look feature to preview a single mission in your maze. Previewing an entire maze is a great way to ensure your test flows nicely, and that your users are seeing what you want them to see. But you might also want to preview a single mission to review the expected path and see if the mission is ready for testing. How to proceed
Everything you need to know about creating missions.
A guide to all block types you can use in Maze
Read this guide to understand the block types available for your maze.
Collect answers with a Multiple Choice question
Learn how to add a Multiple Choice question to your maze.
Collect open-ended answers with Open Questions
Learn how to add an Open Question block to your maze.
Collect closed-ended answers with Yes/No Questions
Learn how to add a Yes/No question to your maze.
Survey participants with an Opinion Scale
Learn how to add an opinion scale question to your maze.
How to set the expected path of a mission
Here's how to set up the expected path for your missions.
Best practices for writing mission titles
A few best practices to follow when writing mission titles.
Create multiple expected paths for missions
When completing a mission, testers may take different paths than the expected one you set. You can add multiple expected paths for a mission to record all paths as direct success. Maze records every path a tester takes and categorizes them into: Direct success: tester takes the same path you set Indirect success: tester takes an undefined path but reaches final screen Give-up / bounce: tester leaves your maze or gives up mission. But if a mission has more than one c