Stop Judging Ideas by Job Title
#HowIPM - Bi-Weekly Product Management Tips and Tricks · 2026-03-26 · 2 min
Substance score
11 / 100
Five dimensions, 20 points each
What our scoring noted
Our reviewer’s read on each dimension, with quotes from the episode.
Insight Density
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
Originality
'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
Guest Caliber
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
Specificity & Evidence
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
Conversational Craft
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
Conversation analysis
Computed from the transcript - who did the talking, and the verbal tics along the way.
Filler words
Episode notes
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:
Full transcript
2 minTranscribed 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.