It seems too reductive to say that good engineering strategy is boring, but bad strategy can certainly come from chasing new and exciting. Strategy doesn’t have to be clever, or a unique take on some existing process, or even exceptionally innovative. It can just work, and that’s ok.

Good software engineering strategy is often short changed for immediate return instead of long term focus/gains.

Frequently this is because of mismatches between engineering discipline vs. non-engineering discipline approaches.

Different people find different things interesting or boring. I don't think there's anything that can just be called "boring" (or the opposite) in a blanket sense.