Firstly, knowledge. The expert must know more than just the basics about a domain. He/she must have a solid grounding in the theoretical principles underpinning the domain. But to KNOW is not all….
Then there is application. The expert must be able to apply his.her knowledge. In other words he/she must be able to DO something. There is a definite skills aspects to this. But, I dont think that is it…
Also contextualization is important. A true expert recognizes that his expertise is domain specific. He/she realizes that knowledge and skills are different depending on the context in which that knowledge is applied… Which leads me I suppose to the ultimate quality of an expert:
The ability to create knowledge in the domain. If you have a body of knowledge that you can apply and contextualize, you may have mastered the material in the domain in such a way that you could bring new knowledge, new understanding to a domain. A real expert grows his domain.
In a a blog interchange following The Rise of the Instant ITIL Expert James Finnister compares this to a cook that follows the recipe and the great chef who can write a great recipe. I think this is an excellent analogy! Not recognizing what true expertise means lead to the lots of non-experts calling themsleves experts. This is certainly the situation in the ITIL playing field – see e.g. How to implement ITIL for a client.
What does this all mean? Probably that there is much less experts out there than what we think. And the message for me and my fellow academians? Be careful that we dont KNOW so much that we cannot DO stuff with our knowledge… we may therefore not be able to CREATE true new KNOWLEDGE… ouch!