External collaboration
When Atlassian's paid licensing model for external guests sparked community backlash, I turned that friction into a strategic pivot — advocating to shift from monetization to virality, expanding projected reach from ~40% to ~90% of users.
The problem
The Guests in Confluence Premium early access program launched in June 2021. Community feedback quickly surfaced strong resistance to the paid licensing model. What looked like a pricing complaint was actually something deeper: the licensing structure was limiting who could benefit from the feature at all.
The paid model projected to serve only ~40% of users. A license-free, single-space model could reach ~90%. That gap was the strategic opportunity.
Research and advocacy
I researched customer pain points and built empathy journeys focused on a critical but underexplored scenario: auditing guest access. Enterprise customers needed confidence that external collaborators could be tracked, managed, and removed — the licensing model was noise on top of that underlying trust concern.
Armed with this research, I made the case to product leadership for a license-free, single-space approach for the Beta. The argument wasn't just about usability — it was about business impact: virality, expanded reach, and long-term retention. This directly aligned with Atlassian's core value of not harming customers for commercial gain.
Design impact
The hairy constraint of a clunky permissions model had dependencies on 3 adjacent teams - Identity, Team Work Platform, and Confluence backbone. So I blogged about my design thinking, provoking follow-on chats with multiple teams. The experience changes shaped not just the Guests Beta and GA releases, but became foundational patterns for how Atlassian approaches trust and governance for external users across the platform. The audit and access management flows I designed were referenced as the cross-product starting point for future external collaboration work.
Outcomes
The pivot from monetization to virality changed the trajectory of the feature. The trust and governance patterns established here were carried forward into Atlassian's broader platform strategy for external collaboration — making this project foundational beyond its immediate scope.
