OVERVIEW
This project was a hackathon winner. I worked on this for the second and third week of my 12 week internship at Atlassian, concurrent to my main internship projects.
We came first in 2 of 3 categories within Atlassian’s Growth team! 🏆🏆🥳 (Product Prize & People’s Choice)
While ‘Up-Flow’ is the idea of getting customers to pay for the next tier from the pricing plans, ‘Cross-flow’ is about getting customers to acquire another product within the product ecosystem.
e.g. getting customers who are using Jira Software to add and start using another product like Confluence or Jira Service management.
What is One-Button Crossflow?
One-Button Crossflow is a feature we built that allows users to add another product from Atlassian’s ecosystem with one button (or as few steps as possible). We noticed that there were a large number of screens that our users had to go through in order to add another product, and we felt that this was part of why so many users would leave the flow before adding another product.
ROLES/SKILLS
TOOLS
Competitive analysis, Prototyping, Negotiation, Usability testing, Pitching
Figma
PERIOD
TEAM
2 weeks
Farhan Khan (Myself),
Brian Leung (Engineer),
Katia Mercuri (Engineer),
April Lipson (Content Designer)
Discover
Background
Atlassian runs plenty of internal hackathons (ShipIt, InnoWeek and InnoSprints) in an effort to foster collaboration, creativity and generate new ideas within the company. Some of Atlassian’s biggest products such as Jira Service Desk (Now Jira Service Management) have come about because of these hackathons.
I was lucky enough for the innovation sprint to happen during weeks 2 and 3 of my internship, right in the midst of my onboarding. This allowed me to allocate a bit more headspace to this project than if it occured later on during my internship
The Problem
Many users would stop half-way when adding another Atlassian product. Our users would open the switcher, click to add a new product, and click through a large number of screens before dropping out.
We think they dropped out because there are so many screens they need to go through in order to add a new product.
The switcher is found at the top left of the header of well-known Atlassian products. It is used to switch between different products the team is using.
There are product reccomendations in the switcher for products which the user do not own yet. This is how many of our conversions begin.
Once clicking on a reccomendation, the user would have to click through more than 9 screens, not accounting for loading times within them to provision the product. As you might imagine, this is a huge pain for our users.
Our Solution?
One-button crossflow.
We felt that if we were to get rid of all (or atleast most) of this screens, and allow the provisioning of a product to commence with click of a single button, we would get far more conversions.
Now, a product reccomendation appears within a card with an option to add immediately, or learn more.
The decision to add a card is data-driven, It provides options for users who are familiar with the product and are rushing to add it, as well as those who are unsure and would like more information.
Now, provisioning happens without taking the user away from their work like it used to. The provisioning product appears alongside added products, albeit greyed out to communicate the visibility of system status.
Brian and Katia were able to confirm and ship the feasability of this feature.
⚠️ Want to see my process? ⚠️
This is an industry project, and I can’t show everything here sadly 😔. So if you’d like to see more about the process (which includes research and how I got to my solution), please contact me! ⬇️⬇️⬇️⬇️⬇️⬇️⬇️