The complexity of software is an essential property. Hence descriptions of a software entity that abstract away its complexity often abstract away its essence.
-- F Brooks
While that is true, good system design needs to be a conversation where developers and business people both take responsibility for the end result.
If a concept can't be easily described, it's essence is probably too complex to be tamed anyway. So if you can't avoid being overwhelmed by the complexity of the answer, would it perhaps help to ask a simpler question?