What research methods and test types does Wynde support?

Wynde supports a broad set of research methods for product teams: usability tests, surveys, asynchronous user interviews, Figma prototype and live website testing, A/B tests of design options, discovery surveys, card sorting, product copy validation, first-click tests, and 5-second tests. You can combine these into a single study, and the platform is positioned as unmoderated, meaning respondents complete tasks on their own rather than in a live session with a moderator.

Core method categories

Wynde groups its capabilities into three broad buckets, and each one serves a different research goal.

Usability tests and surveys

Use these when you need to watch how people move through a flow or collect structured answers at scale. The platform describes creating "a range of usability tests, surveys or asynchronous user interviews using a wide variety of methodologies," so the same study builder covers both behavioral tasks and question-based instruments.

• Usability tests — task-based sessions where respondents attempt something and you observe where they succeed or stall.
• Surveys — structured questions for product feedback or discovery.
• Discovery surveys — early-stage questions to understand needs before you design.

Asynchronous user interviews

Instead of scheduling live calls, you set up interview-style prompts that respondents answer on their own time. This suits teams that want qualitative depth without coordinating calendars, and it fits the platform's stated goal of involving the whole team in research.

Prototype and website testing

You can test before anything ships:

• Figma prototypes — validate flows and interactions on designs.
• Any website — run tests against live or staging sites.

Specialized test types

Beyond standard usability runs, Wynde lists several focused methods. The table below maps each to what it actually measures.

How findings are reported

Wynde's own example output shows how results come back: a summary states that "most respondents (55%, or 27 out of 49) didn't understand how to apply a coupon during the checkout process," with a smaller subset (12%, about 6 of 49) flagging a different issue. That pattern — a headline finding plus counts and percentages — is what you can expect from an unmoderated study, and it's the reason the platform emphasizes speed: you get quantified signal without a moderator in the loop.

Choosing a method

Match the method to the question you're asking:

• "Can people complete this task?" → usability test on a Figma prototype or live site.
• "Which version is better?" → A/B test of design options.
• "Do people understand this screen at a glance?" → 5-second test.
• "Where do people look first?" → first-click test.
• "Is our wording clear?" → product copy validation.
• "How should content be organized?" → card sorting.
• "What do users need?" → discovery survey or asynchronous interview.

If you're unsure, start with a usability test plus a short survey in one study — it gives you both observed behavior and stated feedback from the same respondents.

Practical notes before you start

• Prepare your stimulus first. For prototype tests, have your Figma file ready to share; for website tests, confirm the URL is accessible to respondents.
• Write tasks as goals, not instructions. "Find a way to apply a discount" produces more useful data than "click the coupon field."
• Expect unmoderated limits. Because sessions aren't moderated, unclear tasks won't get clarified mid-run — pilot your study with a colleague first.
• Recruiting is part of the platform. Wynde describes itself as helping teams "find relevant respondents," so participant sourcing sits alongside test creation rather than requiring a separate tool.

Pricing and plan limits aren't specified in the available site information, so check the Pricing page directly if seat counts or study volume matter for your team.