Lessons from years applying the Growth Machine
When I first read Hacking Growth, something shifted in my thinking.
Sean Ellis’s framework became an absolute turning point in my career. I’ve read the book three times now, and each time I revisit it, new layers of understanding emerge. The Growth Machine and the Growth Pyramid have become my professional compass.
I systematically recommend the book to anyone entering the world of Growth. It remains a foundational reference that has guided my decision-making across every company where I’ve led Marketing and Growth.
But ironically, the more deeply I worked with the framework, the more I learned one of the most valuable lessons in Growth: no framework should ever become dogma.
When the playbook becomes a dogma
At one of the companies I worked with, after I introduced Hacking Growth to the founding team, it quickly became mandatory reading, and one of the founders became an enthusiastic advocate of the approach.
The problem?
Every initiative we discussed, whether a new campaign, a channel test, a product release, or even building our Go-To-Market strategy was forced into the same Growth Machine model.
His reasoning seemed sound:
“We have a validated framework to test channels, generate hypotheses, measure results, and scale. Why not apply it systematically to everything?”
But that’s precisely where the danger lies: a powerful framework is not a universal solution.
Frameworks can also kill agility
There’s an even subtler trap that many growth teams fall into: when the desire to “do it by the book” actually starts killing agility.
There were moments when we needed to launch a campaign quickly, test a message, or seize a time-sensitive opportunity. But insisting on rigorously running every action through the full framework process (formal hypothesis creation, experiment design, pre-metrics, scoring, post-analysis) created unnecessary operational friction, especially when the cost of failure was low and speed was the most valuable asset.
Growth requires method, but it also requires fluidity.
If the framework starts paralyzing the team, what was meant to be an accelerator becomes a brake.
Each framework has a distinct purpose
Every framework is built to answer a specific question.
The Growth Machine is brilliant when the question is:
“How can we accelerate and sustain the company’s growth engine?”
Especially after achieving Product-Market Fit, when there’s already clarity on what we offer and to whom.
The Growth Pyramid lays out the organizational pillars that enable this machine to run: data-driven culture, experimentation mindset, cross-functional alignment, strategic focus.
But when the question is still:
“Who is our Ideal Customer? What core pain are we solving? How should we position ourselves in the market?”
… we’re dealing with a Go-To-Market Strategy challenge, not pure growth optimization.
This is where I realized we needed to bring a different framework into the discussion: the GTM Mandala Framework.
The GTM Mandala Framework forced us to first map:
- our competitive positioning;
- our Ideal Customer Profile (ICP);
- customer pain points and buying triggers;
- key messaging;
- differentiation strategy.
Only once this foundation was clearly established could the Growth Machine truly operate at full efficiency. Otherwise, it’s like stepping on the accelerator without knowing which direction you’re headed.
Discovering the answers is the real challenge
Even with the right framework in hand, one of the most underestimated challenges in early-stage growth work is this: how do we actually find the right answers?
We often treat ICPs, pain points, and positioning as items to be filled in during a strategy workshop, but in reality, they are insights to be discovered through investigation, not declarations made on a whiteboard.
This was one of the most valuable pieces of feedback I received from Sean Ellis: knowing what questions to ask is essential, but knowing how to get the right answers is where the real skill lies.
So how do we uncover those answers in practice?
Here are a few approaches that have worked in real growth environments:
- Start with “must-have” users
Identify your most engaged users, those who would be genuinely upset if your product disappeared tomorrow.
Ask:
- “What was happening in your life or work when you found us?”
- “What problem did we solve that no one else could?”
- “What would you use if we didn’t exist?”
- Analyze retention before acquisition
Segment your users by cohort and retention rate.
Ask:
- Which cohorts retain better?
- What actions or use cases do they share?
This helps refine your ICP based on evidence, not opinion.
- Look for buying triggers in interviews
Ask users:
- What triggered your search for a solution?
- What convinced you we were the right choice?
These patterns often define key emotional or situational hooks for messaging.
- Use behavioral data to sharpen hypotheses
Identify behavioral signals that correlate with retention and satisfaction:
- What’s the “aha” moment in product usage?
- Which features drive repeated engagement?
- Co-create your messaging with users
Test your copy directly with real users:
- “Would this message make you feel seen?”
- “Would you click on this if you saw it today?”
In short: strategy is not something you just decide, it’s something you discover, through conversation, observation, and iteration.
If you skip this discovery process and jump straight into execution frameworks, you might build a very efficient growth machine, but one that’s accelerating in the wrong direction.
And that realization, inspired by Sean’s feedback, made me think: this topic deserves a dedicated deep dive. It’s too important to just skim over, so I’ll explore it further in an upcoming piece. I might have to bother Sean again for that one, haha.
My direct conversation with Sean Ellis
These reflections led me to reach out directly to Sean Ellis himself.
His response was both generous and precise:
“The Growth Model isn’t a one-size-fits-all solution… For earlier-stage companies still shaping their go-to-market strategy, the Growth Model is more of a living hypothesis — something that evolves as the team learns more about customer behavior, acquisition, retention, and monetization.”
This captures the key insight perfectly:
The Growth Machine is incredibly powerful, but it demands timing, maturity, and ongoing evolution.
Most frameworks share a common root
Interestingly, almost all these frameworks: Growth Machine, Mandala, JTBD, Blue Ocean. Share a common philosophical root: the timeless PDCA (Plan-Do-Check-Act) cycle.
All of them are grounded in planning, execution, learning, and continuous adjustment.
As Sean wisely pointed out:
“It doesn’t make sense to scale acquisition if retention is weak or conversion is inefficient.”
Likewise, it makes little sense to fully activate a growth engine if we don’t yet have crystal-clear clarity on who our ideal customer is or which problem we’re solving with sufficient strength.
The hidden maturity in Growth leadership
The biggest mistake I’ve witnessed, and one I’ve made myself, is treating frameworks like step-by-step recipes.
Frameworks never replace critical thinking.
They help us structure thinking, they reduce complexity, but they never eliminate the need to interpret context.
The real maturity of a Growth leader lies in knowing:
- which framework to apply;
- at what stage;
- at what depth;
- and how to adapt it accordingly.
A compass remains essential
Sean Ellis’s work has profoundly shaped how I think about Growth.
But perhaps the greatest lesson, one that Sean himself reinforced in our conversation, is this:
Frameworks are compasses, not GPS devices.
The map always needs to be adjusted as the terrain reveals its true nature.
The Universal Laws Behind Every Growth Framework
These principles aren’t just useful, they’re foundational. They silently power every other model or framework we use: the Growth Machine, Mandala, JTBD, AARRR, loops, even the ones we haven’t invented yet.
If I had to summarize the universal laws of sustainable growth, based on everything I’ve learned from Sean’s work (and many hard lessons in the field), they would be:
- Don’t scale what isn’t working
- Retention before acquisition
- Learn from real user behavior (not opinions)
- Solve a real pain with clarity
- Align the entire company around customer value
- Measure before scaling
- Iterate fast, learn faster
Even if the structure of a framework evolves: new visuals, acronyms, or tooling. The foundation rarely changes. That’s the beauty of real principles: they survive beyond trends. Just like the PDCA cycle has guided continuous improvement for decades, these laws are the bedrock of lasting growth strategies.
That’s why I believe this deserves a full deep dive. These laws are not just a checklist, they’re the operating system behind every successful growth model. Whether we’re talking about the Mandala, the GEOX framework, or strategies we’ll build in the future, it all starts from the same root.
So yes… I’ll explore them in more depth soon. And I’ll probably have to bother Sean again for that one too. 😄
What about you? Have you also faced similar challenges when applying frameworks?
Growth, at its core, remains an ongoing exercise in adaptation.
