Two products in Atlassian’s suite, Bitbucket and Jira Software, works together to enable software teams to plan and build products. They are often used together, but could not be purchased in one flow.
The Bitbucket team had a goal to increase monthly active users, and this project will help improve product bundling, sign-up and product integration, ultimately leading to increased stickiness.
There is no one place to direct customers when marketing the benefits of the integration. Customers are likely to be convused and less likely to successfully purchase both products.
Increased co-purchase of Jira Software and Bitucket, Increased cross-acquisition from Jira Software to Bitbicket.
Enabling this functionality required updates to multiple services owned by different teams. I helped facilitate the conversations across different product teams (Bitbucket, Jira) and service teams(Provisioning, Payments). Ironically, my own development team had the least amount of work, as we owned the ‘button’ on the customer-facing site. I remained the owner of the overall project that saw through the dependencies, removed roadblocks and facilitated decision making between all of the stakeholders involved.
This was necessary for several reasons:
First, updates made to the purchase flow almost always result in a short-term dip in conversion numbers, and we need to give our business analyst team a granular breakdown of changes to the site.
Second, there was both a update in the layout of the page as well as major new functionality and it was important to isolate the effects of each.
Finally, we used it to build in time to make changes once we saw how users behaved on the live site.