Jira Milestones

A new milestone feature to help teams work towards incremental goals and stay on track

My role

Solo designer. Conceptual project, not affiliated with Atlassian.

Timeline

8 weeks

the problem

Teams have difficulty delivering work on time

As a product manager, I noticed how my team and other teams can end up rushing to meet the delivery date for a project or having to delay it after the initial planning phase. This sparked the question - why was there a disconnect between the original plan and execution?

the solution

Improving visibility and defining incremental goals

Jira Milestones is a conceptual feature in Jira which allows users to break up large projects into Milestones, or value drops, and track it's progress against a timeline.

user insights

Teams are more likely to succeed when they give more attention to a project

My target users were product and engineering as both groups need to work closely together to deliver a project. I conducted interviews with people from both roles and asked them questions to understand why they succeed at delivering some projects versus others and organized this data into insights.

How might we help teams better manage large initiatives so they can meet expected delivery dates?

translating user needs to key features

Incorporating a new feature into an established product

So, why Jira?

  • Both Product and Engineering already use Jira on a daily basis so this avoids going on a different platform
  • Relevant to the work being done in Jira
  • Contains ability to quickly update timelines and track history of changes

information architecture

Defining Milestone navigation

The information hierarchy was developed based on my research of how product and engineering use Jira while keeping in mind Jira's design systems, meaning granting users various access points.

testing & explorations

Improvements to my design

Optimizing for engagement

The initial design required a fair amount of reading with fewer visual cues. This leads to a lack of scannability therefore defeats the original goal of having Milestones in the Active Sprint for guided visibility. After testing a few iterations, I landed on a more visual design which contains a dedicated Milestone section and symbols to communicate whether a date has passed or a Milestone has been completed.

Removing inconsistency

The initial design contained a popup that would appear after marking a Milestone as "complete". However, this is inconsistent with Jira's design systems of being unobtrusive, so I removed this feature.

the final product

Blending in as an Atlassian product

When building the high-fidelity wireframes, I referenced Atlassian's design systems to ensure my design was consistent with their design standards. In order to speed up the wireframe process, I took screenshots of Jira's actual pages, adjusted the image's transparency, and "traced" over the image in Sketch.

The Milestone Overview feature are an extension of Jira's Roadmaps. Milestones are different than a Roadmap item in the sense that it's more integrated with the Active Sprint and Backlog, which is what engineers interact with on a daily basis.

learnings & next steps

Managing the complexity of Jira

This was my first project where I was incorporating a new feature into an existing product. I learned a lot about design systems (specifically Atlassian's), the importance of following a company's design systems, and how amazing it is for companies to establish them. Here are some other things I learned and what I would work on next.

  • Balancing needs of multiple user groups. As a product manager previously, at times it felt like I kept that user group in my mind a lot more than engineers during this project. In order to ensure my design was really going to solve the defined user needs, I had to remind myself to remember I was also designing for engineers and check if my design decisions addressed that user group.
  • Iterate on Milestone display. Looking back, I think the Milestone section in Backlog and Active Sprint view can be more engaging and intuitive. The challenge is optimizing for the right amount of information while remaining informative. I'd approach this by revisiting what information users absolutely need to meet the user goals and look for UI inspiration online.