- Always Be Zagging
- Posts
- Chief Storytelling Officers
Chief Storytelling Officers
Product marketing reporting lines ↯ Personal brand building ↯ Launch fatigue
Hello and welcome to the first edition of Always Be Zagging.
On a quick personal note, I'm in my 16th and final week of family leave. My twins are nearly five months old, and my eldest is about to turn three. Life is chaotic but meaningful, and I’m finding pockets of time in the evenings to write.
There are three topics in today’s newsletter.
Who should product marketers report to?
Founder Brands
Launch fatigue
Who should product marketers report to?
In my experience, if you ask this question to three different product marketers you’ll get three different answers.
Until recently I reported to Buffer’s Director of Growth Marketing. Before that, it was our Chief Product Officer and before that, our VP of Marketing. Maybe this speaks to hazy definitions of product marketing, but I’m inclined to think it reflects shifting business priorities. In a startup, everyone does product marketing. As the company matures, product marketing becomes a subcategory of marketing that roams across the organization.
Does your business need more help with attracting or retaining users? If the former, your PMMs should sit with marketing; if the latter, they should be with the product team.
Currently, I’m on the marketing team but report to the CEO. This is the best spot for a product marketer.
Why?
My top priority is crafting industry-level narratives that differentiate Buffer from competing products. Notice I say "crafting" and not "creating." That’s because I can’t develop a narrative on my own — it must come from the company’s chief storyteller, typically the founder/CEO. My role is to connect that narrative to everything we bring to market.
Getting stuck in the weeds is easy when you’re a product marketer. There are always new features to announce, one-pagers to write, metrics to be tracked, and copy to be finessed. Reporting to the CEO pulls you out of those weeds and brings clarity to what truly matters.
For additional context, the org chart below shows my CEO’s direct reports. I’m the only product marketer on the team.
Founder Brands
Speaking of CEOs and storytelling, chances are that if you’re reading this newsletter you work in tech. And chances are that if you work in tech, you’re familiar with Paul Graham’s recent essay, “Founder Mode”.
I shared my thoughts on the topic to Threads but I wanted to touch on something related; Founder Brands.
Increasingly, I’m noticing CEO personalities superseding corporate brands. It’s a trend that aligns with the age of influencers. Generally, people don’t follow companies—they follow other people.
Mark Zuckerberg’s brand evolution is an interesting example. Portrayed as callous in The Social Network and criticized for his congressional appearances, he has recently repositioned himself as a lovable, if a little goofy, fashion icon.
The advantages of a strong founder brand are many:
PR: Breaking into the news cycle is easier with a recognizable leader.
Brand Affinity: People relate more to a person than a logo.
Differentiation: Products can be copied, but people can’t.
Culture: It’s clear to everyone what your company stands for.
The risk of a strong founder brand is that it might alienate your customers if they have a divisive personality.
Founder brands aren’t confined to big tech CEOs. If you’re a leader at a startup or smaller business, I highly recommend you develop your brand. It’ll make your marketing team’s job a lot easier. At Buffer, we’ve been intentional about our entire team building their brands on social media. The benefit for us is two-fold. It helps us empathise with our customers—many of whom are content creators—and it amplifies our reach in campaigns.
(Hopefully Threads will implement a lists feature soon!)
Launch fatigue
At Buffer, we aim to deliver value quickly, often incrementally. By keeping product releases small in scope, we maintain a tighter feedback loop with our customers. Ship fast, learn, and iterate accordingly.
The upside, from a marketing perspective, is that there is a steady drumbeat of new releases or enhancements to share with customers. Delivering improvements consistently generates goodwill.
The downside is what I call 'launch fatigue.' Launches begin to feel like a grind rather than something to celebrate, and engagement with your announcements starts to wane. Imagine if you had a birthday every week instead of once a year—eventually, you'd stop caring.
Most product marketers have a tiering system for product launches to help navigate launch fatigue. I’ve attempted to implement various iterations myself. Here’s what I currently use:
Summary | Launch Objectives | |
---|---|---|
Tier 1 - Breakthrough Product | Features that solve problems in new and innovative ways, attracting fresh eyes to our product. | • Attract new users |
Tier 2 - Value Add | Features that are particularly valuable to existing customers | • Drive upgrades |
Tier 3 - Equalizer | Features or UX improvements that bring us up to standard with the competition | • Increase website conversion rate |
The idea is to reserve major launch campaigns for Tier 1 products.
I’ve found these tiering systems to be both helpful and awkward. Helpful because they provide a framework for managing marketing resources and internal expectations. Awkward because the tiers are subjective and often applied retroactively. We try to fit features into tiers after they’ve hit the roadmap, rather than build the roadmap around tiers.
Another way software companies create Tier 1 moments is by bundling “smaller” releases together into one larger launch event. Shopify does this with Editions, and Zapier with ZapConnect.
Last month, we ran an experiment at Buffer called Collaboration Week. You can read about the experiment here. In short, it was an opportunity to discuss strategic topics fully asynchronously.
I used the opportunity to share a proposal about doing seasonal launch events. Here’s what I wrote:
I propose that we commit to two major launch moments in our calendar in 2025 (in Spring and Autumn) and that we configure our product roadmap with these two major launch dates in mind. The benefits of this approach:
Predictability: Our users can expect and look forward to a major release on a predictable schedule. It also allows our product and marketing team to plan and resource accordingly.
Cohesion: Having a set schedule for Tier 1 launch moments enables us to organize our roadmap, strategy, and entire team more cohesively around a theme and a moment. We already do this to an extent with some events, for example, Build Week.
Specialness: Launch moments should feel special. Think about the seasonal events that consumer-grade companies like Apple and Shopify deliver. When you limit the number of major launches you do to two or three per year, you make them feel more special. There is a level of build-up and excitement that can’t be replicated with ad hoc launches.
Innovation: Knowing that we have a major launch penciled in will encourage us to innovate in both product and marketing. It pulls us away from the “treadmill” of regular campaigns.
I also shared a link to this post by Brex’s CEO about rethinking how they build products and go-to-market. Here’s an inspiring excerpt:
Our releases aren’t just an artifact to manage EPD work, which we then package and ship to customers. In fact, it’s the other way around. Each release starts with a story we’re telling customers, from which we then build the product backward. It all starts with: “Here's a problem you have, and how we’re going to solve it better than any alternative you’ve seen thus far.”
We release 4 times a year, and each release has no more than 3 big themes. This forces me to choose what truly matters, allowing us to make a large, company-affecting investment in the few things that are step-function changes to the customer experience, and drop everything else. Our Winter release was the first example with Bill Pay, and I’m excited about how the Spring and Summer releases currently in the works will simplify the customer experience on Brex.
The release is the universal tool everyone at Brex uses to deliver value to customers in a predictable fashion. The word “predictable” is important. Ironically, releasing fewer times a year in a predictable cadence allows GTM teams to get our products in the hands of customers faster. Our pace of innovation and product changes last year was so high that I still meet customers that have no idea we now have AI-powered expense assistants, actuals vs budgets in real-time, and support for 50+ countries with local cards that can be paid in local currency (which requires owning your own financial infrastructure). Enabling our teams to sell, support and set up customers for success is as important as building the product itself.
My goal for Buffer is to maintain our steady drumbeat of releases but add seasonal launch moments to which we can anchor our Tier 1 releases.
Thanks for reading.