A framework and method for developing a Product Strategy collaboratively (Part 3)
A framework and method for developing a Product Strategy collaboratively (Part 3)Also some thoughts on whether or not managers should be technicalThis is Part 3 in a 4-part series. Please read Parts 1 and 2 before continuing:
In-person collaborative Product Strategy workIn Part 2 I discussed how (and why) we chose the Product Strategy framework that felt right for our team. I also talked about the pre-work we did to establish the current state of our Product Strategy. In this post I’d like to talk about the in-person work we did to define, for each of the Product Strategy components:
First, I should say that being together as a team for the first time in three years was fantastic, and definitely my highlight of 2022. At Wildbit we had annual retreats, but for ✌️reasons✌️ we obviously couldn’t get together for the past 3 years. The in-person time was universally wonderful and I am confident it will sustain another year of remote work. But let’s get back to the strategy work. The way we structured our sessions was not necessarily conventional. I don’t know if it was the best way to do it, but we made a few intentional decisions about the structure that felt important. First, we had the discussions together with all ~30 team members. We didn’t do the usual workshop thing where you break up into smaller groups and then report back to the larger group. This was a deliberate decision because we really wanted this to be a full team effort. It likely meant that fewer people spoke up, but it also meant everyone had all the context of our discussions at all times. I loved it. A comment from someone in customer success could spark a marketing idea from someone in engineering that got everyone excited... and that felt magical. So, we all took live notes in a Google Doc while using the structured outline to guide our discussion (see Part 2). It was a little chaos at times, but the good kind of chaos. The kind of chaos that gets people excited about the product and our customers. I won’t be able to share too much of what the document ended up looking like, but here’s an excerpt from one section: We could’ve done this in many different ways. We could’ve used sticky notes and affinity diagramming. We could’ve done small group work with readouts from each team. We could’ve tried to make the conversations more structured. But in the end I really like where this ended up. It was kind of exhausting (especially for the facilitators), but the energy of having everyone together in one room dreaming about the future of the product just felt so good. Which leads me to the “what didn’t go so well” bit... We just didn’t have enough time! We mostly got to a good place with our ideal future state for each component, but we didn’t quite get to the “hopes and fears about the future state” question. I wish we had more time to discuss that because I think we would’ve gotten some really good insights out of that reflective question. That said, I believe that the outcomes we did achieve—and the way we got there—outweighed the potential drawbacks. So what did we come out of the retreat with? We had a vision statement we all believed in. We had a long Google Doc with the raw notes from our sessions. We had enough discussion to have a common understanding of and agreement on some of the strategy components that we weren’t so sure about when we entered the sessions—such as how to think about an expansion in our target market due to the acquisition. In short, our Product Strategy was starting to come together nicely as we began to flesh out the different sections I shared in Part 2: We also had a clear understanding of the next steps: the leads team would consolidate the document into a first draft of a coherent strategy that we can share with the team for another round of async feedback before we finalize. That’s where we’ll continue in Part 4, the final part of the series. I’ll talk about how we refined the strategy, shared with the team and the larger Executive Leadership Team, and how we used it to come up with our broad 2023 plans. See you next week! What I’m readingDavid Hoang wades into the treacherous waters of the Should managers be technical? debate, and IMO comes out safely on the other side. I really like the 3 points he makes towards the end to articulate his point of view. I won’t spoil it because it’s worth reading the whole post. There’s one other bit I wanted to comment on, though:
I agree with the point that as you move into a leadership role, you can’t be as involved in the technical details of the product as much as you used to. But one mistake I see leaders make is to extract themselves completely from the product. And this becomes a bigger problem, especially in larger organizations. The further away the leadership team are from customers and the product, the more difficult it becomes to create product strategies that provide real customer (and business) value. Without the context of how the product works—and more importantly, how customers use the product—you cannot have a strategy that fully takes customer value into account. You end up with strategies that are too heavily skewed towards business value. A good product strategy balances both those things. So, leaders: Spend time with your product at a deep technical level. Download Postman and interact with the API. Ask to be invited to a few customer calls each week, and attend at least one every two weeks. Don’t lose your proximity to the heart that keeps your business alive and well. This is a bleak take on Generative AI (but also kinda hard to disagree with):
I’m not here to defend Ticketmaster but there are some pretty interesting technical details in this article about what went down during the Taylor Swift fiasco:
If you’re into the economics of live music, the challenges for smaller artists, and how pop music has changed over time, I highly recommend this one. Some stray links
|
Older messages
A framework and method for developing a Product Strategy collaboratively (Part 2)
Tuesday, January 3, 2023
Also some amazing photos of a famous jazz recording studio
A framework and method for developing a Product Strategy collaboratively (Part 1)
Tuesday, December 27, 2022
Also I hope everyone is enjoying Dead Week!
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
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 ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏