The tool (Jira) is not the problem. The "tools" (aka PM and process people) are the problem. In my experience, the people who are given the responsibility and

The tool (Jira) is not the problem. The "tools" (aka PM and process people) are the problem. In my experience, the people who are given the responsibility and power to build "systems" and processes are usually least qualified to build the said system as they usually have no experience in and understanding of what it will mean to be working under the system. This is akin to the customer vs. user dichotomy in software development, where things are build for the customer with often detrimental consequences for the actual user. In considering tools and processes, I believe in discussing each individual decision and process step to death by considering secondary and even tertiary consequences. Yet people making such decisions are not in a position to evaluate such consequences since they have no such understanding, capability, or desire. This would make decision making slow when enforcing tools to an entire development organization. But, decision making should be slow and deliberate. Otherwise, as I have seen in my own company, we would be jumping from tool to tool per the latest fashion of the day. I've also seen this with the mess of WebEx, Zoom, Teams way of having online meetings, where tools keep changing for the sake of some perceived benefits with no real clear improvements.