MosEvery product team has people whose most valuable observations fall outside their job description. A QA engineer who runs through the product dozens of times a week sees user experience opportunities the UX designer, focused on the next feature, hasn’t encountered yet. A product manager with a technical background spots data architecture choices that will create rework months later. Breaking down role barriers in product teams starts with recognizing that these cross-functional observations are signal, and they come precisely because someone’s vantage point is different from their title.
Where Cross-Functional Ideas Come From
People rarely contribute outside their lane randomly. When a tester sketches a better user flow or a PM flags a metadata structuring issue, it means their proximity to the work has surfaced something the team’s default structure would miss. These contributions reflect experience accumulated across different disciplines, and they carry information the specialist in that domain may not have access to.
This is especially true for leaders who came to product management through non-traditional paths. Someone who has worked across research, operations, and technology sees the product through multiple lenses simultaneously. The connections they draw come from years of navigating different disciplines, and they surface patterns that a more linear career path would never produce. When teams create space for that range of observation, the product benefits from perspectives the org chart was never designed to capture.
What Changes When Teams Evaluate Ideas on Merit
The teams that genuinely break down role barriers in product teams change what happens to an idea after it’s raised. They evaluate the substance of the observation separately from the credentials of the person who offered it. When that separation becomes a real practice, something specific shifts: people start contributing their full range of thinking, because they’ve seen the team respond to the quality of the idea rather than the title behind it.
That shift compounds over time. A PM who regularly brings technical recommendations to the engineering table, and whose engineers take those recommendations seriously, builds a different kind of working relationship than one where contribution lanes are enforced. The products reflect it. The team culture reflects it. And the people on those teams carry a different level of investment in the outcome, because they know their observations will be heard.
How One Product Leader Practices This
Renata McCurley, Founder of Mariposa Insights and a product leader with over 20 years across consulting and enterprise delivery, has a specific approach to breaking down role barriers that starts with her own willingness to cross contribution lines. In this How I PM tip, she shares how she brings technical recommendations to her engineers and what that dynamic looks like when a team commits to evaluating ideas on merit.
“Don’t discount an idea just because of the source.” Renata McCurley, Founder, Mariposa Insights
The Product Guy 