Heuristic

Let the change bake before stacking the next one

If you change the experiment before the result arrives, you inherit an explanation problem.

About 1 min read

Before you use it

Use when
  • A first change has completed technically but important effects may appear with traffic, queues or delayed jobs.

Keep this limit in mind

  • Do not delay urgent remediation just to preserve a clean experiment; incident response can justify immediate follow-on action.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Choose an observation window long enough to expose the failure modes you care about before adding another unrelated change. Watch leading and delayed signals during that time. The point is not idle waiting; it is preserving causal visibility long enough to know whether the current state is healthy.

An example

After changing replication parallelism, observe at least one full processing cycle before also changing retry settings.

Check your result

When a metric moves, the team still has a reasonably interpretable set of recent changes rather than a stack of simultaneous experiments.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingLet the change bake before stacking the next one

Evidence and sources
Supports

AWS identifies rapid follow-on deployments without sufficient bake time as a deployment anti-pattern.

Required observation time depends on traffic, delayed jobs and the failure modes that matter.

REL08-BP05 Deploy changes with automation · Common anti-patterns

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details