The everyday problem
Two accounts with the same age can require very different actions. One may be ready for follow-up; another may depend on information from a different team. An aging report is useful for seeing time, but it does not automatically reveal the cause of delay or the work needed next.
A practical approach
Pair age with status, blocker, and ownership. Separate time spent waiting from time spent actively being worked. Review how status values are assigned so that a generic pending label does not hide multiple operational problems.
Try this with your team
Take a sample of synthetic aged accounts and add a next-action field. Count how many can be assigned an action without another investigation.