nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Does anyone else feel Jira gets harder to manage as more teams get involved?

Pallab_Empyra.com

I've noticed this on a couple of large delivery programs recently.

Everything works fine until you have several teams working in parallel, dependencies everywhere, approvals, testing, and different stakeholders trying to stay aligned.

That's usually the point where things start getting messy.

Curious if others have experienced the same. What's been the biggest challenge for you when Jira has to support a large cross-functional program?

Comments

Maria Reisinger _MetaFrazo_

Absolutely. In my experience, Jira itself usually isn’t the problem. Complexity grows as more teams, workflows, approvals, automations, and dependencies are added over time. Small configuration differences can gradually turn into operational blind spots.

The real challenge is often visibility. If you can’t see where workflows are drifting, approvals are being bypassed, or processes are becoming inconsistent, it’s difficult to react before those issues start affecting delivery.

I’m a Co-Founder of MetaFrazo, so I’m naturally looking at this through that lens. This is exactly the challenge we’re focused on, helping organizations make operational complexity visible early, so they can respond before it turns into a governance or delivery issue.

I’d be interested to hear what others experience first. Is it workflow complexity, configuration drift, reporting, or simply coordinating across many teams?

Calogero Bonasia

ciao @Pallab_Empyra_com
I’ve encountered this problem several times over the years, especially in large programs involving many teams, dependencies, approval flows, testing stages, and different levels of management.
In my experience, Jira itself is rarely the real source of complexity. The difficulty usually appears when the underlying organizational model has become unclear: ownership is fragmented, workflows have grown independently, terminology differs across teams, and reporting expectations are added without a shared governance model.
At that point, Jira becomes a very accurate representation of the organization’s complexity.
I’m actually writing a book about my experiences with Jira, project governance, and large organizational environments, including cases where the tool gradually became the place where unresolved process and responsibility issues accumulated.
After more than twenty years working with Jira, I think the most difficult question is still the same: how much complexity should Jira represent, and how much should the organization resolve before configuring the tool?