A change is not finished when it ships; it is finished when someone checks whether it worked and the playbook learns from the answer. This skill keeps a change log, fixes a baseline before each change, reads the data again after a set window, and decides: keep, keep testing, revert, or unproven. In CMO.so it starts from what Maggie actually did and how each tracked article performs in Google Search.
When to use
- After Maggie publishes or rewrites articles, or after any page, campaign or offer change.
- "Did it work?", "before and after", "keep or roll back?", "which changes moved traffic?".
- Building a habit of monthly readbacks so future work follows evidence.
- Not for: designing a controlled split test up front (
cmo-ab-testing), watching for ranking or traffic drops (cmo-seo-monitoring), channel-level ROI and funnels (cmo-campaign-analytics) or rewriting the articles themselves (cmo-content-refresh).

