I get, and see, a lot of questions from other folks in product around how others have structured their product teams. Curious how your team is organized. What roles have you added/changed as your organization changed and grew? What resources have inspired some of your thinking on this topic?
A few resources I’ve enjoyed:
- The book Team Topologies which covers a lot of ground on the organizational design aspects and considerations when structuring teams
- Adam Calica had a good article on this as well last year in BuiltIn
- Jens-Fabian Goetzmann has also written on this topic of establishing a product organization structure
We recently adopted a tailored version of Spotify’s squad/tribe model - which they ended up abandoning. I am a bit concerned about pigeon holing people in one area especially when you think about the engineers who are part of those squads.
At Railz we have a squad for all web product (Platform & Connectivity Squad), another for API & Integrations (Core Squad) and Developer Experience Squad (SDK, Libraries, Environments etc.)
Curious to see if anyone else is organized around tribes/squads and what that looks like :)
It’s interesting, as you noted, that Spotify doesn’t work this way anymore yet so many product teams do. I like the model as it helps provide focus across a clear mission.
yeah i like it too. we have seen major improvement on our end
Good morning product makers :)
I am curious how your product teams are staffed. One of the things we’re starting to notice is that the product owner tasks are dominating a lot of the PMs work (story writing, sprint ceremonies etc.). I am a strong believer that these roles should be split as the org grows but curious what you’re doing in your org. For context, our product is a technical one and requires a lot of integration research. What I have seen in the past as alt options:
Curious to know more what you do in your org. Curious also how productboard manages this
We are currently trying to find our way of organizing the different processes. For the core PO activities we have two dedicated POs.
The overall product management is done by the two POs and me (CTO), but parts of the activity is split apart to an interdisciplinary team called RPS.
The “Roadmap Planning Squad” is responsible for the roadmap management. We are trying to make a different approach here, the team combines members from the product, customer care, sales and marketing teams. We meet regularly and decide which customer insights need to be generated and we do RICE scorings together and talk about final roadmap decisions.
We are still starting on this so I’ll keep you updated on how this works for us.
I love the idea of a “Roadmap Planning Squad”
@dkirsten. Thanks for sharing this with the community!
Hi Product Makers, does anyone organize their product teams around jobs-to-be-done? Curious to know more about it - in case you can share your experience.
I liked your idea about the Roadmap Planning Squad and wondered how it’s working out ?
What’s working well ? What’s not working ?
My challenge at the moment is to get everyone to agree on what we should we working on and to stop changing priority so often !