People who create IT digital products test hypotheses at an unprecedented speed. Even comparisons with traditional manufacturing are a thing of the past, and now we are changing and improving the work process of a quarter ago. Growth hacking is one of the ways to create services that can grow to suit users more quickly. It is a lightweight book that makes it easy to understand what growth hacking is as a way to test hypotheses at a low cost.
Author: Seunghwa Yang
There is nothing worse than discovering later that the product you have invested a lot of time and effort into, turns out to be something no one wants.
All projects will be hypothesis testing. Spending a lot of resources on a single hypothesis is a risky approach if you don't know which hypothesis will succeed. In order to reduce risk, it is necessary to naturally verify hypotheses at minimal cost. There are times when we fall into various planning traps when we fail to achieve our goals, but I thought that the key is how well we repeat the Lean process of Hypothesis – Execution – Learning centered on verifying the Product Market Fit. A way to test a hypothesis is to ask the user or observe their behavior. There must be these two ways
It also briefly introduces how to ask questions to users, but it seems to be one of the important criteria that anyone who makes a product should know.
Question method
Growth Hacking is the activity of finding key metrics and finding ways to grow those metrics.
You can only grow by measuring your current status and setting goals. By defining key metrics around AARRR, you can create products around user behavior. If different teams have different goals, resources may be torn apart to achieve different goals, but setting goals around the user will ensure that everyone is working toward one goal.
Defining appropriate goals and focusing on them as one unit is the most fundamental element of growth.
Organizations whose goal is to maintain the status quo can be meaningful simply by setting goals and then executing them. (ex. Achieve 00 this month) However, if you are an organization that needs high growth, the ultimate goal will be endless growth, not a specific number.
When you actually work on a project, you try to solve countless problems at once. If a project is carried out randomly without a clear goal, there will be insufficient resources even with 10, 100, or 1,000 people.
Also, Chief Yang. Great for deep insight into the culture for growth.
