- Task
- Version · 6.0
- Govern
Improve governance end to end
Last updated: September 29, 2026
You can keep improving how you govern your databases based on the measurements Liquibase gives you. This helps you work out how to remediate the issues they surface, and end up with a more secure database.
Before you begin
A measurement or an investigation has surfaced something worth acting on. Improvement starts from evidence, not from a hunch about which rule is wrong.
Procedure
Interpret the measurements
Read the trends honestly before acting. The unit of interpretation is the trend, and a single data point is a question rather than a finding. See Interpret governance and delivery measurements.
Identify the constraint
A bad number has three possible causes, and they take different fixes: A miscalibrated policy, a practice problem, or pipeline mechanics. Name which one you are looking at before changing anything. See Identify the constraint: Policy, practice, or pipeline.
Decide what to change
Pick the smallest change likely to move the measure, and make one change per cycle. Record what you expect to be different afterwards, because that expectation is what the last step verifies. See Decide what to change.
Make the adjustment
When the constraint is the policy, follow Adjust policies, assignments, and scope. When it is the teams or the pipeline, follow Adjust development and delivery practice.
Communicate the change
Tell the affected teams what changed, why, and when it takes effect, before the first pipeline feels it. See Communicate the change to affected teams.
Verify the effect
On the next measurement cycle, check whether the measure moved in the direction you expected and for the reason you expected. See Verify the effect on the next measurement cycle.
Retire what no longer earns its cost
Governance accumulates. Along the way, retire the controls that only produce noise, or that protect against a risk the platform no longer has. See Retire controls that no longer earn their cost.