Teaching article

Redesign one feature for a reason you can show

Connect a change to evidence from the first test.

Save the first test result before changing the model. A slipping tab, for example, gives a focused reason to revise a join; documenting that link makes iteration more than repeatedly making something different.

Save a note or photograph of the first version. The revision becomes easier to explain when its connection to the test evidence is visible.

Connect the change to the evidence

  1. Record the first outcome.
  2. Explain one change.
  3. Repeat the test.

Raising a slipping tab follows evidence about the slipping join.

Random changes make learning harder to trace. Why was that feature changed?

Use before-and-after boxes.

Resources

Further reading

Read next

Explore Design and paper engineering. Browse all teaching articles.