The fact it's a tree is really important to the functionality the user wants, even if they don't know how to think in terms of trees in an abstract way ("you can roll up information from child orgs into their parent's reporting").
The language around trees just doesn't resonate and gets lost on people. This includes potential customers, sometimes project management, etc.
Have you ever come across a _really_ good way of describing trees? Or, in-context of requirements/work material, a means of talking about this idea that didn't cause people to lose focus?
