Document the change
Documenting the change makes the experiment useful later.
Experiments can become confusing if the team forgets what changed. A short note can prevent that.
Change note for the test
Write the change note before or right after the change.
Keep it direct. Include the page, prompt, routine, date, and reason when those matter.
md
## Experiment change note Date: July 9. Change: added source-proof section to the comparison page. Reason: prompt answers mentioned competitors but did not explain CLEA source evidence. Expected result: answer wording should mention source evidence more often.
1
Record the date
Say when the change happened.
2
Name the changed item
Page, prompt, workflow, or link path.
3
State the reason
Explain which gap the change should address.
4
Set expected signal
Say what should move if the change helps.
Narrow change
If the change note is long, the experiment may be too broad.
Try to split the work into smaller notes. That makes later review easier.
Change record
Keep the record close to the experiment.
Use `EXPERIMENT.md`, a workflow file, or the relevant sitemap page notes.