> And what I've found is, this doesn't make people read your documentation. What it does is it makes people stop asking for it. Hence my belief about it being a ploy more than anything else, again, perhaps not consciously, but in effect.
I can't say it always stops people for asking them. Even when they've commented on the documentation when it was shared, even when the conversation started around a link to the documentation, I've found people one month in when it's time for them to do something ask for documentation with the implication there is none, and if you provide it in the meeting where they're trying to prolong the process they just insist they need time to review it despite having had at some stages a month to do so (or having left comments that at least indicate they already did)
I can't say it always stops people for asking them. Even when they've commented on the documentation when it was shared, even when the conversation started around a link to the documentation, I've found people one month in when it's time for them to do something ask for documentation with the implication there is none, and if you provide it in the meeting where they're trying to prolong the process they just insist they need time to review it despite having had at some stages a month to do so (or having left comments that at least indicate they already did)