Working on Paradigm Change Towards Web3.0

Recently, I've been asked to set up an architecture practice. This requires setting up the processes and information systems needed, expanding the software development process to properly facilitate architecture. Turns out that this does not take most effort. Something else does: Working to create a paradigm change to the Web3.0 way of thinking.
My current employer is very open-minded. In exploring the possibilities for an information system we've concluded that Semantic Web Technology can supply us with all tools to do the job. Some of the advantages beinig: small learning curve, cheap, easy to maintain, accessible through the entire enterprise, et cetera.
After creating the information model and setting up the tooling, I walked into an invisible wall: Paradigm mismatch. The people that have to work with the semantic tool need time to get their head around it. The concepts are new and different from anything they're used to. Same thing with architecture collegues. Some are critic, many are sceptical and only a handful of them understand the potential.
A lot of time goes into explaining what it is, what it does and how it works. And I guess this is a good thing. In order to convince the world (everyone) this is the way to go, some of us have to break the proverbial ice. Some have been doing so for over a decade. And I'm glad I'm contributing. Please feel free to join.