They don't even follow the docs that they have, and they certainly don't update them when they notice errors or omissions. In some cases, I've witnessed them performing a task that is documented on a Wiki page (last updated: 2016!), but they skip some steps, perform others differently from the doc, and do things not covered in the doc at all. When I asked why they don't update the docs, they respond with claims of "it's not my doc" or "it's owned by Team X" so they can't change it.
They rarely describe the solution for bug fixes in the Jira ticket and instead just declare it fixed and pass it to QA so the knowledge stays with the person that fixed the bug. They've even refused to share their screen during live debugging sessions and instead just loosely describe what they're doing in words.
How can I foster a culture of information sharing?
* natural human tendency for us to become curmudgeons
* you may be involved in a conspiracy
Curmudgeons
Consider yourself, how do you feel during first week of a new job? Like you can do anything and your eager to go out of your way to make it all perfect?
Or the last week of a job you respect, when you wanted to make sure you’ve left nothing hanging?
And the long interim in between? The daily grind, the now familiarity, comfort zone dividing what is expected and responsible for you, and how not to get caught up in “extra work”.
Psychologically unlocking this human capacity for change may require reshuffling the org, or a incentive level redirect of priorities.
Conspiracy
Worth mentioning (about humans). What causes conspiracy? Job security and haters to name a few. Solution? Reshuffle the org as appropriate.