Confirmed users
9,624
edits
Line 3: | Line 3: | ||
<b>Time</b>: 9:30 Wednesday | <b>Time</b>: 9:30 Wednesday | ||
<br/><b>Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate</b>. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a Webmaker account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate? <br | <br/><b>Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate</b>. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a Webmaker account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate? <br | ||
/><b> | /><b>Q2 strategy</b>: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/<br | ||
/><b>Lead</b>: Cassie/Karen Smith<br | /><b>Lead</b>: Cassie/Karen Smith<br | ||
/><b>Collaborators</b>: Cori Schauer + Tony Santos (User research) + Kat | /><b>Collaborators</b>: Cori Schauer + Tony Santos (User research) + Kat |