You kinda need to impose process for large projects, and know where you are. The engineers are free to show a better tool for the job.
> I think Jira does a good job of making teams look much busier than they are, but in the end I see it more as a “talk more not do more” situation.
It does not make teams looks busier, it shows that teams are a lot busier in reality, which is valuable information.
> The Alternative
> Although a potential downside to Linear is that it is built explicitly for engineers, thus may not be suitable for other teams such as marketing, design, etc.
And this is why engineers will never build any viable alternative to Jira, because there is this us vs. them mentality. Issue management tools need to work for the whole organisation, that's why Jira is still the gold standard.
> If you’ve given Linear a try, but it just doesn’t work for you, some viable alternatives include GitHub Issues, Asana, ClickUp, YouTrack, Trello, Pivotal Tracker, and monday.com.
None of these are viable in larger organisations, they are fine for small projects, but you would have a lot of trouble with them in an enterprise context.
Jira's web UI can be very annoying, however an alternative to Jira would need to be at least as customisable and familiar as Jira, otherwise no large team will ever adopt it.