Jul 30, 2020 • 6 minutes read

Say hello to Conditions 👋

You can now apply conditions to your mazes to create contextual, dynamic flows based on your testers’ input.

At Maze, we’re big believers in bringing our users’ voice into our decision making and this is why we review user feedback regularly. Over the past couple of months, we noticed a common theme among many feature requests: the need to create custom, dynamic flows based on the testers’ responses.

And this is why we’re excited to announce our newest feature: Conditions. 🎉

Before Conditions, testers completed the sequence of blocks in a maze in order. Now, you can apply conditions to your mazes to create contextual, dynamic flows based on testers’ input. This means you can easily send them on a custom path after a completed mission, follow up with your testers, ask screening questions before they get started, and more. The result? Richer data for you and a customized user experience for your testers. It’s a win-win.

“Conditions can act like a ‘moderator’ in a moderated test. Based on the tester’s responses and behaviors, the maze can respond in context and create a more dynamic, personal experience. In the end, our users are able to collect richer insights.”

Arjen Harris, Head of Product at Maze

Conditions is a solution that enables several use cases that were requested on our feedback board. Here are some examples of the ones that inspired us to build this new feature. We hope these inspire you to use Conditions, too.

👣 Custom paths from or to a Mission

“It would be great if you could show participants certain questions or missions based on their previous actions and/or answers.”

To get the most out of your usability testing with Maze, you can show a question or a new Mission based on the outcome of a previous Mission. For example, if a tester completes a Mission indirectly, you can then send them to a specific question to get more information about why they took the path they did. This enables you to collect more contextual, qualitative feedback to complement your usability data.

Add a condition to a Mission

🧐 Give-up question

“Testers should be able to leave feedback when they give up a mission. I think this will make Maze next level.”

Not everyone will complete your Missions—and there are different reasons for this. But you won’t know until you ask. So, to get a better understanding of why testers give up on a Mission, simply set up a follow-up question. This will enable you to collect contextual feedback about their actions.

Add a condition to a Mission

🔀 Contextual follow-up

“It would be great to be able to branch our survey into different paths when it comes to the blocks.”

When creating research surveys, you can define your respondents’ paths based on their responses. This enables you to create dynamic, customized surveys for your audience. For example, if you ask your testers a Yes/No question, you can send them to different follow-up questions based on their response. Ultimately, this means that you are able to collect more contextual data.

✋ Screener

“It would be great to have more filters for recruiting users from a panel or conditional logic as a way of screening participants.”

Add screening questions at the beginning of your maze to ensure only the right type of profiles complete your maze. Based on their responses, you can decide whether to send them to the next question or directly to the Thank You Screen to exit the maze. This ensures that only qualified testers respond to your mazes and, most importantly, you collect relevant data.

Add a condition to a Yes/No block

✅ Consent

“It’s important to have a consent form before users start a maze stating how and where data will be recorded.”

Add a Legal Screen block (Enterprise only) at the beginning of your maze to get your testers’ consent. Based on their response you can send them to the next block to start the maze or have them exit the maze directly via the Thank You Screen. This ensures that your testers are aware of and have agreed to your terms and conditions.

Add a condition to a Legal Screen block

These are just a few examples of how you can use Conditions to create contextual mazes. We're super excited about this new feature because we believe it completely changes the way you can set up your mazes—and ultimately the quality of data you collect.

How are you going to use Conditions? Whether it's one of the use cases we covered in this article or a completely new one, let us know @mazedesignhq.

Note:Unlimited Conditions are available on all paying plans.

Try rapid testing now, for free.