The bulk of my experience has been on Plans in Jira, a tool that helps organizations effectively plan work across multiple work streams and monitor progress towards deadlines.
Through my content work, I’ve helped Plans grow to a key part of our Premium and Enterprise offerings used by companies like Ford, Visa, and NASA.
And while it’s been daunting at times, I’ve had the opportunity to solve complex and high-impact problems that I wouldn’t have gotten anywhere else.
Over my time at Atlassian, I have:
- updated the copy in a product developed by third-company to match that of Jira, including adopting new terminology
- simplified language and concepts to make Plans/Jira accessible to a wider audience
- driven conversations and decisions about our Content standards and how we apply them
Lastly, I’ve owned and adapted the Plans documentation throughout this journey. To this end, I have:
- audited and revised the IA to meet changing product strategies — twice
- written content for new features and revised existing content as those features changed
- done so in a way that’s accessible to users of all reading levels
Examples
New Navigation Early Access Strategy
To validate that our new navigation was an improvement over the old, I was tasked with creating an Early Access Period plan. Through the feedback and interactions, we would then refine the experience before migrating all customers into the new experience.
Writing Interfaces and Experiences for Non Tech Teams
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. I explored what this means from a Content Design perspective.
The New Navigation Onboarding Tour
New users can view a multi-step spotlight tour that covers the basics of the tool and highlights the features. I capitalized on the chance to rewrite the content of the tour to be more human and interesting.
Top-Level Planning Template
Making a plan in Jira can be complicated. To make to easier for new users, I designed a basic plan builder template that prioritized the information new users needed to know while also helping them setup one of the key features of Plans: extra hierarchy levels.
New Feature Docs – Program Board
The Program board is a planning interface that aligns to the concept of PI Planning in SAFe methodolgy. While also helping create the feature, I wrote the documentation that describes the product and specific functionalities planners will find helpful.
The Case for Retiring ARJServer
Advanced Roadmaps used to have an old interface called Live Plans. I made the case that, years after the last version of it shipped, we should close our old documentation site that we were keeping open for that content alone. I did so by demonstrating how our reasons for keeping it alive were no longer relevant, then quantified the size of the customer impact.