Maple's one source of truth for product decisions

Before Jira Product Discovery, Maple wasn't short on ideas. Customer asks, internal requests, and strategic bets lived everywhere: in docs, in Slack, in tickets, and in people's heads. Prioritization meant hunting for ideas instead of weighing them, and work often jumped to delivery before it was shaped. Maple needed one source of truth for product decisions, and today it's how every product team captures opportunities, weighs them against strategy, and decides what to build.

Brent Johnson sits down with Axel Sooriah from the Jira Product Discovery team for a candid, peer-to-peer look at how Maple got the whole org on board: his setup, his month by month schedule, the team routines that made it stick, and how he won product managers over first.

You'll learn:

• What was really breaking before Jira Product Discovery (too many good ideas in too many places) and the trigger that started the pilot.

• How adoption actually spread: solving a visible pain first, winning over product managers, and tying it to the rituals teams already had.

• What to standardize for alignment (core fields, statuses, leadership views) and where to leave teams room to shape their own.

Can't make it live? Register anyway and we'll send the recording.