Building Your First Growth Team?
A Blueprint to Implementing Startup Growth and Making the Right Hires
Read Time: 3 mins
Good news! I’m back with a new live cohort of Growth Design for a Sustainable Future. I’ve made 5 tickets for early birds (first come first serve) with code [INNOVATOR]. 5 people have signed up in the past week! Come join.
Second, it has come to my attention that I stopped receiving newsletters I really loved because Substack doesn’t send it to my inbox anymore. I’ve also received messages from people saying they don’t receive this so I’ll explore moving away from Substack over the coming month. You don’t need to do anything. ☺️ Just want to give you a heads up.
Scroll to the bottom for the audio. 🎧
The Growth Team Playbook
Build Your Startup's Growth Engine (Without Breaking the Bank)
Most founders ask me: "When should we hire our first growth person?"
Right idea, wrong question.
The real question should actually be “How do we start implementing growth strategies?”
Before this point, you’re not ready to hire a growth expert. ❌
Avoid accumulating growth debt and remain scrappy. ✅
Where are you? Need help? Reach out for guidance.
The Growth Debt Problem 💰
Here's what's happening at 90% of startups: Teams spend months building features that users never discover. You've got this amazing product suite, but your activation rates are terrible and you can't figure out why.
Sound familiar? You've got growth debt.
Growth debt is like technical debt, but worse. It's when you build capabilities without optimizing for adoption. Six months later, you're sitting on unused features wondering why growth has stalled.
This will sink you faster than the titanic. ⛴️☠️
The 3+1 Sprint Framework 🏃♀️
Andy Budd from Seedcamp (recent guest on my podcast) shared a brilliant approach that prevents this trap:
Before Series A: Run 3 sprints building features, then 1 sprint optimizing for adoption. Repeat.
Post Series A-B: Hire that analytical designer who gets excited about conversion rates and behavioral science.
Series B+: Build your "Navy SEAL" growth squad.
The Navy SEAL Approach 💡
Traditional product teams get features to build.
Growth teams get problems to solve.
It’s targeted and intentional. Instead of "Build user onboarding flow," they get "Activation is down 15% this month - fix it."
That’s why growth is the ultimate skill for tech professionals.
It requires you to understand the impact of your work.
Key insight: If it’s an acquisition or activation focus, position your growth team between product and marketing. This can prevent territorial battles that kill momentum.
3 Growth Team Essentials
✅ Short-cycle experimentation over long-term roadmaps
✅ Problems to solve instead of features to build
✅ Analytics-driven designers who speak business language
The Essential Bytes
→ Growth debt kills more startups than bad products
→ Growth teams solve problems, product teams build capabilities
→ The 3+1 sprint model prevents feature graveyards
Your Next Step
Audit your last 3 months of development. How many features shipped versus growth experiments run? If it's more than 5:1, you might be accumulating dangerous growth debt. 😵
What's your current build-to-optimize ratio? Comment if you have questions. 💬
This Week’s Byte Sized Content 🎥
The US Has More Capital for Founders…But is That What Matters? (YouTube)
Unpopular Opinion? AI Does Not Make You An Artist (Linkedin)
Comfort Creates Weakness (Tiktok)
3 Ways We Can Co-Create ✨🔮
Startup Advising
If growth design resonates with you, I advise select climate tech founders. My insights are most valuable for those ready to deepen customer discovery, design validation experiments for PMF, and build growth models. Apply here.
Growth Design Fundamentals
Hundreds of thoughtful technologists have found value in my approach to Conscious Growth Design. If you're curious about growth principles, building a sustainable future, and how to apply growth to your work, this free 5-day experience offers a glimpse into my comprehensive course.
Conscious Product-Led Growth Immersion
When teams at Uber, Ikea, and Adobe recognized the need for more conscious growth approaches, they invited me to share the frameworks I've developed for a decade in the field. You can get it here. If your team would benefit, message team@conscioustech.com to explore how a private workshop would serve your needs.
Get the Audio below ⬇️
Want audio? Become a paid subscriber for full access. Appreciate your support for this newsletter. 🤙
Keep reading with a 7-day free trial
Subscribe to Conscious Tech to keep reading this post and get 7 days of free access to the full post archives.