#HowIPM · 2026-03-26 · 2 min
Key moments - from our scoring
Substance score
11 / 100
Five dimensions, 20 points each
Renata, a product manager and tabletop gamer, argues that organizational success depends on valuing ideas based on merit rather than job title. She emphasizes how testers often generate valuable user experience insights, how PMs can meaningfully contribute to technical decisions like database modeling and metadata structure, and how dismissing ideas because of someone's role stifles both creativity and product quality. This episode is essential for team leads, engineering managers, and product leaders who want to build psychologically safe teams where cross-functional collaboration drives better outcomes. By breaking down role barriers and treating all contributors as potential sources of innovation, organizations can leverage their full talent pool and create products with greater applicability and user value.
Testers often have deep insights into user journeys and user experience that can generate strong product backlog ideas, regardless of their official role. Dismissing ideas based on job title means missing valuable perspectives that improve product quality.
PMs can bring user-centric and product strategy perspectives to technical architecture discussions, and these alternate viewpoints can make implementations more effective and aligned with actual product needs.
According to Renata's experience, dismissing ideas because of someone's title leads to less good products with lower applicability, reducing overall team effectiveness and innovation.
Getting too bogged down on people performing very specific roles and discounting ideas based on the source, rather than evaluating ideas on their merit and potential impact.
Our reviewer’s read on each dimension, with quotes from the episode.
The entire two-minute episode delivers a single, well-worn point - don't dismiss ideas based on job title - with minimal elaboration. There are no sub-ideas, no surprising corollaries, and no density whatsoever; it is essentially one platitude stretched to fill a brief slot.
Just because someone is a tester doesn't mean that that person isn't perfectly capable of bringing really good user journey or user experience ideas into your product backlog
'Break down role barriers' and 'value ideas regardless of source' is foundational Agile/cross-functional collaboration boilerplate - arguably the single most repeated piece of PM advice in existence. Nothing here is contrarian, first-principles, or counterintuitive in any way.
My product management trick is about breaking down role barriers
Renata self-identifies only as 'a product manager' with no company, no scale of experience, and no verifiable accomplishments mentioned. The intro leans heavily on personality descriptors rather than any practitioner credential.
I'm Renata. I'm a product manager and a tabletop gamer and a kitten herder and I also moonlight as a whiskey aficionado
There are zero named companies, no metrics, no timelines, and no concrete outcomes. The only quasi-specific examples - database modeling suggestions and metadata structuring - are mentioned in passing with no detail about what was recommended, what changed, or what the result was.
I oftentimes will make recommendations to my engineers about database modeling or about the way that they're structuring metadata
This is an uninterrupted solo monologue with no host, no questions, no follow-ups, and no opportunity for challenge or depth. The format structurally prevents any conversational craft from existing.
That's something that I have experienced in a prior life and I feel actually led to less good and less applicability to the products that we are creating
Computed from the transcript - who did the talking, and the words that came up most.
The How I PM collection includes 50 strategies from practicing product leaders. Most are available exclusively to Product Way members. Renata McCurley, Founder of Mariposa Insights, has led product teams for over 20 years across consulting and enterprise environments. In this tip, she addresses a pattern that costs teams their most creative thinking: filtering ideas by the job title of the person who raised them. Renata shares how she challenges that pattern on her own teams. She talks about making technical recommendations to her engineers, why her team evaluates contributions on merit regardless of role, and what opens up when a team commits to hearing ideas before checking credentials. Get the full library of 50 How I PM strategies plus PM Select, where we connect product managers with companies actively hiring for PM roles:
Transcribed and scored by The B2B Podcast Index.
I'm Renata. I'm a product manager and a tabletop gamer and a kitten herder and I also moonlight as a whiskey aficionado and this is how I pm. My product management trick is about breaking down role barriers One of the biggest inhibitors I found in previous projects to really getting the creativity and collaboration that a team needs is and fostering a healthy culture within a group is getting too bogged down on the idea of people performing very specific roles within a project.
Just because someone is a tester doesn't mean that that person isn't perfectly capable of bringing really good user journey or user experience ideas into your product backlog. Don't discount an idea just because of the source. I oftentimes will make recommendations to my engineers about database modeling or about the way that they're structuring metadata. I'm kind of an alternate source for that information, but now and then something will hit home and it'll make an idea more effective when we actually implement it in the product.
I'm so happy that my engineers don't disregard me just because I'm a PM when I bring technical expertise to the table. That's something that I have experienced in a prior life and I feel actually led to less good and less applicability to the products that we are creating.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
Changying (Z) Zheng - Connecting Teams Through OpsBrave UX with Brendan Jarvis 🇺🇦 · on cross-functional collaboration79 / 100
The Data Mix - S3 Ep2 - Rosanne WernerThe Data Mix Podcast · on cross-functional collaboration78 / 100
Customer Success Playbook Podcast S3 E66 - Jake McKee - AI Experience DesignThe Customer Success Playbook · on user experience design77 / 100
Learning TogetherAll Things Product with Teresa and Petra · on cross-functional collaboration75 / 100
Tool selection and the unpredictable variableContent Operations · on Metadata structure73 / 100
#294 The Skills Every CFO Will Need by 2030 Myles Corson EY Global Financial Accounting Advisory Services, Strategy and Markets LeaderGrowCFO Show · on cross-functional collaboration72 / 100
How Small Experiments Improve Team Processes42 / 100Why Your Timelines Sound Like Promises33 / 100Stop Putting Features on Your Roadmap43 / 100Tell Your Product Story with a Strategy-Based Roadmap (#HowIPM)31 / 100Tell Your Product Story with a Strategy-Based Roadmap