Hi everyone!
My name is Sam Ugulava and I am a Senior Product Manager working on Jira Align.
Recently, we announced a rather lengthy list of Jira Align capabilities that we plan to remove over the next several quarters. For more information, this page outlines the timeline, specific pages, and process for this effort.
Unshipping is an important step in our product strategy, but we know it can set a few alarm bells off without knowing the “why.” As a team, we believe it’s important to share the strategic thinking behind this effort and re-emphasize that Atlassian has doubled down on its investment in Jira Align. In this post we want to share two things:
-
The strategic thinking behind the upcoming removals
-
How to give feedback if any part of this plan would negatively impact you
Why these removals?
Our Product team truly builds solutions in collaboration with customers: product managers meet with customers weekly; every team offsite includes at least one customer visit; we recently started bringing entire R&D teams to customers' offices to understand their unique needs and use cases.
In these conversations, we often hear our customers say that Jira Align is complex with a steep learning curve. The complexity of Jira Align is in part due to the sheer volume of functionality in the product, so in June, we began a product-wide data analysis to identify low-usage, low-value components. This analysis resulted in the unshipping list linked above. Our goal is to make it easy to find and use the most important features while up-leveling Jira Align’s overall user experience.
What to do if any of these features is critical to your workflow
While we’re confident these removals should not disrupt your existing workflows, we have a robust removal process which includes time to share feedback if you feel a feature should not have been included.
If you have any questions or comments on these upcoming changes, please reach out to Jira Align Support, your Jira Align partner or your Enterprise Solution Strategist.
0 comments