From both a professional and an academic curiosity point of view, how can one tool be subject to so much hate and yet is the industry’s go to tool for issue management? The answer, something that took me awhile to understand, lies in how TPMs & PMs see the world versus how Engineers see it. Obviously - it is not the same.
I used to be a big believer in the "one tool, one source of truth" approach... but as organizations grow and needs evolve I now think you need tailored tools sharing data (truth) elegantly across the org. Jira tries to be all things to all people - but it ends up being not enough for anyone.
This post resonates so much with my thinking ! I sincerely believe that JIRA is getting that much hate because most companies have unrealistic expectations: there's no way to simultaneously be a good team collaboration tool, a good management tool, and a good reporting tool.
Sorry for the plug, but I wrote precisely on that topic here: https://www.echoeshq.com/post/the-ticketing-conundrum/. To your point, I think the solution will not be found in a single alternative, but in the ability to embrace the variety of tools that the builders have _chosen_ to operate with.
Can any tool live up to the expectations of being both good for collaboration and good for reporting?
Love it. That is exactly the thread I started pulling on. Very much enjoyed your take on this. Bingo on this point -> Where things break is when we start mixing in the needs of management and stakeholders.
I used to be a big believer in the "one tool, one source of truth" approach... but as organizations grow and needs evolve I now think you need tailored tools sharing data (truth) elegantly across the org. Jira tries to be all things to all people - but it ends up being not enough for anyone.
Yes, omg precisely. Well put. Wonderfully put.
This post resonates so much with my thinking ! I sincerely believe that JIRA is getting that much hate because most companies have unrealistic expectations: there's no way to simultaneously be a good team collaboration tool, a good management tool, and a good reporting tool.
Sorry for the plug, but I wrote precisely on that topic here: https://www.echoeshq.com/post/the-ticketing-conundrum/. To your point, I think the solution will not be found in a single alternative, but in the ability to embrace the variety of tools that the builders have _chosen_ to operate with.
Can any tool live up to the expectations of being both good for collaboration and good for reporting?
Love it. That is exactly the thread I started pulling on. Very much enjoyed your take on this. Bingo on this point -> Where things break is when we start mixing in the needs of management and stakeholders.
1000%. Great points especially the weaponizing.