Group items tagged

Growth hackers are creative, constantly on the lookout for ways to increase acquisition, adoption, retention, revenue, and referral. They are disciplined, subjecting themselves to an empirical process to determine what works and what doesn’t. They understand that the product itself is the most effective marketing tool. And they are technical enough to leverage existing platforms to reach the billions of users at their fingertips.

Modern Techniques A decade later, things have changed since those early days of guerilla user testing. Now there are a few different ways to highlight usability issues and some of them are even easier, quicker, and cheaper to implement that the in-person tests that Nielsen popularized. Here are 4 test types that I’ve used: In person, moderated and lightly scripted: This is the traditional format of a usability test and of the in-person techniques, it’s the easiest one to get started with. A quick definition of terms: in person means that you’re sitting down with the user, moderated means that there’s someone talking to the user and acting as a sort of referee to keep things on track, and scripted means that there’s a fixed set of tasks written down in advance and that the moderator wants the user to accomplish. In person, moderated and unscripted: This is the Listening Lab technique popularized by Mark Hurst. It requires a bit more experience and finesse to pull off in order to gather valid usability insights without turning into a completely unstructured focus group. In it, the moderator asks the user what tasks he or she wants to accomplish before diving into the app, based on their demographic, a loose conversation about their interests, or their impressions of external marketing pages. Remote and moderated (scripted or unscripted): This can be roughly the same as the two techniques above, except the moderator and user aren’t physically present in the same room and use a video app like Skype to connect instead. This is especially a help to early stage projects, when initial early users can come from any part of the world. Remote, asynchronous and heavily scripted: This is the absolute easiest and most newbie-friendly way to try user testing. It’s enabled by relatively new tools like Usertesting.com, where the moderator and user don’t chat in real time and instead, the user is left on their own to follow step-by-step instructions on how to use the site or app in question, while their mouse movement and audio feedback is recorded.

The basic framework of an in-person tests is: Think about what goals you’d like the user to accomplish (yes, even for the unscripted tests because you still want to see if they can complete certain tasks, although in a looser, unguided format). Record everything – at least the audio and screen, if not also their face and body, so you can review later as well as share with the team. It’s a newbie mistake to try to moderate a test at the same time that you’re analyzing it for lessons, and even newbier to ask stakeholders to just listen to a summary when audio/visual feedback can have such a punch. Use about 5 or 6 people – any less has too much noise while any more has diminishing returns. Note that a qualitative research method like this is different from a quantitative one like A/B testing, where the cutoff is much higher and more users is always better. Let people explore and make mistakes on their own while also keeping them on task. Don’t talk so much that you’re explaining everything on the screen like a car salesman, but also don’t morosely sit back and let them feel judged. Try to strike a balance between friendly and observant.

Behind the term 'growth hacking'The concept for growth hacking grew out of the fact that most startups fail, and needing to not fail. When you think about games, the market is filled with large companies with lots of money to throw into marketing. Sean summed this need up well, with: When you're competing against Sony, you can't go dollar for dollar

2. A Must-Have Experience Sean focused on the importance of a Must-Have Experience (MHX) - you must have a hook that clearly identifies what this is.

3. Uncovering your MHXTo get a clear understanding of what your MHX is, Sean suggested reaching out to your Must Have Users (MHUs)… but what is a MHU?