In an article Morgan Miller shares why he believes it's smart to rename the Service Blueprint to Experience Delivery Blueprinting, or Experience Blueprinting.

One of the big ideas that is shared in the article is the fact the term "Service" makes often people react with: "WTF is that?". Indeed the word service is one of the words that means a lot of explanations and comes with a loaded background.

So instead of spending hours explaining it, just switching to the term "Experience" which is much more known can be smart.

An additional interesting aspect of switching to "Experience" is that it includes both people who work on Products and Services. It makes clear that a product designer too can use a Service Blueprint, euh... Experience Blueprint.

Personally I'm sticking with the term Service Blueprint at the moment. I feel that it's better to stick with the historical name so that when people look on the web for more information about it, they can discover the rich history of the tool and see all the academic papers that have been written about it.