I have done research that changed product roadmaps and research that was politely filed away and never referenced again. The difference was almost entirely in how I communicated findings.

**The brutal truth**

PMs are busy and optimistic. They are looking for data that confirms what they already believe, and they will skim your 40-page report for that data. If your key insight is buried on page 23, it will not be acted upon.

**The 1-3-10 rule**

Every research output has three forms: a 1-page top-line (for executives and PMs who need to decide quickly), a 3-page summary (for designers and PMs implementing changes), and a 10+ page full report (for those who want to dig deeper). I write all three every time.

**Lead with implications, not findings**

Never start a research readout with methodology. Start with the most important implication for the product. "Users don't understand our new navigation. We should test two alternative patterns before shipping." Then show the evidence.

**Make the ask explicit**

End every research presentation with a specific ask: "I recommend we pause the feature launch and run a quick usability test on the new navigation. I need two weeks and your sign-off."

**The asynchronous research brief**

For most ongoing research, I share a Loom walkthrough of key findings rather than scheduling a meeting. PMs watch it at 1.5x speed. They're more engaged because they're in control.

**The follow-up system**

30 days after a research readout, I send a one-line email: "Quick check-in on the [feature] research from last month — has it influenced any decisions?" This creates accountability.