So far analogy that worked for me is a house building one. Something along the lines: If you expect to build a cottage and it turns out to be actually a cathe

So far analogy that worked for me is a house building one. Something along the lines: If you expect to build a cottage and it turns out to be actually a cathedral, that is the source of the extra time or rework. Or, imagine you build a wall inside a house. But once the wall stands, suddenly you remember, that you wanted to have a window there. Or an electric socket. Imagine what extra work that will be. It is more easy for clients to imagine that and they understand the necessity of planning and a why some changes, although they seem like a small ones, may actually take a lot of time. I have the feeling that software is too abstract to reason about for non developers.