Play and test prototypes

I need someone to run the prototype with Michael from growth and call out every place a click or swipe doesn't feel like the product we sell. Start with the sign-up flow I linked, go through desktop and mobile breakpoints, and stop if an interaction takes more than three taps to complete. After testing, email Michael and me a short list: three critical breaks that block conversion, two visual bugs that erode trust, and one quick mitigation we can ship by Friday.

Before I hand this prototype to the user research session, make the core task obvious: label the primary CTA consistently, remove any dead links, and ensure microcopy shows success and error states. Surface timing of transitions so I can script tasks for participants, and flag any flows that require data we don't have in test accounts.

We demoed the prototype to Priya in growth and the animation during onboarding made her think the screen was frozen. She asked whether users can skip it and whether it performs on older phones. I don't know if the animation causes input-blocking or if our test devices mask lag. What is the most likely cause and the best next move to prove it quickly before our next demo?

Over the last three launches we get stuck in the same cycle: we hand over prototypes with flaky interactions, stakeholders call them clumsy, and engineering delays integration. Where are we losing credibility — in fidelity of touch, lack of performance checks, or missing edge-state content — and what one habit should we change so each prototype is reliably demoable?