Designing for scale and performance: Jira configuration tooling

With the increased adoption of cloud tooling and low barriers to product expansion, products being created and managed by users outside of the IT department becomes a serious and costly management problem. Studies showed that 79% of IT admins believe the security of company data is at risk due to Shadow IT.

Admins are responsible for how their company utilises cloud software, they therefor need visibility into how their company utilises cloud software.

Company

Atlassian

Primary role

Product design

Year

2021

Password protected

Don't have the password? Get in touch

Process

I developed, outlined, and implemented the qualitative research process to evaluate user perceptions of performance between on-premises and Cloud products through discussions with representative users from participating businesses. Insights were looked at alongside quantatitive measures to form a holistic picture of performance and perceieved performance.

Additionally, I facilitated the understanding of the UX implications associated with transitioning to a scalable architectural model for managing issue data in Jira, as we shifted from one method of search to a new, more scalable search. This effort resulted in the creation of Principles and Guidelines designed to support multiple teams responsible for the migration between search methodologies and help them understand the expected user experience.

Outcome

  • Integrated customer experience feedback into an internal EAP for major clients.
  • Shared knowledge with peers on the nuanced understanding that performance experience extends beyond mere page load times.
  • Authored 'Principles and Guidelines for Eventual Consistency' that linked engineering decomposition efforts to their impacts on user experience, facilitating the onboarding of new designers to these insights.
  • Addressed the design requirements of four teams located in Gdansk (GDN) and Bangalore (BLR), scaling design support for engineers across different geographies.
This page helped me to learn that "performance" means much much more than just TTI [Time to interactive]

Software engineer using the Principles and Guidelines

Other work