one of my goals for 2021 is to create short explainer videos for key concepts related tocontinuous discovery. this is my first one. i’d love to hear what you think. is this helpful? are there other core concepts you’d like to see me explore? you can share your comments ontwitteroryoutube.
watch the video above or read a lightly edited transcript of it below.
do you work on a cross-functional product team? how often do you work together to make team decisions about what to build? or does your product manager write requirements, your designer designs, and your engineers code?
what’s a product trio? why are they becoming so popular? and how can you get started with this way of working? let’s get started.
a product trio is typically comprised of a product manager, a designer, and a software engineer. these are the three roles that—at a minimum—are required to create good digital products.
a product trio is typically comprised of a product manager, a designer, and a software engineer. these are the three roles that—at a minimum—are required to create good digital products. –tweet this
historically, these roles have worked together by handing off work from one stage to the next. the product manager writes requirements, the designer designs mockups, and the engineers produce the working software.
however, this model is rife with challenges. oftentimes, the product manager doesn’t know what’s possible and the engineers can’t implement the requirements as written. this leads to rewriting requirements, redesigning mockups, and rewriting code. this is why so many projects end up over budget, under scope, and late.
“mercenaries” are people who are paid to do the work that is asked of them and nothing more. “missionaries,” on the other hand, are driven by a mission. they work tirelessly to achieve that mission.
great products tend to be built by missionary teams. a missionary team needs to have a say in what they are building. they need to develop a shared understanding of who their customer is; what needs, pain points, and desires (collectively called “opportunities”) they have; and the context in which those opportunities occur.
when a product trio works together to develop a shared understanding of their customer, they are in a much better position to create products that customers love.
when a product trio works together to develop a shared understanding of their customer, they are in a much better position to create products that customers love. –tweet this
what does this look like in practice?
a product trio is jointly responsible for a sharedoutcome. theyinterview customers together. theymap out the opportunity space together. they choose atarget opportunitytogether. theygenerate solutionstogether. and theyiteratively testand develop those solutions together.
they work collaboratively from beginning to end, iterating their way to their desired outcome.
when product managers, designers, and engineers work together as product trios, they have more impact.
now if you’ve never seen this model in practice, it might seem theoretical or even impossible. however, hundreds—if not thousands—of teams are already working this way.
the product trio concept is taking hold across our industry because it works.
the product trio concept is taking hold across our industry because it works. –tweet this
if you aren’t working in a product trio today, ask yourself, “how can i work closer with my product, design, or engineering peers to move toward a more collaborativedecision-makingmodel?”
don’t get caught up with trying to be perfect. remember, we are all on a continuous improvement journey. how can you make next week better than last week? keep asking that question and you’ll be well on your way.