Ask HN: Is there a tech term for disparate apps overlapping use cases over time?

I work for a SaaS company. We have a few applications that our clients use and each has a purpose. Same goes for the documents we generate for clients.

Over time clients slowly request "add this data to X document". The requests are simple and easy to do so they are done. Yet over time that data seems to trigger the clients to request more and more related data.

Eventually apps, documents, and etc all start to look the same ... and the work load managing and errors (human and other) start to rise because now people sometimes use the wrong document for the wrong reason (same goes for apps and so on).

Is there a technical term for this specific issue?

Homogenization? Feature creep doesn't really sound right ... Use case creep?

Example:

If you added an address to a given document, why not add the contact names, what about the special directions to get to that location? But then you realize that this random request for a document that was to be handed to accounting ... turned into a document that is being used by some poor truck driver staring at an accounting document, and not the document he should be looking at (that already has that information).

To be clear we've largely managed this issue, I'm just wondering if there is a specific term for this kind of problem / tendency?