[ChrisMarshallNY]

I worked for a Japanese corporation, and a really major default posture, was to make sure that someone was always on the hook for $THING, at every step of the development/maintenance process.

We never ended a meeting, without making sure that everyone had specific, well-documented marching orders, and we had an insane JIRA workflow, designed especially, to ensure that someone owned the issue, at every point. GitHub issues (my preferred method, these days) would never have been acceptable, as it does not force ownership.

They had huge Excel spreadsheets, that tracked issues, and there was always a “responsible person” column.

It could be a massive pain, but things seldom “fell through the cracks.”