Talk about your next project
productboard case study

The lesson

Anchor an enterprise story in the old coordination cost, then show how one shared product system changed feedback, roadmaps, and executive visibility.

The move

The page opens with Autodesk’s logo, company facts, the challenge “Static, out-of-sync roadmaps,” and a quote from Mitko Vidanovski about executives reviewing roadmaps in one place. The story then explains Autodesk’s Building & Infrastructure Design products and says the organization adopted Productboard to connect systems across the product lifecycle. It gives early adoption facts, including onboarding 20 product teams in less than 2 months and seeing 2,000+ roadmap views across 167 unique viewers over a 90-day period. The narrative then moves through “How it started: Aligning on the right problems,” with subsections on capturing feedback, reaching alignment, and multi-product oversight, before shifting to “How it’s going: Faster alignment on the right investments.”

Why it works

  • Our readThe left-side customer facts and challenge give a fast brief before the reader reaches the longer story.
  • Our readThe first quote names the executive visibility payoff, so the case is not only about product managers organizing feedback.
  • Our readThe before sections make the pain operational: lost feedback, static roadmaps, extra meetings, and dependency risk across product lines.

What not to copy

Don't copy Autodesk's product names, construction examples, or Building & Infrastructure Design org details. Keep the structure of customer facts, one executive-facing quote, early adoption proof, then a before and after story about how product work changed.

More from productboard

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.