Appreciate your input. Perhaps it is seen as a waterfall way of doing a things. Personally I would write it alongside building the system, then continue to evolve it as the architecture matures. It does not need to be a case of writing everything down first before building things. Although it might be cheaper to change the words in the document compared to destroying Infra and rebuilding it!
This can then be used to show customers or auditors that we have been diligent and designed the system carefully, even if they find some flaws.
This is an interesting perspective that I hadn’t considered.
My colleagues all seem happy in their roles, although they work in countries with less workers rights/securities(?) than in my own country. Maybe they don’t document anything so they are seen as “sticky”.
However I do wonder how they would feel if they were blocked from taking a new internal role because they’re deemed too essential, because they’ve not documented anything.