The User Research Strategist

The User Research Strategist

Stop stakeholders from ignoring you

How to Use the Pyramid Principle to Write Research Reports

Use the Pyramid Principle to make your research insights stick (and get acted on)

Nikki Anderson's avatar
Nikki Anderson
Apr 22, 2025
∙ Paid

👋 Hey, I’m Nikki. Each week I write about UX research strategy, communicating impact, and using AI to do your best work. For more: Claude Skills Bundle | AI Prompt Library | Team Training

P.S. Paid subscribers get access to full archive, all content, a private Slack community, Substack lives, and a hub of templates, scripts, and mini-courses


Unsplash

If you’ve ever spent weeks on a research report only to have stakeholders skim it, misinterpret it, or worse, ignore it entirely, you’re not alone.

No matter how great your research is, if you don’t communicate it well, it won’t have an impact.

This realization hit me early in my career when I spent three weeks crafting a beautifully detailed 30-page research report. I presented it to the product team with excitement, only to hear:

  • “Can you summarize the key takeaways in a few sentences?”

  • “So… what do you actually want us to do with this?”

  • “I didn’t have time to go through everything, can we just chat?”

I was crushed. All that effort, and they weren’t even reading it. That’s when I realized I was structuring my reports the wrong way.

Fast forward to today, and I structure every single research report using The Pyramid Principle and it has changed everything.

Now, my reports don’t just get read. They drive real product decisions.


If your reports keep landing with a dull thud, it’s rarely the research and it’s usually the structure. Paid subscribers get the full Pyramid Principle system I use to write reports stakeholders can skim in two minutes. Inside the paywalled section, I share:

  • my exact “first sentence” formulas (by study type)

  • a copy/paste report skeleton with headings you can reuse every time

  • a simple way to choose 2–4 “key arguments” without dumping your whole findings list

  • examples of weak vs strong insight statements, rewritten into stakeholder-ready language

  • how I package evidence so it reads like a case, not a data dump

  • the “action plan” block that stops the “so what?” question before it shows up

  • a finished example you can mirror for your next report

Exclusively for paid subscribers

User's avatar

Continue reading this post for free, courtesy of Nikki Anderson.

Or purchase a paid subscription.
© 2026 Nikki Anderson · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture