If you have good teams basically all you need is a thin layer of process that prevents total chaos, kanban is a good fit for that, but most teams implement kanban in a cargo cult manner.

I've worked on sales driven teams where I fundamentally trusted the sales guy because when he said if you make feature X I can sell it for $Y dollars and we made bank doing that.

Conversely I've worked on teams where everyone was trying to avoid being fired and would only make decisions that were defensible, eg. company X is doing Y so lets do Y, resulting in the usual follow the leader failure.