A team sometimes takes a shortcut to finish a necessary task. The difficulty comes later, when the surrounding situation has changed and no one remembers which parts were meant to be temporary.

Record the reason, the tradeoff, and a condition that would justify revisiting the choice. A note such as “replace someday” gives little guidance. A concrete constraint makes the decision easier to evaluate against new needs.

Revisit the choice where it meets actual work. Some shortcuts remain appropriate; others create repeated friction. The aim is to understand the cost before habit turns a provisional decision into an unexplained foundation.

A few starting points
  1. Record the reason for the shortcut.
  2. Name the cost it introduces.
  3. Choose a practical condition for revisiting it.

An example to consider.

Imagine skipping a clear filename during a rushed export. The saved minute may return as a longer search when several versions accumulate.

Put it in perspective.

Consider the point where a person should regain control. A future tool remains useful when its limits are legible and a different choice remains possible.

Follow a related question

Describe accepted input and expected output.

An interface is a promise

Describe a scene at two scales.

Changing the scale of a question

Keep learning

Related background to continue exploring this subject.

W3C: web accessibility W3C: accessibility, usability, and inclusion
Make room for ideas