In my former org we've started out with dev/engineering having different workflows and work types. We've ended up standardizing our workflows across dev/engineering because it enabled consistent reporting and kpis across these projects. If you have different workflows for systems that do same type of work, you have to measure these differently and then run into challenge of reconciling or comparing stats. We've also ended up standardizing most screens, because it reduced errors and learning curve for developers who worked on multiple projects or moved between teams.

I've worked with Asana, ClickUp and Azure Devops. Migrated all three to Jira also. Azure DevOps is less visually appealing and has the sterile sharepoint feel to it. It's also focused on DevOps, so it's not as versatile for non-sdlc related workflows. Teams who are locked into Microsoft ecosystem might use this because it's an easy choice within an existing portfolio. Asana's appeal is that it is simple. It has a very clean and easy to learn interface. Non-technical teams love it. Its very easy to spin up projects and a lot of teams end up using Asana as a task list. You can get fancy with automations, custom fields, integrations and the like, but it is nowhere as robust as Jira. Teams work in isolation in their projects, so it doesn't require the type of governance you normally want in Jira, because your changes are project-level. Asana is quite expensive for what it is, but it has a good reputation in the marketplace. Click Up is more Jira-esque and is appealing to both technical and non-technical teams, although I believe devs still lean towards tools like GitLab, ADO or Jira. Click-up might be a good solution if you have a mixed bag of teams and are cost-conscious. It feels more complicated than Asana, but I feel it can do more also. Between these tools I'd say Jira is the most feature rich with the widest marketplace app library. Atlassian also built a platform where Jira integrates well with other options like Confluence, JSM, Bitbucket and others. Microsoft's Azure DevOps is the closest to that, although I'd say the way Jira-JSM-Confluence-Loom flow together feels more cohesive than Azure/Power Suite.