While you don’t often see the strategy, it defines your execution. It tells you how to speak the language of your customers and your products simultaneously, what words to use, and what matters most in an interaction.
Without this roadmap, you’re just writing random words.
On this page:
• Writing for non-tech teams
• New navigation EAP strategy
Writing for non-tech teams
Jira was made by developers for developers, but to engage a wider audience, it needed to be simplified.
To achieve this, I:
• evaluated the language and structures found in Jira
• aligned these with the user personas of our current and target audiences
• defined recommendations that aligned with our product design and strategy
This page didn’t produce any direct outcomes, but was successful in:
• prioritising simplification projects in Plans as well as in Jira at large
• influencing future content and product decisions and
• it was cited by other designers to justify future design decisions
New navigation EAP strategy
To validate that our new navigation design was an improvement over the old, I gathered feedback from users then refined the experience before migrating all customers into the new experience.
To achieve this, I:
• defined key points of the user journey throughout this Early Access Period
• presented work to stakeholders to get resourcing and
• triaged and prioritized feedback to solve most impactful design-related issues
This Early Access Period was a success in that it led to:
• usability issues raised by customers that were solved before larger rollout
• improved customer reception of new navigation
• widespread rollout to all users – see New Navigation Onboarding tour
What’s shared below is documentation from that process. It includes:
• the metrics by which we measured success
• an exploration of whether another competing rollout might interfere with this, including usage statistics and timeline comparisons
• recommendations about what actions to take