I think a partial, but substantive explanation is related to fragmented domain expertise across the stakeholder base and lack of ownership of the vision of what the stack is meant to achieve. The recent blog post from the Lago folks about why they exited the no-code reverse ETL space discusses parts of this problem [1].
> Marketers often already have access to data, at least in ‘read-only’ mode, and can download it in CSV format. They don’t really explore their options, not because they would need to learn SQL (no need with spreadsheets), but because this would require them to study the whole data structure of the company.
A database usually contains dozens or hundreds of data tables, and understanding how they are organized, how they relate to each other and how often they are updated is a huge effort. Therefore, they say they want to be more data-driven, but they rarely acquire the knowledge that is required to do so, because the bar is pretty high and because this would add up to their existing workload
The inverse observation here I believe is also relevant and rings true. Engineers often don't have have the marketing/sales/analytics/business domain context to make decisions that inform optimal infrastructure decisions. There's a bidirectional dog-piling effect that just gets worse over time.
My own personal experience has led me to believe that this is largely an ownership and governance issue. It's not enough to just give marketers access to the data warehouse, and it's also not enough to sync up with engineers about KPIs and OKRs on a weekly basis. The result of that is the equivalent of a kids soccer game where everyone is chasing the ball rather than playing their positions as a team.
Adding tooling complexity on top of all that, pressed into the service of fixing "pipeline woes", compounds the problem substantially.
[1] https://www.getlago.com/blog/why-we-moved-away-from-the-no-c...