Our squad is currently working on signup, login, and onboarding. We want to make sure that people understand what Hotjar is and what value they can get from it. We’re also aiming that once a user is signed up, they can get up-and-running quickly.
As a product team, we take an experiment-driven approach to building Hotjar. This means preparing multiple versions of the experience—the Hotjar user interface—and presenting them to selected portions of our users. We measure to see which experience performed the best and based on this knowledge make decisions on what should be launched to more users.
As a young team with a fair amount of new joiners, I thought it would be a good idea to use Hotjar to see how people use Hotjar. I planned a session that was designed to increase our knowledge of our users as well as getting us all more accustomed to using the product we’re building.
I invited my team to a one-hour session with two goals: watch recordings, and create action points. Prior to the session, we’d just launched a couple of user-facing experiments in the product, so as the facilitator I decided to focus the session on recordings related to the experiments we’re running.