This needs working schema migration process, including ability to undo schema change if the new column tanks the performance or breaks stuff. If there are CLI

This needs working schema migration process, including ability to undo schema change if the new column tanks the performance or breaks stuff. If there are CLI tools involved, you also need to ensure you can handle some downtime, or do synchronized version update across company, or support both old and new schemas for a while. If a database is not part of team's primary product all of this could be missing.