A new column sounds simple. It is not. The fastest path often breaks production or slows it until your alerts light up. Done wrong, it can cause locking, block writes, or create hours of downtime. Done right, it is invisible to the user and safe for your data.
Start with the schema. Decide if the new column will be nullable, have a default, or need indexes. Adding a column with a non-null default can rewrite the entire table, which can be dangerous on large datasets. For high-volume systems, create the column as nullable first, backfill in small batches, then apply constraints.
Run the change in a migration tool that supports transactional safety. In MySQL, ALTER TABLE can lock the table, so plan for online DDL operations. In PostgreSQL, certain column additions are instant, but defaults or type changes can still trigger heavy locks. Always test on a staging database with real-size data before touching production.