Loading work...
ManyChat needed to know whether Quick Automation, the flow that carries new users from signup to a first working bot, was clear enough to convert and fast enough to keep momentum into more complex builds. The studio ran a two-round usability program with five participants per round across low, medium, and high tech-savviness tiers, testing intuitiveness, time-to-complete, and willingness to keep building after a first win. Participants rated speed 5 / 5 and complexity 4 / 5, with clarity at 3+ / 5, and the readout fed clarity-fix microcopy and prioritization tags directly into the backlog between rounds.
Framed four research questions (intuitiveness, challenge points, time-to-complete, willingness to build more complex automations) and a recruitment frame spanning low, medium, and high tech-savviness.
Participants rated the flow five out of five on speed and four out of five on complexity (surprisingly simple rather than expected-hard). Clarity scored three or slightly above, which is where the backlog work concentrated.
Users who got a visible result in their first bite-size step kept going. The learn-by-doing shape of the flow lowered the barrier to attempting more complex automations afterward.
Participants hit friction on specific terms where it was unclear what they could and could not edit, and when bot replies felt inauthentic. Microcopy rewrites closed most of these gaps between rounds.
Low, medium, and high tech-savviness participants all hit the same three themes (Clarity, Complexity, Speed) but at different intensities. Segmentation sharpened prioritization without changing the framework.
Every finding carried a Quick Win, High Priority, or Backlog tag. That turned the readout into a product-ready input rather than a discussion document, and compressed the loop between research and shipping.
A backlog-ready readout that accelerated Quick Automation work between the two rounds.
The two-round shape and the Clarity / Complexity / Speed theme framework let product act on round-01 findings before round 02 confirmed the fixes. Prioritization tags compressed the loop between research and shipping, with speed and complexity already working in the users' favor and clarity becoming the backlog focus.