Fun rhetorical challenge for you:
Describe/explain something technical so that someone non-technical can understand it, but also so that someone technical can't criticize it for being imprecise.
@kyle that's mutually exclusive requirements. And is exactly the reason executive summary, high level solution design documents and such exist.
@kyle But! it does not remove necessity for low-level design documents, technical reference dcos, blueprints. Providing one (HL/LL) without the other (LL/HL) - that what brings criticism.
@kyle be sarcastic, so that the tech people can laugh, but the others don't. Hm well maybe bad advice.