Talk about your next project
Granola case study

The lesson

Let the skeptic lead the story, then show the operational, security and support concerns the product had to answer.

The move

The story opens with the title “How Granola turned Docker's meetings into shared knowledge” and a subhead that frames Docker's Director of IT as a skeptic won over by team-wide chat and query across shared notes. Three result callouts follow: “All 600 employees,” “Shared notes” and “Faster, better decisions,” then a named quote from Jeffrey Strauss. The body moves through organic adoption, the limits of Docker's existing meeting tools, cross-platform capture, security review, consent and support. It closes by showing Granola becoming part of how Docker prepares for meetings, follows up and makes decisions, followed by a short Docker company description and product CTA.

Why it works

  • Our readThe opening makes the buyer's objection the hook, so the case study reads like an IT evaluation rather than a simple testimonial.
  • Our readThe three callouts give the reader the rollout scope, behavior change and reported decision impact before the detailed story begins.
  • Our readThe security, consent and support sections answer the practical questions an IT buyer would raise before approving a company-wide tool.

What not to copy

Don't copy Docker's developer-tools context, Jeffrey Strauss's quotes, or Granola's meeting-notes feature set. Keep the structure of organic user adoption, skeptical IT review, practical approval criteria and a closing behavior change.

More from Granola

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.