For your interviews, I'd ask someone to walk through their last bug or art handoff: where did the request start, which file changed, and where did the reason for the change end up? A board can tell you who owns a task while still leaving that trail scattered across chat.
I'm building PlayWeld, a free open-source workspace for project files, notes and searchable project knowledge, so I'm interested in that gap too. It's still a testing prerelease, rather than evidence of a proven team workflow. Are you finding the bigger problem is assigning work, or recovering why a decision was made?