Small changes are rarely small

One of my first tickets on a new team asked for a small change to an information box.

During refinement, a senior developer explained that the box existed in more than twenty variants. The request had not become larger. My view of the system had.

Those variants were not arbitrary. Each had once answered a customer need, a regulation or a constraint that could not be removed. The complexity came from reasonable decisions accumulating in the same place.

A ticket rarely carries that history. It describes the visible change, not the number of assumptions underneath it.

Now, when a request looks small, I ask different questions. How many versions already exist? Why are they different? Which behaviours are deliberate, and which are residue? What else relies on this part of the product?

The size of a request tells us how much the user wants to see change. It tells us very little about the size of the system the change will touch.