Lesson plan

Growth hacking

Growth hacking is a subfield of marketing focused on the rapid growth of a company. It is referred to as both a process and a set of cross-disciplinary (digital) skills. The goal is to regularly conduct experiments, which can include A/B testing, that will lead to improving the customer journey, and replicate and scale the ideas that work and modify or abandon the ones that do not, before investing a lot of resources. It started in relation to early-stage startups that need rapid growth within a short time on tight budgets, and also reached bigger corporate companies. A growth hacking team is made up of marketers, developers, engineers and product managers that specifically focus on building and engaging the user base of a business. Growth hacking is not just a process for marketers. It can be applied to product development and to the continuous improvement of products as well as to growing an existing customer base. As such, it is equally useful to everyone from product developers, to engineers, to designers, to salespeople, to managers.

Back to article

Article summary

Growth hacking is a subfield of marketing focused on the rapid growth of a company. It is referred to as both a process and a set of cross-disciplinary (digital) skills. The goal is to regularly conduct experiments, which can include A/B testing, that will lead to improving the customer journey, and replicate and scale the ideas that work and modify or abandon the ones that do not, before investing a lot of resources. It started in relation to early-stage startups that need rapid growth within a short time on tight budgets, and also reached bigger corporate companies. A growth hacking team is made up of marketers, developers, engineers and product managers that specifically focus on building and engaging the user base of a business. Growth hacking is not just a process for marketers. It can be applied to product development and to the continuous improvement of products as well as to growing an existing customer base. As such, it is equally useful to everyone from product developers, to engineers, to designers, to salespeople, to managers.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.