Startup Growth Club by Upfocus.io discussion

This topic is about
Hacking Growth
May 2022 - Hacking Growth
>
May 1-6, Chapters 1 and 2
date
newest »

Hey everyone,
Excited to get started reading with you! Does everyone have their book? Did anyone start reading yet? Anyone already past chapter 2?
Excited to get started reading with you! Does everyone have their book? Did anyone start reading yet? Anyone already past chapter 2?

Yeah, already got the book 💪
Already have some favourite parts within the first chapters and practical questions for real-life-situations.:
The part, that got stuck with me the most from chapter 1 "Building Growth Teams" was, that it's not only important to put together a great independent and versatile team for growth, but also to optimise/change the communication-structure as they go. We often assume teams have a fixed routine for communication - which most rigid companies have - but I really see more and more, that a stiff communication-structure is far from ideal.
Luckily within the Upfocus team, I was able to experience communication-growth myself and I am assured, that a lot of companies would benefit tremendously from this.
Two major questions I have (either for the AMA with Sean or for the discussion on Friday) :
- While I feel very strongly that it's important to work on the team's communicational structure, what really is the optimal way - in practice - to carve out and develop unique communication channels/paths within the team, which can nurture growth?
- The "AHA-Moment" is a major part of chapter 2. While it makes ton of sense to improve the experience of the AHA-Moment, my question here is, if there is a practical way to figure out this moment within your own project. Is it a matter of personal experience to target this part of your own product, or can this only/mostly be figured out by interviewing customers?

I started reading the book over the weekend, and I'm especially excited about it because it's highly relevant to my upcoming role :) My Kindle copy is full of all sorts of highlights.
One thought I'm not sure how to reconcile: how to know whether a Growth team is "doing well" or not. By the nature of things, it seems like a Growth team might be given more free range than other teams. It also seems like a Growth team might strike out nine times before they hit a home run on the 10th. Given the uncertain nature of experimentation, it's hard to evaluate whether the team is doing a good job.
I also love reading about the philosophy behind the Product-Market Fit survey :)
Thank you for sharing your thoughts on these first couple of chapters. Team structure and communication also struck me as something that is clearly important to get right, but challenging to get right.
It might be a good question for Sean on how to practically identify your AHA moment.
Johannes wrote: "Hey Justin!
Yeah, already got the book 💪
Already have some favourite parts within the first chapters and practical questions for real-life-situations.:
The part, that got stuck with me the most ..."
It might be a good question for Sean on how to practically identify your AHA moment.
Johannes wrote: "Hey Justin!
Yeah, already got the book 💪
Already have some favourite parts within the first chapters and practical questions for real-life-situations.:
The part, that got stuck with me the most ..."
Daniel, can't wait to hear your highlights!
It's a good question to know whether a Growth team is "doing well". To your point, once you're succeeding, then it's obvious. But, how do you know if a team is making progress before they succeed? Another good discussion item for Sean.
Daniel wrote: "Hey everyone!
I started reading the book over the weekend, and I'm especially excited about it because it's highly relevant to my upcoming role :) My Kindle copy is full of all sorts of highlights..."
It's a good question to know whether a Growth team is "doing well". To your point, once you're succeeding, then it's obvious. But, how do you know if a team is making progress before they succeed? Another good discussion item for Sean.
Daniel wrote: "Hey everyone!
I started reading the book over the weekend, and I'm especially excited about it because it's highly relevant to my upcoming role :) My Kindle copy is full of all sorts of highlights..."

I'm intrigued by the blend of engineering, design, and marketing skills needed to do this right. For most organizations, that requires a lot of buy-in (which they address in the book). Along the lines of Daniel's point about tracking success, I wonder if there are lower barrier "wins" that someone can achieve without this well-rounded team to make the case for it?
This comes from my work with developer marketing teams, who rarely have much input into product, yet still want to make an impact.
- Live video discussion on Friday May 6th at 10am PDT
- Live show link https://live.zeacon.com/web/84093582-...