Name each variation clearly

Use a consistent name for the concept, opening, format, and version. Keep the source file connected to the approved export so the team can identify what actually ran.

Change one idea deliberately

Write down the question each variation is intended to explore. A clear hypothesis helps the team explain a result without guessing why every detail changed.

Record decisions, not just numbers

Keep a short note about what the team observed and what it will try next. Include the context and review period so the decision can be revisited responsibly.

Turn the brief into a useful next step

Bring these notes into the conversation with your team or ADFBM. Keep the selected configuration, the responsible contact, and any open question together. Before an order or change is confirmed, make sure the people doing the work share the same written understanding.

Use the checklist below as a starting point, then adapt it to the business and assets you are authorized to manage. Product details and platform requirements should always be confirmed for the specific setup involved.