Newsletter: The secrets of growth engineers #9363
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
High level feedback:
-
I like the format and points in this, though maybe we need to go one level deeper somehow? I can't quite put my finger on it, but maybe the takeaways feel a little vague. Rather than "think about X" it's more like "go try this" and being a bit more explicit?
-
I feel like it's lacking at least one good example from something we've done at PostHog. This would add some credibility plus make it feel more specific to us, rather than a general guide anyone could have published. Could we come up with one example for each point, even if it's hypothetical "this is what this looks like" type example?
-
I wouldn't normally say this, but I feel like it might need some kind of conclusion? Either that, or one more point to feel a little more complete? I don't feel so strongly about this, though. Adding some examples elsewhere might be enough.
-
Let's get some custom art for this. We've used the "experiment hog" enough already!
| @@ -0,0 +1,90 @@ | |||
| --- | |||
| title: The secrets of growth engineers | |||
There was a problem hiding this comment.
'How to think like a growth engineer' tested well in the poll. 'How growth engineers think' could work well, too.
|
|
||
| The tradeoff is caring less about products, features, roadmaps, and user requests. They let the metrics be their north star and do whatever, wherever to improve it. Instead of doing what they feel is right or the roadmap set by someone else, they work trying to improve the metrics. | ||
|
|
||
| > **Takeaway for software engineers:** What are the growth metrics of what you are working on? Understand your key flow [conversion](/docs/product-analytics/funnels), activation, and [retention](/docs/product-analytics/retention). You can use a framework like [AARRR](/product-engineers/aarrr-pirate-funnel) or [growth loops](/product-engineers/growth-loops) to model this. |
There was a problem hiding this comment.
-
We should remove the "for software engineers" here. It's useful for anyone in product roles, so need to limit the audience.
-
To add something visual, could we add a graphic of a growth loop between these two sections with a caption?
|
|
||
| Growth engineers capture these gains through their unique way of thinking and working. Luckily, you don't need to go to growth engineer school to learn this yourself. If you aspire to create a successful product and business, you should care about what growth engineers do to make that happen, and this post aims to help you do just that. | ||
|
|
||
| ## 1. Being data-driven is a cliche, but it's also a way of life |
There was a problem hiding this comment.
Depending on the headline we choose, we should tweak these headlines so they match up.
|
|
||
| > **Takeaway for software engineers:** What are areas of your work that could leverage more of an experimentation mindset? Could you be more pragmatic and iterate on a hypothesis instead of just shipping the next feature on your list? | ||
|
|
||
| ## 3. How growth engineers figure out what to work on |
There was a problem hiding this comment.
Maybe change to be something "Hunting wins < fixing problems"
Yeah I agree with this, I wonder if it's because I'm reading it as a bit too general 'this is what growth engineers do' rather than 'as a software engineer, these are things you should steal to be a better engineer'? |
|
I'm using rockethog as cover for now:
|
|
Changes
Next newsletter just dropped
Checklist
Article checklist
Useful resources