This is the same argument as “why is software X so bloated when nobody uses more than 10% of the features?”
Because everyone uses a different 10%.
I write these documents too and I’ve watched people “read” them. They all do the same thing: flip to the conclusions and then if there is a need they will skim the section that’s relevant to their role.
The project manager cares only about the risks, costs, and time estimates.
The architect just wants to see the diagram and maybe check that the naming conventions have been followed.
Sysops just wants to know what they’re on the hook for after go-live.
None of them read the whole document, but the whole document ends up being read.
PS: I’ve found I have to take care of distributing documents myself. All organisations big and small are shockingly bad at disseminating information. Help them!
Because everyone uses a different 10%.
I write these documents too and I’ve watched people “read” them. They all do the same thing: flip to the conclusions and then if there is a need they will skim the section that’s relevant to their role.
The project manager cares only about the risks, costs, and time estimates.
The architect just wants to see the diagram and maybe check that the naming conventions have been followed.
Sysops just wants to know what they’re on the hook for after go-live.
None of them read the whole document, but the whole document ends up being read.
PS: I’ve found I have to take care of distributing documents myself. All organisations big and small are shockingly bad at disseminating information. Help them!