Devs struggle to plan for read/write workloads. Making more indexes can then make the same inbound volume from the previous day require n more writes per row.
You can still get surprised by query optimizations on relatively simple joins just changing query strategy when hitting tuning parameters.
Making analyzers more visual and giving lots of suggestions (that could then be ignored) would b a good intermediate step.