ATLASSIAN ADMIN LAUNCHPAD
RESPONSIBILITIES
UX / UI / Interaction Design
Qual & Quant Research
Early Signal Testing
Project Management
ATLASSIAN ADMIN LAUNCHPAD
RESPONSIBILITIES
UX / UI / Interaction Design
Qual & Quant Research
Early Signal Testing
Project Management
The Launchpad is a unified admin hub where the user will be able to ideally navigate through all the sites and products on their domain in one location.
The Launchpad is a unified admin hub where the user will be able to ideally navigate through all the sites and products on their domain in one location.
WHAT IS THE GOAL?
WHAT IS THE GOAL?
WHAT IS THE GOAL?
Our primary business goal was provide a clear link between sites and orgs in order to effectively monetize security features as part of Atlassian Access. The user need we were solving was to make it easier to understand the relationship between Organization (the umbrella) and Sites (the instances and products), a notion that was necessary but completely misunderstood or unknown. We set out to have a few high level goals:
Unify the navigation between sites and orgs
Make it easier to link a site and an org together
Help users understand how their sites and orgs relate to one another
Nurture potential security feature customers throughout the entire funnel from site admin to org creation to domain claim to Atlassian Access purchase
Our primary business goal was provide a clear link between sites and orgs in order to effectively monetize security features as part of Atlassian Access. The user need we were solving was to make it easier to understand the relationship between Organization (the umbrella) and Sites (the instances and products), a notion that was necessary but completely misunderstood or unknown. We set out to have a few high level goals:
Unify the navigation between sites and orgs
Make it easier to link a site and an org together
Help users understand how their sites and orgs relate to one another
Nurture potential security feature customers throughout the entire funnel from site admin to org creation to domain claim to Atlassian Access purchase
WHAT IS THE PROCESS?
WHAT IS THE PROCESS?
WHAT IS THE PROCESS?
Atlassian has a concept of a Triad which is essentially a group consisting of the Designer, Product Manager and Engineering Manager. The triad, through a collaborative process, establish a high-level product vision and the long-term roadmap for the product.
This project was so big and involved so many stakeholders that every micro detail was gone over dozens of times and communicated continuously with all the teams. At a macro level, there were three major components (and lots of smaller parts),
The Organization and Site connection/linking (a necessity for SCIM User Provisioning that was being worked on concurrently)
The unified admin Launchpad (which served as the new landing experience after all sites were migrated to one place)
The Organizational overview page (the page where all Sites that were connected/linked to that Organization would show up)
Atlassian has a concept of a Triad which is essentially a group consisting of the Designer, Product Manager and Engineering Manager. The triad, through a collaborative process, establish a high-level product vision and the long-term roadmap for the product.
This project was so big and involved so many stakeholders that every micro detail was gone over dozens of times and communicated continuously with all the teams. At a macro level, there were three major components (and lots of smaller parts),
The Organization and Site connection/linking (a necessity for SCIM User Provisioning that was being worked on concurrently)
The unified admin Launchpad (which served as the new landing experience after all sites were migrated to one place)
The Organizational overview page (the page where all Sites that were connected/linked to that Organization would show up)
BUT WHAT IS THE DESIGN PROCESS?
BUT WHAT IS THE DESIGN PROCESS?
BUT WHAT IS THE DESIGN PROCESS?
The design process was broken down into a variant of the design thinking process for each of those phases listed above (details can be seen in the screens)
Discovery Phase (summarize past research, gathered and analyze existing data, document current state through confluence, had dozens of whiteboard sessions, kick-offs, etc)
Ideation Phase (Explored the problem space, concept sketches, low fidelity wireframes, early signal testing, begin scheduling customer interviews, in depth stakeholder feedback and sparring, etc)
Refine Phase (Test prototype in front of customers for insights, finalize design based on stakeholder & customer feedback, prepare designs for dev handoff)
The design process was broken down into a variant of the design thinking process for each of those phases listed above (details can be seen in the screens)
Discovery Phase (summarize past research, gathered and analyze existing data, document current state through confluence, had dozens of whiteboard sessions, kick-offs, etc)
Ideation Phase (Explored the problem space, concept sketches, low fidelity wireframes, early signal testing, begin scheduling customer interviews, in depth stakeholder feedback and sparring, etc)
Refine Phase (Test prototype in front of customers for insights, finalize design based on stakeholder & customer feedback, prepare designs for dev handoff)
↳ DISCOVERY PHASE
This was the most complicated project I'd encountered during my time at Atlassian. I was 3 months in and there was so much domain knowledge to acquire along with product, legacy and tech debt to understand. I had many whiteboard gathering, understanding and kick-offs. During this phase I also collected all quant and qual research to begin forming a hypothesis.
This was the most complicated project I'd encountered during my time at Atlassian. I was 3 months in and there was so much domain knowledge to acquire along with product, legacy and tech debt to understand. I had many whiteboard gathering, understanding and kick-offs. During this phase I also collected all quant and qual research to begin forming a hypothesis.
Quantitative Data (summarizing product & platform data)
Quantitative Data (summarizing product & platform data)
Qual data (collecting customer feedback theme through Confluence and customer interview insights through Dovetail)
Qual data (collecting customer feedback theme through Confluence and customer interview insights through Dovetail)
Whiteboarding (conducted triad whiteboard working sessions to align on goal, problems, dependencies and constraints)
Whiteboarding (conducted triad whiteboard working sessions to align on goal, problems, dependencies and constraints)
↳ IDEATION PHASE
This project was so big with so many moving parts and components, that I zero'ed in on one journey first, the most complicated journey, which was "adding a site to an org" for User Provisioning. I then designed an end-to-end wireframe of the journey as a kick off point for discussion with my immediate team. Once I landed on the UX, I ran some early signal testing to validate comprehension, discovery and task completion. I did this for every moving part of the Launchpad.
This project was so big with so many moving parts and components, that I zero'ed in on one journey first, the most complicated journey, which was "adding a site to an org" for User Provisioning. I then designed an end-to-end wireframe of the journey as a kick off point for discussion with my immediate team. Once I landed on the UX, I ran some early signal testing to validate comprehension, discovery and task completion. I did this for every moving part of the Launchpad.
Wireframes (I designed the most complicated user case for user provisioning as a kick-off to identify constraints and dependencies as soon as possible — this method allowed a kick-start for the team deep dive and answer technical questions)
Wireframes (I designed the most complicated user case for user provisioning as a kick-off to identify constraints and dependencies as soon as possible — this method allowed a kick-start for the team deep dive and answer technical questions)
Early Signal Testing (once I landed on the UX, I ran some early signal testing to validate comprehension, discovery and task completion. I did this for every moving part of the Launchpad)
Early Signal Testing (once I landed on the UX, I ran some early signal testing to validate comprehension, discovery and task completion. I did this for every moving part of the Launchpad)
↳ REFINE PHASE
After refining the UX in wireframes, I then put all the UI's into high fidelity designs. I created a prototype in inVision and put it in front of users to gather first impressions and perform basic tasks. Based on stakeholder and user feedback (a lot of micro and macro decisions), I finalized the designs and prepared them for handoff.
After refining the UX in wireframes, I then put all the UI's into high fidelity designs. I created a prototype in inVision and put it in front of users to gather first impressions and perform basic tasks. Based on stakeholder and user feedback (a lot of micro and macro decisions), I finalized the designs and prepared them for handoff.
High fidelity design flows (designed all use & edge cases and sparred with design and immediate team)
High fidelity design flows (designed all use & edge cases and sparred with design and immediate team)
User Feedback Testing (actual user testing & feedback from paying Atlassian admin testing prototype for new 0 to 1 feature)
User Feedback Testing (actual user testing & feedback from paying Atlassian admin testing prototype for new 0 to 1 feature)
Eng Handoff (Sketch to InVision / Zeplin spec handoff)
Eng Handoff (Sketch to InVision / Zeplin spec handoff)
CONCLUSION
The project, although encountered a few hurdles in terms of so many outside dependencies, hit it’s Q2 OKR date Australian quarter). Customer feedback was relatively positive as we resolved several of the user pain points (but not all of them, billing is still the overall biggest pain point and longer company overhaul initiative). We allowed Organizational admins to navigate all sites within their domains and Site admins to have quick access to their top tasks (add users to groups, deactivate users, adding groups, create groups, etc). The project was launch with positive review both internally and externally with users.
The project, although encountered a few hurdles in terms of so many outside dependencies, hit it’s Q2 OKR date Australian quarter). Customer feedback was relatively positive as we resolved several of the user pain points (but not all of them, billing is still the overall biggest pain point and longer company overhaul initiative). We allowed Organizational admins to navigate all sites within their domains and Site admins to have quick access to their top tasks (add users to groups, deactivate users, adding groups, create groups, etc). The project was launch with positive review both internally and externally with users.