How do I keep documentation up to date as systems change?
You have learned to document, which is more than most manage. The wall you have hit is a real one: systems keep changing, and keeping the knowledge base current feels like painting a bridge that never stops rusting. The work is never done, so it feels like failing. Stop measuring against perfect and current. No knowledge base is ever fully up to date; the good ones are just updated where it matters most. Your job is not to capture everything but to keep the important, frequently used parts trustworthy. Make updating part of the change itself, not a separate chore for later. When you alter a system, fix its doc in the same breath, before you move on. Tie the two together and the knowledge base stays current as a side effect of the work, instead of a task you never get to.