A framework and method for developing a Product Strategy collaboratively (Part 1)
A framework and method for developing a Product Strategy collaboratively (Part 1)Also I hope everyone is enjoying Dead Week!When I arrived at Wildbit in 2016 as Postmark’s first product manager, my initial job was to work with the team to create a formal vision and strategy for the product. I wrote about that process in How we built a product vision and roadmap so I’m not going to spend much time on that initial process. The focus of this series of posts will be on how we redid the Product Strategy 6 years later—and how we did it together as a team. I am hoping this will be helpful as one way to approach this work in your own teams. But first, a little background. As a small team (<30 people) working on a bootstrapped, profitable product we were lucky that the Product Strategy we came up with for Postmark in 2016 remained remarkably consistent over the next 6 years. We made some tweaks along the way, mostly to the ideal customer journey, but the fact is that it worked, so we didn’t need to keep revisiting and pivoting over and over. That, however, changed in 2022 when Postmark was acquired by ActiveCampaign. The entire Postmark team moved over to ActiveCampaign and we are still working on the product together. For the most part Postmark operates as its own business, but we also recognized an opportunity and responsibility to revisit and update our Product Strategy to align better with the broader ActiveCampaign vision and goals—and include plans for integrating the two products. We are a team that loves to work collaboratively and get input from everyone, so we really wanted to create this strategy together. To do that, we broke the process up into 3 phases:
There was another part to this. We are big fans of “working in the open”, so we we felt that we had an opportunity not just to do this work as a Postmark team in isolation, but also to share our journey with anyone in the larger ActiveCampaign team who might be interested. So we created a space in Confluence where we documented our process as we went along. I highly recommend this approach because it has the added benefit of building up “organizational memory.” If we were to come back a year from now and go “wait, why did we decide to do that?”, we will have a record not just of our decisions, but also the context and the journey that led to those decisions. This is often severely lacking in strategy work, and I believe it’s one of the main reasons why strategies seem to change so often in some organizations. If no one knows why a decision was made, the next person to come along can very easily change a strategy or a direction without having the necessary context about the work that has already been done. In short, learn to love documentation! But I digress. Let’s get back on track. For this series of (hopefully weekly) posts, I plan to cover each phase of our process separately:
One more thing before I close up Part 1… I will talk about Molly Graham’s “black hole words” in more detail in Part 2, but there is one term we had to define right upfront. Since the “Product” in Product Strategy can mean so many different things to people, we wanted to be clear on the definition right from the start. Postmark is heavily focused on product-led growth, so we clarified in our documentation that when we use the term “Product Strategy” we don’t mean only design and product experience. We mean everything that goes along with that as well: product marketing, growth marketing, sales, customer success, scaling and reliability… the whole deal. And with that… I’ll see you in Part 2 where I’ll talk about the Product Strategy framework we chose to use, and how we collaborated asynchronously to lay a solid foundation for our in-person retreat work. What I’m readingJeff Patton writes about balancing conflicting goals in product development, including:
He walks through each of those moments of tension in detail, with some advice on how to navigate that. I also love this paragraph about purpose and motivation:
I wanted to spend a little time talking about the Mastodon social network and its viability as a “Twitter replacement”, since this is space that’s really interesting to me. In a new post M.G. Siegler vocalizes the viewpoint that a lot of people have, which is that Mastodon is terrible and it will fail:
I agree that right now the product is really clunky and complicated, but that is changing fast. iOS app Ivory is in Alpha and looking great. The Mammoth app is running their own server to make sign-up easier, and I imagine more apps will start to go that route. User-controlled, abuse-resistent quote-boosting is actively being discussed. I think the mistake people make when talking about Mastodon is all tied up in the search for “the next Twitter”. Please, let’s not do that. Let’s not give another social network as much power and influence as we gave that site. If the criterium for Mastodon to succeed is “it creates as many main characters as Twitter did”, then yeah, I agree with Siegler that it’s never going to get there. But if, instead, we think about it as smaller communities, loosely tied together? I think then we might be on to something. Connection > Scale. Anyway. We can connect on Mastodon if you’d like! Some stray links
|
Older messages
Obsession and the joy of iterative projects
Friday, December 23, 2022
Also 9100 fantastic words on Metallica
It’s still a long December
Tuesday, December 20, 2022
Also what companies learned while doing 4-day work week trials
A product spec template for empowered, autonomous teams
Tuesday, December 13, 2022
Also how to challenge the status quo at work
The Friday Edition // Dec 9, 2022
Friday, December 9, 2022
5 links for your weekend
When shutting down a product is the right thing to do
Tuesday, December 6, 2022
Also a new book on the product design process.
You Might Also Like
For Authors • Book Promo Subscription Svc• Set It & Forget It • Tweets & FB Posts •
Tuesday, November 12, 2024
Choose from 4 levels of Monthly & Annual Social Media Plans Enable Images BANNER IMAGE Subscribe to a ContentMo Book Promotion Affordable Monthly
🤝 Biz Buyers, This Could Change Your Life
Tuesday, November 12, 2024
PLUS: 1 hard-learned biz buyer lesson, and 1 FREE RESOURCE for you right now Main Street Minute Newsletter Header (4) (1) Biz Buyers, We've been working on something BIG for you. Something BIG for
The $2.56 Trophies
Tuesday, November 12, 2024
And why you can't get one any more.
🧙♂️ FREE Summit Ticket: "Get more Clients from your Content"
Tuesday, November 12, 2024
see you there? ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Holiday Season Tips To Help Your Revenue, Audience, and Productivity
Tuesday, November 12, 2024
End-of-the-year advice so your content business doesn't lag. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
For Authors: Audio Book Promos 🔊 Tweets & FB group posts • 60 Day orders save 15% +
Tuesday, November 12, 2024
Affordable Audio Book Promos Enable Images Audiobook Promos for Authors & Publishers CHOOSE
Waiting for Black Friday?
Monday, November 11, 2024
Hi, Just wondering, if you're waiting for Black Friday. Every year I usually do something pretty crazy! Offering deep discounts on certain products. And releasing limited 1-time-use coupon codes.
Turn online shoppers into subscribers 🛍️
Monday, November 11, 2024
4 Proven Tactics to Increase LTV for E-commerce Customers ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Oneteen and Twoteen
Monday, November 11, 2024
Why are they called "eleven" and "twelve"??
🧙♂️ Was this the brand’s fault or ours?
Monday, November 11, 2024
They never hired us again ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏