Run old and new tools in parallel during evaluation — controlled comparison under comparable conditions beats hypothetical feature comparison

Why This Is a Rule

Evaluating a new tool after fully migrating creates confounded comparison: you're comparing the new tool with your data in it against your memory of the old tool. Memory is biased — you remember the old tool's frustrations more vividly than its strengths (negativity bias for the departed) or, conversely, you romanticize what you had (rosy retrospection). Either bias distorts the evaluation.

Parallel operation creates a controlled comparison: both tools are available simultaneously, used for comparable tasks in the same period. You can directly compare how each handles the same real-world task — not "How did the old tool handle something like this last month?" but "How does each handle this exact task right now?" The comparison is immediate, concrete, and unbiased by memory distortion.

This parallels Run old and new tools in parallel for 2-4 weeks during migration — new data to new tool, old data from old tool, end only when daily needs are confirmed's migration parallel-run but serves a different purpose: Run old and new tools in parallel for 2-4 weeks during migration — new data to new tool, old data from old tool, end only when daily needs are confirmed validates whether the new tool meets daily needs during an already-decided migration. This rule creates the controlled comparison that informs the migration decision itself.

When This Fires

• During any 14-30 day tool evaluation period (Define 3 measurable success criteria before any tool trial, set evaluation at 14-30 days — shorter misses friction, longer activates sunk cost)
• When deciding between keeping your current tool or switching to a new one
• When feature comparison spreadsheets don't resolve the decision
• Complements Define 3 measurable success criteria before any tool trial, set evaluation at 14-30 days — shorter misses friction, longer activates sunk cost (evaluation criteria) and Run old and new tools in parallel for 2-4 weeks during migration — new data to new tool, old data from old tool, end only when daily needs are confirmed (migration parallel) with the evaluation-phase comparison method

Common Failure Mode

Full-migration evaluation: abandoning the old tool to "really give the new one a fair chance." This eliminates the comparison baseline and makes returning to the old tool psychologically harder (sunk cost of migration). Two weeks later, you can't objectively evaluate because you have nothing to compare against.

The Protocol

(1) Keep your existing tool fully operational during the evaluation period. Don't export, don't uninstall, don't change configuration. (2) Set up the new tool alongside it. (3) For each task during the evaluation period, perform it in the new tool (primary) and note how the old tool would have handled it (comparison). For critical tasks, do both. (4) At the end of the evaluation period, compare against your 3 measurable criteria (Define 3 measurable success criteria before any tool trial, set evaluation at 14-30 days — shorter misses friction, longer activates sunk cost): which tool scores better on each? (5) Only after the parallel evaluation produces a clear decision do you begin migration (Run old and new tools in parallel for 2-4 weeks during migration — new data to new tool, old data from old tool, end only when daily needs are confirmed) or reject the new tool.