Explicit versus Tacit – Content versus Process
Tanmay Vora
Difficult situations like slowdown force organizations/managers to do cost-benefit analysis. Salary you are paid is a cost and what you do in the organization for that cost generates value.
Value has two components – tangible and intangible.
Tangible value (easier to visualize) is explicit knowledge of subject (e.g. knowledge of .NET programming or software testing), revenue, efficiencies, numbers etc. This is important.
Intangible value (which is also hard to visualize) is tacit knowledge, knowledge on processes, knowledge on how to deal with typical situations/clients, attitude, different ways of doing things, workarounds etc. This is hard to visualize and measure. But impact of this value is huge.
So from organization/manager’s standpoint – it is important to see value as a sum-total of tangible and intangible value that someone brings on board while rewarding or hiring.
In this regards, I loved what Seth Godin has written in his post “What are you good at?”. He writes about explicit versus tacit knowledge. Crux is that explicit knowledge on subject can be easily learnt. Tacit knowledge only comes with experience within and outside the organizations. There are no shortcuts to acquire tacit knowledge.
Seth Godin writes:
As you consider marketing yourself for your next gig, consider the difference between process and content.
Content is domain knowledge. People you know or skills you’ve developed. Playing the piano or writing copy about furniture sales. A rolodex of movers in a given industry, or your ability to compute stress ratios in your head.
Domain knowledge is important, but it’s (often) easily learnable.Process, on the other hand, refers to the emotional intelligence skills you have about managing projects, visualizing success, persuading other people of your point of view, dealing with multiple priorities, etc. This stuff is insanely valuable and hard to learn. Unfortunately, it’s usually overlooked by headhunters and HR folks, partly because it’s hard to accredit or check off in a database.
Knowing difference between explicit and tacit aspects of one’s knowledge is very crucial from an individual standpoint.
I can easily relate contents of this post with Tom Peter’s saying “Hard is soft. Soft is Hard.” More elaboration on this in the next post.
Have a fantastic weekend!
Not very long back when I had to appear for tests on aptitude to get recruited I used to frown – “What has this to do with what I am going to do, technology?”. I am more convinced than ever before that there is no better way (other than working closely with the person) to judge the non-technical aspects which have great impact on what we deliver. Those tests of aptitude could be far from being accurate but just looking at the way someone approaches the solutions gives us a clear idea about what it would be to have such a person on board.
Few days back we, people on interview panel, assembled to gather all inputs and come to a decision about a particular candidate. One interviewer said he asked the candidate how much time he would estimate to develop a web form. The candidate replied four hours. You know how much we could make out from such a simple question and such a quick reply. There were several details missing and several questions unasked 🙂
Love the topics you choose and the treatment you give to the subject. Thanks!
Hi Vamsi, You are so right when you say that any aptitude test will not be sufficient to measure actual aptitude/attitude, till the time you work with a person.
While hiring, details like attitude, enthusiasm and overall knowhow is generally visible in candidate’s body language, provided you have an eye to identify it. There are several people in my current team who were hired not because they were technically very sound, but based on overall attitude they demonstrated in interview. Because technical skills are learnable with time, but attitude is in one’s DNA.
Thanks for commenting. Keep reading and have a nice weekend!
[…] 6, 2009 I wrote earlier about the explicit and tacit value that an individual brings to the organization. But how do you do […]
[…] January 2009: Explicit versus Tacit – Content versus Process […]