I don't know, it could be interpreted both ways. FWIW, in my current job, documentation is plumbing I tend to own, even though it really is supposed to be a col

I don't know, it could be interpreted both ways. FWIW, in my current job, documentation is plumbing I tend to own, even though it really is supposed to be a collective effort to improve it. There are people in my team that will be quick to say documentation is "adequate", even if it's missing some implicit knowledge. Rather than sulking and running sociopathic "experiments", I've found it to be more effective to keep advocating for more attentiveness to docs (by discussing it as a task prioritization item with the team, by setting examples, via code reviews, etc). If you continuously call it out when people drop the ball, and give constructive feedback when they attempt to take on the task in earnest, you gradually see better results.