Who owns the "why we did it this way" knowledge on your team?

Market insights

Stack

Apply

Upload your CV — we will connect you with the employer directly through our pool.

Description

Who owns the "why we did it this way" knowledge on your team? Small team here and I keep running into the same thing. The reasoning behind half our setup lives in two people's heads. Not in the runbooks, not in Confluence, not in the repo. Someone new joins and rediscovers everything the hard way and when one of those two is out we just stall. It got noticeably worse once we started leaning on Claude Code and Cursor for real work. The agents read whatever context files we give them and treat it as truth, so now stale knowledge doesn't just slow a person down, it gets confidently baked into code by something that has no idea the decision changed months ago. So I wonder how this actually works at bigger shops. Is there anyone whose job includes keeping that stuff current or does it just live with whoever happens to remember? And has anyone here had a documentation process survive past the first busy quarter or does it always quietly die? Not looking for tool recommendations just trying to work out whether we're unusually bad at this or whether it's the normal state of things. [link] [handle]

Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.