u/Hour-Two-3104

I’m at the point where I genuinely dont know if the problem is the tools or just what happens when agile teams scale past a certain size. Right now we are struggling with this weird middle ground where simple tools stop working but heavier tools slowly kill flexibility.

Trello style boards are nice at first because everybody actually uses them but once you start having multiple teams, dependencies, shared resources and roadmap planning, everything becomes labels, workarounds and wait which board is the real source of truth? moments.

Then you move to something more enterprise and suddenly the opposite problem appears. Too many workflows, too many fields, too much updating, too many layers between work happening and work represented in the system. Feels like the tool slowly turns the team into administrators.

Main things we are struggling with currently: seeing dependencies across teams without building giant Gantt monsters, keeping backlog/workflow simple enough that engineers dont hate updating it and roadmap + day to day execution living together in a way that actually makes sense. What I DONT want is another system that looks amazing in demos but turns into process gravity 6 months later.

What agile teams here are actually using long term once projects become more complex?

We used Trello for quite some time because it was simple and everybody understood it immediately but once projects became more complex it started falling apart. Too many boards, too many labels, too much manual stuff just to keep visibility.

Then we moved to Jira because everybody said this is what serious teams use and honestly… maybe too serious. Powerful for sure but after some months it felt like we were spending more time maintaining workflows and statuses than actually managing projects. Half the team hated opening it.

Tried ClickUp too and I wanted to like it but it just became overwhelming really fast. So many options, views, hierarchies, automations etc. Felt like everybody was building their own version of the system and after a while nobody really saw the same picture anymore.

Now I’m kind of stuck in this weird middle where simple tools become chaos when things scale, but enterprise tools start slowing everybody down. Main thing I need is: clear visibility across projects, dependencies, not too painful to update daily and enough structure without becoming process for the sake of process.

Would honestly love to hear what people here actually use long term because right now every tool demo looks amazing until real work starts happening inside it.

Trying to improve the way we handle dependencies because right now it still feels more confusing than it should be once projects get even slightly complex.

We have dependencies documented, technically everything is tracked but in practice it’s still hard to quickly understand what blocks what and which delays will actually affect other work.

I’ve tried a few different setups already, timelines, linked tasks, dependency maps, even color coding stuff but none of it really feels clean once there are many moving pieces and multiple teams involved.

Would honestly love some inspo from people who feel like they found setups that actually work in real life. Screenshots/examples/workflow ideas would be super interesting.