Question: I have a need to explain MVC to non-programmers. Namely, to managers of other departments, in the context of progress report. One of the things I do is refactor our codebase towards MVC separation.

What is MVC separation they might ask?
Why is it needed they might ask?

After reading a fairly technical answer like this: [What is MVC, really?](https://softwareengineering.stackexchange.com/questions/127624/what-is-mvc-really), I am not entirely satisfied, since I will be talking to non-programmers. They may nod their heads but they probably will not understand what it is and why it is needed. 

In reality, I don't fully grasp what MVC is other than "separation of concerns, duties, functions, classes, blocks, tasks, things, in order to improve flexibility of making changes to the software". Separating database from view and view from business logic using techniques like DI and OO tools and techniques is something I consider to be MVC separation.

So next time you are explaining MVC to a non-programmer who has background in sales and accounting for example, what would you tell them?

Answer: 
You don't explain MVC.

What you do is explain that this is a restructuring of the codebase.

A restructuring that simplifies the codebase and therefore enables the developers to make faster and better changes to bug reports and feature requests, with less bugs.

They don't need to know the technical details, just why it was done, what was achieved by doing it and how the business benefits.

In other words - speak their language to them.
Benefits of MVC is primarily in the separation of concerns:

It lets people concentrate on what they do best.

```
Database admins develop the model
Programmers write the controllers
and Graphic designers can design the views.

```

It lowers costs because intertwined systems require staff to be either experts in all of these areas, or you are more likely to have problems when a change on one area affects the others.

Provide real-life examples of MVC architectures: Cell Phones, Desktop Phones, Skype, etc. Changing the View (type of dial pad, speakers, mics) doesn't affect the model (the audio signal), the controller is the circuitry in the phone that translates sound waves into audio signals.