My father was a barber but he was a specialist focused on grooming. Back in medieval days you could go to a barber for just about anything. You could receive a haircut, a shave, a blood letting, a tooth extraction, surgery… the barber could do it all.
I’m sure there was confusion about the various types of barbering one could receive. I can hear the comments medieval people made as they discussed the various types of barbers:
- “Don’t go to Vlad he only does blood letting”
- “Our barber does haircuts, shaves and tooth extraction – how about yours?”
- “We don’t call our guy that operates on wounds a barber, we call ours a surgeon”
- We had a bad experience with our barber so we put him on the rack. We don’t do barbering anymore.”, “But how do you remove teeth?”, “We do dentistry.”
I’m sure barbers fought for a long time to keep surgery, and tooth extraction as part of the trade. Factions must have formed around surgery and barbering. Barbering methodologies each proclaiming they were the true practice. It is similar to conversations about enterprise architecture and how the IT industry discusses the role of an enterprise architect.
We now have many different types of hairstylists, surgeons, and dentists… I wonder how many others think history will repeat itself and distribute various aspects of the EA discipline across many business roles and professions?
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
How to Live Without Mobile Device Management
This webinar addresses the growing trend of users refusing to have enterprise management of their mobile devices due to privacy concerns....
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.