Unifying Product Launch Tiers Across Atlassian’s Growing Portfolio

We started with a comprehensive audit of every existing framework to surface common threads and divergences. We deliberately separated true product launches from routine release marketing. Next we defined shared impact pillars—customer impact, company/business impact (with ranges rather than rigid numbers, and differentiated for land vs. expand/GTM motions so newer products weren’t permanently locked out of tier one), and ecosystem/partner impact (critical for marketplace developers and channel partners)—plus a change-category lens (pricing model shifts, high engineering or partner effort, licensing vs. consumption, etc.).

Because bottoms-up attempts had stalled, we secured top-down leadership alignment (spurred by our new CMO) on the final criteria and number of tiers. We then road-showed the framework broadly—not only to marketing and product but to sales, customer success, partnerships, pricing, strategy, and BizOps—to catch missed impact levers. With criteria locked, we mapped tactics to each tier according to first principles (audience size and reach required, resource intensity) rather than channel checklists, built Confluence playbooks per tier that linked ownership, self-serve assets, and process, and committed to an annual refresh cadence so we wouldn’t overhaul the system after every hiccup. For the smallest “micro-launches” (tier four) we created lightweight, high-authenticity plays: empower PMs and engineers to post personally on social with message-house guidance and visual libraries, swarm engagement from peers plus the Atlassian organic handle, slot them into ongoing programs such as monthly Demo Den videos paired with community AMAs, community feature round-ups, and newsletter spots, and occasionally bundle several micro-updates into a single higher-tier moment.

We housed the tier definitions, decision criteria, and detailed playbooks in Confluence so every team could self-serve. Internal blogging and short Loom recordings after launches became our standard way to share creative, press coverage, and shout-outs. For micro-launches we leaned on existing visual/icon libraries, product-tour screenshots with dummy data, LinkedIn and community posts, the Atlassian organic social handle (approximately 2 million followers), YouTube-hosted Demo Den videos, and community series. We also began exploring generative AI and agents to draft tier recommendations, work-back plans, announcement copy from the message house, and social variants.

We now operate from a single, leadership-aligned tiering framework with clear shared language and playbooks. Product managers understand why a given release lands in a particular tier and still feel supported—even on the smallest updates—through authentic employee advocacy, Demo Den slots, community amplification, and bundling options. Cross-functional groups (sales, ecosystem, CS, pricing) are looped in early, reducing surprises. We protect both internal bandwidth and audience attention by matching investment to real impact, while the annual review cycle keeps the system current without constant overhauls. Trust between PMMs and PMs has measurably improved because every launch, no matter how tiny, now has a defined, respectful path to market.