How do you approach documentation and knowledge sharing in an operations team?

Documentation is where operations teams most commonly fail, so a considered answer stands out.

• Write it for the person on call at 3am, not for an audit. Runbooks with exact commands, expected output, and what to do when it does not match. Prose explaining the architecture is separate and less urgent.
• Document at the moment you solve something. A fix written up while fresh takes ten minutes; reconstructed six months later it takes an hour or never happens.
• Keep it where people look. A wiki nobody opens is worse than nothing because it creates false confidence. Linking runbooks directly from alerts is the single most effective practice.
• Test the documentation. Have someone unfamiliar follow the runbook. Gaps surface immediately.
• Prune aggressively. Out-of-date documentation actively causes incidents.

On knowledge sharing: rotate who handles which type of ticket so knowledge does not concentrate in one person, review incidents as a team, and treat any system only one person understands as a risk to be scheduled away.

Note: Saying you would rather automate a procedure than document it — because automation cannot go stale unnoticed — is a strong closing point.