Context
Petra Wille and Teresa Torres use this episode to examine a community problem, not a single tactic: real product work is getting shared less often in public, while generic advice and AI-generated filler are getting shared more. Petra sees the gap from coaching product leaders, where she regularly finds strong examples of strategy, discovery, prototypes, and AI-enabled ways of working that never leave private company walls. Teresa adds the creator side of the story, including how she changed her own writing strategy to focus only on work she was personally doing. This matters to PMs because product craft improves when practitioners can learn from concrete examples, not just slogans.
The Big Idea
The product community gets better when practitioners share small, real, unfinished work, and it gets worse when that gets replaced by generic advice.
Teresa and Petra argue that the main problem is not a lack of interesting work. It is that people feel behind, too close to their work, or unsure what they are allowed to share. Their answer is simple: write for the person one step behind you, not for the person far ahead of you.
Key Insights
Useful stories are drying up
Petra's concern is not just that social feeds are noisy. It is that the most useful layer of product knowledge is disappearing from public view.
- In earlier product communities, people were more willing to share unfinished work at meetups, in company blogs, or in product community posts.
- The useful material was the how: how a team shaped strategy, ran discovery, structured a prototype, or learned from a narrow use case.
- What is replacing that material is what Petra calls platitudes. Advice like "talk to your customers more" may be true, but it does not help someone understand how to do the work.
- For PMs, the loss is practical. When concrete stories disappear, the field gets worse at collective learning.
Great work stays private
Petra says she still sees a lot of strong product work in coaching. The issue is not that good work stopped happening.
Examples she says she sees privately include:
- Strong product strategy work.
- Well-shaped opportunity solution trees.
- Clickable prototypes.
- Better versions of discovery practice.
- Product leaders documenting how they want teams to collaborate, including AI-enabled operating guidance for meetings, decks, and working norms.
The gap is that people often treat these as too small, too niche, or not impressive enough to share. That means the public conversation becomes less grounded than the real work happening inside teams.
Proximity hides what matters
Teresa argues that people often do not share because they are too close to their own work to see why it would matter to someone else.
- People assume what they are doing is ordinary because they are living inside it every day.
- People compare themselves to imagined "front runners" and conclude their own example is too basic.
- People also worry about permission: they are not always sure what company details they can safely share.
Teresa compares this to how product teams view competitors. Even when a team is leading, someone on the team usually believes a competitor is doing something better. The same distorted comparison shows up in public sharing.
Lived experience beats generic advice
Teresa says she deliberately changed her own content strategy about two years ago. Instead of writing broad guidance on topics she had already covered many times, she decided to write only about work she was actively doing herself.
- She wrote about Claude Code because she was spending time in it.
- She wrote about AI evals only after roughly a year of creating them repeatedly and developing a point of view.
- She explicitly rejects writing the generic guide just because a topic is hot.
Her claim is concrete: since making that shift, everything she has published has performed better. She says she saw more LinkedIn views, more engagement, and more blog visits. Her explanation is straightforward. Humans respond to lived experience because it contains specificity, judgment, and real stakes. Generic advice no longer stands out.
Vulnerability blocks better sharing
Both hosts frame the blocker as emotional as much as tactical. Sharing real work requires admitting where you are, including the messy middle.
- A real post may show partial progress, not mastery.
- A real post may describe an experiment that did not create efficiency gains.
- A real post may expose uncertainty, not polished certainty.
That feels riskier than posting a broad principle. But Teresa's argument is that broad principles are exactly what readers are tuning out. The content that helps others most often starts as the content that feels a little more personal to publish.
Small stories still teach
One of Petra's strongest points is that even a narrow or mixed result can be valuable to others.
- A team might try 20 things with AI and see no efficiency gain, only a different kind of work.
- A workflow change might help only in one niche context.
- A team may still be figuring out the rest of its AI practice.
Petra argues those are still useful stories. A PM reading that kind of post can compare it to their own context, disagree with it, or build on it. Public learning does not require a perfect success story. It requires enough detail for someone else to think with.
Mental Models & Frameworks
One step behind rule
This is the core audience-selection heuristic from the episode.
- Assume there will always be people ahead of you. That is not the audience to optimize for.
- Assume there is also always someone one step behind you. That is the audience to write for.
- At the end of a workday, ask: "What would I tell another product team that is about to hit this same situation?"
Use this when you are stuck on impostor syndrome. It lowers the bar from "Do I sound like the expert on the internet?" to "Can I help one person who has less context than I do right now?"
Five day sharing challenge
Teresa proposes a low-stakes practice for building the habit.
- For five days, or even ten, end each day by picking the most interesting thing that happened.
- Write a short LinkedIn post about that one moment.
- Do not aim for a universal lesson. Describe the situation, what you did, and what you think might happen.
- Expect most posts to be ignored. Teresa treats that as a feature, not a problem, because it makes the experiment safer.
The point is not immediate reach. The point is to build the muscle of noticing what is interesting in daily work.
Only share lived work
Teresa's personal filter is a useful framework for deciding what deserves public attention.
- Share topics you are personally doing, not topics you could theoretically explain.
- Wait until you have enough repetition to form a real point of view.
- Prefer a concrete artifact or practice over a broad category.
This helps PMs avoid adding to generic content. It also raises the odds that what they share contains real detail instead of recycled advice.
Decision Principles
Principle: Share the messy middle
When: deciding whether a story is too unfinished, too narrow, or too uncertain to publish.
Why: the episode argues that half-formed but specific work is often more useful than polished generalities. A PM can learn from the thinking, even before the final outcome is known.
Principle: Start from direct experience
When: choosing between posting a broad opinion and posting something that came from your own recent work.
Why: Teresa says posts grounded in direct practice perform better and teach better because they carry evidence, examples, and judgment that generic advice lacks.
Principle: Reduce the audience scope
When: sharing feels intimidating because more advanced practitioners might judge the work.
Why: writing for the person one step behind you makes the task concrete and useful. It replaces status anxiety with service.
Trade-offs & Nuance
Specificity versus confidentiality
The hosts acknowledge that some hesitation is reasonable. People do not always know what they are allowed to share.
- If a story includes sensitive company details, the answer is not necessarily silence.
- Teresa suggests generalizing the proprietary parts while still sharing the decision, the reasoning, and the lesson.
- The trade-off is that more detail makes a story more useful, but responsible abstraction is still far better than retreating to empty slogans.
Safety versus learning
Generic posts feel safer because they expose less of the author's uncertainty or current level. Real stories feel riskier because they reveal actual work.
What gets traded off is clear:
- Safer posts create less embarrassment, but they also create less value.
- Riskier posts may feel more vulnerable, but they produce more learning and, in Teresa's experience, stronger audience response.
Reach versus substance
A broad statement can be written quickly and understood by everyone. A real example takes more effort and may apply to a narrower context.
Petra and Teresa still come down on the side of substance. Their argument is that niche examples often travel farther than expected because many readers are facing a similar problem in disguise.
Common Mistakes
Mistake: Hiding behind platitudes
This happens when someone shares only the headline principle and skips the actual work.
- "Talk to your customers more" is directionally true.
- It does not tell a PM what changed, what method was used, what obstacle came up, or what was learned.
The better move is to add the missing middle: the situation, the action, and the observed result or open question.
Mistake: Waiting to feel ahead
People often delay sharing until they feel like the expert in the room.
The episode argues that this is the wrong threshold. If you wait until you feel unquestionably advanced, you will miss the audience that most needs what you know now. Public learning works because people share from the middle of practice, not only from the finish line.
Mistake: Assuming small means trivial
A narrow workflow change, a niche industry problem, or a mixed AI result may feel too minor to post about.
Petra's point is that these examples are often exactly what other practitioners need. Small stories are useful because they are concrete enough to copy, critique, or adapt.
Practical Application
Post one real moment
For the next week, end each workday by capturing one specific moment worth sharing.
- Pick a decision, disagreement, prototype, research move, or AI workflow change from that day.
- Write 3 to 6 sentences on what happened, what you did, and why.
- Do not wait until you know the final outcome.
This works because it trains you to notice that useful content is already sitting inside normal product work.
Write for one step back
Before posting, name the exact reader who is slightly earlier in the journey.
- That reader might be a new PM running their first interview loop.
- That reader might be a product leader trying to document team norms for AI use.
- That reader might be a peer who has not yet tried the approach you just tested.
This makes the post more concrete and reduces the pressure to impress advanced experts.
Generalize sensitive details
If confidentiality is blocking you, strip out the company-specific identifiers instead of abandoning the story.
- Replace product names with category labels.
- Remove revenue, customer, or roadmap details that are not essential.
- Keep the problem, decision, and lesson intact.
The result is still far more useful than a generic principle with no example attached.
Use low stakes formats
A public LinkedIn post is not the only option.
- Share at a meetup.
- Record a short video.
- Write on a company blog if that is available.
- Start with a smaller community where discussion feels more human.
Petra's point is that real examples used to spread through many channels. PMs can bring that behavior back without waiting for one platform to improve.
Questions to Consider
- Which part of your team's current product work would be genuinely useful to another PM if you described the actual steps instead of the headline principle?
- Where are you staying silent because you believe more advanced teams are doing fancier work, even though another team one step behind you could still learn from your approach?
- What result from your recent AI, discovery, or collaboration experiments felt too small to share, but would become valuable if you wrote down what changed and what you observed?
- What company detail are you treating as impossible to discuss, even though you could probably generalize it and still share the decision-making behind it?
- If you posted one real product moment every day for five days, which day would feel hardest to write, and what does that reveal about your own sharing barrier?
Bottom Line
The real loss is not that social feeds are noisy. It is that practitioners are withholding the concrete, imperfect stories that help other PMs learn how the work actually gets done. Teresa and Petra's fix is intentionally modest: share what you are really doing, keep the stakes low, and write for the person one step behind you.
Notable Quotes
"I am only going to share and write about things that I am personally doing." (Teresa Torres)
"There will always be someone a step ahead of you, but there's also always going to be someone a step behind you." (Teresa Torres)
"Write for the person that's a step behind you." (Teresa Torres)
