When I had to explain MassTransit to my coworkers, I liked to use Entity Framework as an analogy.
I think it's more likely for them to understand it that way: instead of having to work with
ADO.NET and the SqlConnection, SqlCommands, pure SQL queries, etc, you just normally use EF to make the mappings between POCO classes and tables, define the class inheritance strategies, navigation properties, etc.
With MassTransit, instead of working with the raw RabbitMQ client and having to refer to every exchange, queue, set their bindings and the occasional routing keys, you just use different message types, configure the consumers, create the SendEndpoints, etc, and that's it; you have all the pipeline created behind the stage and you only need to say what type of message you want to send or publish without much further effort. It even implements certain patterns that save you all the fuss of having to implement them by yourself, like Sagas, or the Request/Response.
Cheers!