> I can not understate how hard it is to get engineers to read a scope document, ...

Ironically, it is hard because it doesn't consider the user. Scope documents likely seem reasonable for the author living in their own little bubble, dismissing it as something "trivial", but if they actually had to use it like those on the receiving end they would soon realize how horrid and ill-conceived it is. Much like was learned in the original link, once you stop with the bad practices, things become much easier.

For my scope documents I spend hours questioning users and validating each step and asking “why don’t you just…?”, and try and boil that down.

Doesn’t matter if you drive VS Code every day though, because that means You Know Better (tm), and to hell with the discovery process.

I actually wouldn’t have a problem with pulling engineers into those discovery exercises directly, except when I have, they’ve just refused to engage. Come out without asking many questions and seemingly haven’t listened to a thing.

It’s like engineers just think it’s all beneath them, (and I accept I was a bit like that when I was engineering), so forcing them to do the calls isn’t an awful idea.