Database Director · Database Manager · Senior DBA

Where does your team's knowledge live?

This page is not a criticism of the team. The opposite: it is about why the knowledge of a team that works well is still fragile.

How this question is answered today

Someone knows the release order. Someone knows which table must not be touched during business hours. Someone knows which job has to run before which.

That knowledge is not wrong. It was built over years and is often more accurate than any written rule.

The problem is that it cannot be handed over. Written into a document it loses its nuance; left unwritten it leaves with the person.

What that answer costs

The most senior person cannot take leave comfortably. When they do, the release is postponed or a risk is taken.
The rollback script written at 02:10. It worked that night. Nothing guarantees it will work next time.
A new joiner learning by asking questions for six months. That period is in nobody's plan.
In an audit, answering "why was it done this way" with personal experience.

What governance changes

Governance does not dismiss the team's experience. It turns it into a rule in the system. The release order lives in a definition rather than on one person's screen.

The rollback is prepared together with the change. It stops being a script written at night and becomes part of the plan.

How risk is assessed no longer depends on who is assessing. The same script under the same conditions gets the same answer every time.

Team knowledge moves from people into the system, night interventions stop being improvised, and you can turn your phone off while on leave.

Where this meets other roles

CTONight work sits outside the pipeline; the scope problem is shared. InfrastructureWhat changed on which server is the same question for both. CISOWhen answering a data request you should not have to make the masking decision alone.
Read a day in a database team Self assessment