# Meeting Setup [Image] This experience sits at a moment where people are trying to turn intent into something concrete. They already know they need a meeting. Now they need to lock in details and trust that nothing important gets missed. For the business, this moment supports reliability and repeat use. If setup feels solid, people come back without thinking twice. In this test, we looked at Zoom’s meeting setup screen in the desktop app. Participants were asked to imagine scheduling a meeting and interact with the available options as they normally would. The test focused on usability, comprehension, and usefulness to understand how easily people could take action, how clearly they interpreted their options, and whether the setup supported their needs. Testing this type of experience helps surface where confidence holds and where it softens. Small moments of hesitation during setup can lead to errors, rework, or slower momentum later. For teams working on core workflows, these signals help clarify whether the experience is quietly helping people move forward or asking them to pause more than they should. * * * ## **User Needs & Business Goals** This experience balances speed and control, giving users familiar tools to set up meetings while supporting Zoom’s need to handle many scheduling scenarios. People want to feel confident that the meeting details are correct and complete, while the business supports reliable setup that reduces errors and follow-up changes. **Audience** This concept was tested with adults primarily in the United States, with some participation from Canada and Western Europe. Participants reviewed Zoom’s desktop meeting setup screen, including date, time, recurrence, and meeting options. They were asked to imagine scheduling an upcoming meeting and indicate where they would take specific actions, as well as share how clear and useful the experience felt. **User Needs** When people set up a meeting, they are focused on getting details right without slowing down or feeling unsure. - The experience should feel easy to move through, with clear paths for common actions **(usable).** - The experience should help people quickly locate key settings like date, time, and recurrence **(findable).** - The experience should feel familiar and predictable, reducing hesitation during setup **(intuitive).** - The experience should support confidence that the meeting will work as expected once created **(reliable).** - The experience should feel worth using for both simple and repeat meetings **(useful).** Together, these needs help people move from intent to action without breaking momentum. **Business Goals** From the business perspective, this experience supports reliable and repeatable meeting creation. - Increase successful meeting setup by reducing setup errors and confusion. - Support frequent use by making recurring and one-off meetings easy to configure. - Build trust by ensuring meetings are scheduled correctly the first time. - Improve efficiency by minimizing rework, edits, or abandoned setups. - Reinforce Zoom as a dependable default for everyday meetings. When these goals are met, users save time and Zoom strengthens long-term adoption and trust. * * * ## **Choose Metrics to Test Your Meeting Setup** This concept focuses on the meeting setup experience, where people are trying to schedule a call and move on with their day. We selected a small design stack of UX metrics by mapping core user needs to signals we could clearly observe in behavior and responses. The metrics used here were Usability, Comprehension, and Usefulness. **Usable → Usability**
 When setting up a meeting, people want to act without stopping to think about mechanics. Usability captures whether users can complete common setup tasks, like naming a meeting or setting recurrence, without friction. The signal comes from where people click first and whether they hesitate or misfire when taking action. **Intuitive → Comprehension**
 People need to quickly understand what their options mean before they commit to them. Comprehension reflects how clearly labels, structure, and grouping communicate intent at a glance. This metric surfaces whether understanding comes easily or requires extra mental effort. **Useful → Usefulness**
 Meeting setup only works if the options feel worth engaging with. Usefulness captures whether the available features feel relevant and supportive of real scheduling needs. The signal shows whether people feel the experience covers both simple and repeat scenarios without feeling excessive. Together, these metrics help reveal whether the setup experience supports confidence, clarity, and forward momentum at a critical decision moment. * * * ## **Establish Hunches to Direct Your Testing** Before testing, the team had a few open questions about how this setup experience would actually hold up in real use. These hunches helped narrow where confidence might break down and where clarity might already be doing its job. Each one shaped a focused question tied to a specific UX signal. **Example: Zoom Meeting Setup**

Hunch

Question

UX Metric

The number of scheduling options might slow people down when they try to take their first action.

Where would you click first to set up a Zoom meeting for next week?

Usability

Recurring meetings may not be as easy to configure as one-time meetings.


Where would you go to set up a recurring weekly meeting?

Usability

People may hesitate when trying to change or confirm the meeting title.

Where would you go to change the name of the Zoom call you’re setting up?

Usability

Even if people can act, they may not fully understand all scheduling options at a glance.

How well do you understand your options for scheduling a Zoom call?

Comprehension

The setup experience may feel capable but not clearly valuable for all meeting types.

How much do you agree with the statement: “This app’s features meet my needs.

Usefulness

Together, these hunches aimed to understand whether the experience balances clarity, confidence, and momentum at the moment people commit to scheduling a meeting. * * * ## **Turn Hunches into Test Questions** Turning hunches into concrete questions helps remove guesswork from testing. Pairing each UX metric with a specific question type makes the signal observable, not abstract, and ensures participants can respond based on what they actually see and do. **Usability (First-click test)**
 *Question type:* First-click task
 *Example:* Click where you would go to set up a Zoom call for next week. **Usability (First-click test)**
 *Question type:* First-click task
 *Example:* Click where you would go to set up a recurring weekly meeting. **Usability (First-click test)**
 *Question type:* First-click task
 *Example:* Click where you would go to change the name of the Zoom call you’re setting up. **Comprehension (Likert scale)**
 *Question type:* Agreement scale
 *Example*: How well do you understand your options for scheduling a Zoom call? **Usefulness (Likert scale)**
 *Question type:* Agreement scale
 *Example:* How much do you agree with the statement: “This app’s features meet my needs.” This structure makes it possible to see where people move confidently, where they pause, and how their understanding and perceived value line up with their actions. * * * ## **Calculate UX Metric Scores from User Feedback** This concept tested Zoom’s meeting setup experience, where people are trying to schedule a call and move forward without revisiting their choices later. In this moment, users are focused on getting details right while keeping momentum. The design stack included Usability, Comprehension, and Usefulness, combining behavioral signals with attitudinal feedback to show how action and understanding line up. - Very Good = 90% and above - Good = 70%–89% - Average = 50%–69% - Poor = 30%–49% - Very Poor = below 30% **Usability (78% — Good):**
 Most participants completed setup-related tasks successfully, but some paused or misclicked before committing. These moments suggest small uncertainties about where to act first, rather than confusion about what the options mean. Overall, people move forward, just not always instantly. **Comprehension (96% — Very Good):**
 Participants clearly understood what the scheduling options represented. Labels and structure made intent easy to grasp without extra explanation. Understanding stayed high even as the number of options increased. **Usefulness (93% — Very Good):**
 The feature set felt relevant and supportive for real meeting needs. People felt the setup covered both simple and recurring scenarios without feeling incomplete. This reinforced confidence that the tool could handle everyday scheduling. [Image] Taken together, the scores point to a strong, confidence-building setup experience. Understanding and perceived value are clear strengths, while usability shows a mild strain where choice density slows action. The experience favors correctness and coverage, even when that means a brief pause before moving on. Click here to check out the [raw survey data and UX metric scores for Zoom’s meeting setup experience.](https://my.helio.app/report/01KEJ2DEEQR6K80GJKEB1T5R2R) * * * ## **Draw Signals from Your Design Stack** Here’s how signals were surfaced from Zoom’s Meeting Setup test results by following five steps: **1\. Focus on poorly scoring or imbalanced metrics** [Image] The overall test score landed at 89% (Good).
Comprehension was the strongest signal, while Usability trailed slightly behind the others. People generally understood what each option meant, but a few hesitated when deciding where to click first or which control handled their intent.
Signal: Clarity is high, but choice density introduces small moments of hesitation during action. **2\. Identify patterns across metrics** [Image] Comprehension and usefulness reinforce each other. The labels and structure help people make sense of the setup quickly, and most feel the features cover their needs. Where friction appears is at the interaction layer. Knowing what something does does not always translate into instant confidence about where to act. This points to a common tension between flexibility and speed. **3\. Determine if user needs are being met** [Image] - **Usable:** Partially met — Most tasks are completed, but some clicks reflect momentary uncertainty. - **Findable:** Met — Core controls like date, time, and recurrence are easy to locate. - **Intuitive:** Met — Familiar patterns reduce learning and help people move forward. - **Reliable:** Met — Users trust that the meeting will be set up correctly once saved. - **Useful:** Met — The range of options supports both simple and repeat meetings. **4\. Compare outcomes to business goals** - **Increase successful meeting setup:** Supported — Most users complete setup without breakdowns. - **Support frequent use:** Supported — Familiar structure encourages repeat scheduling. - **Build trust:** Supported — High understanding reinforces confidence in the result. - **Improve efficiency:** Partially supported — Small pauses slow some users down. - Reinforce Zoom as a default: Supported — The experience feels dependable and known. **5\. Surface signals & establish a direction** Signals derived from the data: [Image] - People understand their scheduling options quickly. - Familiar layout reduces fear of making mistakes. - Interaction friction appears when multiple choices compete for attention. - Flexibility is valued, even when it slightly slows action. **Direction based on business context:**
 The evidence points toward an experience that prioritizes correctness and coverage over raw speed. This works well for trust and repeat use, but it requires careful balance to prevent hesitation as options grow. The tension is not confusion, but decision load. Overall, this is a confident, dependable setup experience. It helps people get meetings scheduled without anxiety, even if it occasionally asks them to slow down to make a choice.