A growing 'sharing gap' is causing a decline in genuinely useful product insights shared publicly, replaced by platitudes and 'AI slop,' according to Teresa Torres and Petra Wille. They advocate for product professionals to share their 'messy middle' learnings, even 'unglamorous' results, by writing for the person 'one step behind' them. This approach fosters authenticity, combats imposter syndrome, and provides valuable, specific insights that outperform generic content. Product managers should actively embrace this practice to build credibility and contribute meaningfully to the community. This week, identify one small, specific learning from your recent work and share it publicly with your target audience.
What happened
Teresa Torres and Petra Wille observe a trend where valuable, practical product development insights are disappearing from public discourse, being overshadowed by generic advice and AI-generated content. They attribute this to fear among practitioners that their work isn't advanced enough, leading to a 'sharing gap.' The proposed solution is to share personal, specific, and messy learnings, focusing on the process and challenges rather than just polished outcomes.
A scenario you might face
Imagine an AI PM who recently spent weeks debugging a complex RAG system that consistently hallucinated on niche queries. Instead of keeping the detailed troubleshooting steps and eventual workaround private, they write a short post explaining the specific query patterns that failed, the techniques they used to isolate the issue (e.g., evaluating chunking strategies, re-ranking logic), and the final solution. This post, though not a 'glamorous' success story, provides immense value to other AI PMs facing similar RAG challenges, establishing the author as knowledgeable and helpful.
What changes in your practice
This week, dedicate 30 minutes to writing and publishing one concrete learning from your current or recent work. Focus on a specific problem, a tool you used, or a decision you made, and frame it as advice for someone at an earlier stage of tackling that challenge. Post it on LinkedIn, your personal blog, or a relevant community forum.
Questions for your team
- 01What specific AI product management challenges are we facing that are rarely discussed publicly, but would benefit from shared learnings?
- 02How can we encourage a culture within our team where sharing 'messy middle' learnings is valued and rewarded, not seen as admitting failure?
- 03What criteria should we use to decide if a learning is 'specific enough' or 'valuable enough' to share publicly?
- 04How can we verify that the insights we are sharing are genuinely helpful and not just 'AI slop' disguised as personal experience?