A structured debrief after a beta or pilot — what worked, what broke, and launch intent.
How long did you use the beta before this debrief?
Which features or parts of the product did you use most regularly?
List the things you kept coming back to.
How satisfied are you with the beta overall?
1 = very disappointed, 10 = exceeded expectations.
What worked well and should definitely be kept?
Tell us what felt right — features, flows, or design decisions you'd be upset to lose.
What was broken, confusing, or missing?
Be specific — describe the situation and what you expected to happen.
Did you encounter any bugs or unexpected behaviour?
→ If answer is "Yes" → skip to Q7
→ If answer is "No" → skip to Q8
Please describe the bugs or unexpected behaviour you encountered.
Include what you were doing, what happened, and whether it was reproducible.
How likely are you to use the full product when it launches?
0 = definitely not, 10 = definitely yes.
After each completed session, Mayetik generates a structured AI summary. Here's an example of the output format — the actual content reflects each respondent's answers.
The respondent's answers highlighted three recurring themes — each supported by specific examples drawn from their experience. The summary captures what was said, not what was expected.
Two responses stood out as unusually detailed and pointed to an area worth following up on. The full text of each answer is preserved below the summary.
Based on the patterns in this session, the AI identified three concrete actions for the project team to consider. These are drawn directly from the respondent's own suggestions.
Generated from 8 questions · ~10 min session