For my first six months at Smartcat I was drowning in alignment meetings. Product strategy syncs, design syncs, engineering planning, stakeholder updates. Then a design decision I made without the tech lead created three weeks of rework, and a feature shipped broken on mobile because I did not involve design early enough. The three people most capable of preventing those mistakes were not actually making decisions together. That is when we formalized the trio.
What a trio is, and what it is not
A product trio is a PM, a designer, and a tech lead who own a product area together and are accountable for the outcome as a unit. It is not a standup, not a design review, not approval theater where the PM brings fully-formed ideas and the other two rubber-stamp them. What matters is that alignment happens synchronously during discovery, not asynchronously in threads where half the team never reads the context. All three perspectives get baked into the discovery work itself, so the tech lead spots architectural implications while you are still talking to customers and the designer surfaces usability concerns before you settle on a direction.
The weekly shape
Block two hours, same day, same time, no pre-reads.
Hour one is discovery together. Pick one problem, not four. For 50 minutes you are in conversation mode, no one presenting. The PM shares raw interview notes, not a polished synthesis. The designer brings sketches. The tech lead brings constraints. Then 10 minutes writing what you learned: the actual problem, the assumptions you just questioned, your constraints, what you know you do not know.
Hour two is deciding together. What do we do next, who does what by when. You decide as a unit, not PM-decides-then-gets-feedback. If you disagree, you decide anyway and make the disagreement testable: build this prototype by Thursday, test with three customers by Friday, pivot if it fails.
The feature we killed in week two
Six months ago we were planning a collaboration workspace: organize projects, share assets, comment on work. Big roadmap item, an exec wanted it. In the first 50-minute discovery session the tech lead asked how we would store the workspaces, which opened a can of worms: one data model meant migrating thousands of accounts, another meant architectural debt. Then the designer asked whether customers wanted a workspace at all or just better organization inside their existing account. We ran three customer interviews in two days. All three said the same thing: I do not want another dashboard to log into, I just want to organize things better here. By week two we killed the feature and shipped lightweight tagging instead. That happened because three brains were in the room. It cannot happen in email.
The common failure is the PM dominating, coming in with a disguised answer instead of a real question. Stay genuinely uncertain. Block one two-hour slot this week, pick one messy problem you are already working on, and start.