Historically, Jira has catered to those with more technical software backgrounds. However, we’ve recently started moving Jira to be more open to non-technical users in terms of design and content.
To understand what this looked like from a content perspective, I wrote a report that examined how:
- we currently use language in Jira (specifically Plans because it’s my corner of the world)
- that language excludes non-technical users
- we can fix the language to appeal to all audiences and
- these recommendations align with product design and strategy
I also recorded a fake podcast to increase engagement. That’s just show-business.
I used the concepts in this piece to outline why certain work items pose a higher value to us in terms of design prioritization. These concepts have gotten enough buy-in from stakeholders on projects that my work has been added to their roadmaps. I have to be vague as to what those projects are, for now.
Beyond that, other designers have also cited the ideas and goals in this page in sparring, leadership reviews, and design explorations.
Listen to me read it
(in a fake podcast format):
Read for yourself
(and miss my dulcet American accent):