I used to do something similar (at a lower level), and my solution was to lie, just lie. A big part was about https://en.wikipedia.org/wiki/Wavelet_transform so my description was something like:
I work in something related to Image Compression, so when the computer has to download the image from Internet it's smaller and use less data. Anyway, I study the mathematical part, not the programming part.
The idea is that images usually have big plain parts like the sky or the wall of a house, so you use big blobs of "ink" to paint them. For the border you use smaller blobs of "ink". And very close to the border you use smaller and smaller blobs of "ink". In this method, all the blobs of "ink" has the same shape, the only difference is the size. Also, the plain parts are not perfectly plain, so you use some small blobs of "ink" there.
In a typical image, you need very few blobs of "ink" if you pick the shape of the blobs of "ink" correctly. So you can only send the position and size of the blobs of "ink", that is much smaller than sending all the information of the image. The hard part is choosing a shape of the blobs of "ink" to make this conversion automatically and very fast, without asking the computer to do something smart to select the positions.
If the listener has more technical background:
The blobs of "ink" have white "ink" in some parts and black "ink" in other parts. This correspond to positive and negative values and actually all the blobs of "ink" are an orthonormal base so the calculation is only a orthonormal base change, that is super easy and fast. There is no smart selection of the position of the blobs of "ink" positions, just a boring orthonormal base change.
If the listener has even more technical background:
Something something Fourier Transform.
I don't want to count how many lies that description has. Also, all the parts in this description were done by other persons perhaps 10 year before me. I think I only once compressed an image, just for fun, and got a tiny compression because it was a toy method (¿Haar base?).
At least you are aware of the lies. I'm reminded of Feynman's refusal to lie about the nature of magnets (https://www.youtube.com/watch?v=Q1lL-hXO27Q): "You'd soon ask me about the nature of the [rubber] bands." Even in his digression about "why" questions, in giving a very high level reason for why ice is slippery he adds "they say", since I suspect he knew at the time the usual explanation had problems, and only recently do we have better explanations (https://www.quantamagazine.org/why-is-ice-slippery-a-new-hyp...). But at the same time, I've thought, it can be fun to try and come up with nice sounding lies, or analogies, or oversimplifications, especially for some types of people who won't leave you alone about something until they think they've understood something (even if a lie), or who want something repeatable to tell their friends about so they can brag about you. Still I think honesty is a better policy, even if it's not as satisfying, and if departed from at least making sure both sides know there are convenient lies and oversimplifications. As a student I would be (and have been) very put out if the goal is to understand something on a technical level and the teacher starts with lies.