At my previous organization, we carried out a detailed analysis of the impact of a privacy breach on our business. Towards the end of my time there, this actually happened. This made headlines in the technology press. I do not think our modelling was used in dealing with this but perhaps that did not matter.
I thought that i had a lot of knowledge in this area and yet very little of this has been drawn on by that organization after i left. They are still operating so I presume that they did not need it. Perhaps experts have an over-inflated view of their own value?
Showing posts with label Value of Expertise. Show all posts
Showing posts with label Value of Expertise. Show all posts
Tuesday, July 20, 2010
Turning Expertise into Algorithms
I am currently working in Guangzhou. The textile industry them is in the top 3 in China. In this industry it’s difficult to measure color. There can be 30% uncertainty in measurements. Expertise is built by experience and there is no single fixed formula. Our problem is how can we standardize a formula? We have a gap between the workers, 40-50 age group vs younger 20-30 age group. The knowledge transfer or expertise building rate is not very high.
Sunday, March 21, 2010
Experts respected for organisational knowledge more than technical knowledge
This was my first experience as a "knowledge engineer" trying to build an "expert system" for a chemical processing plant in the mid 1980s. That experience still shapes a lot of my thinking. Firstly the context was the archetype expert system one, the expert operator (and long term foreman), 35 years + experience, retiring in 12 months ... his name was Maurie. He had the total respect of the rest of the operating crew (who I might add only averaged 20 years on the job).
After doing my knowledge engineering thing and extracting a few hundred "expert" rules, I began testing them with the "junior" operators. Anything special or insightful? No not really... the common answer was yeah you could do it that way. Would you change your action if this was recommended? Maybe ... not sure if it matters. Even Maurie was a bit ambivalent and supported them in saying yeah that could work too. This was pre- TQM days and shortly afterward the standard operating procedure (SOP) was born, so there was a lot more support for standardisation ... not so much from what might work or what might not, but a view that if we standardised actions we would at least have a measurement environment that operating performance drifts could be more easily identified.
When we implemented the system I would have to honestly say that the value the operators gained was not so much in the "insightful" recommendations the system made, but the "evidence" in terms of signals tracked and displayed to justify the recommendations that were most valued.
I continually experienced this in my Expert Systems days. A case based reasoning system for a consumer call centre was of most use to novices. More experienced staff would want to make their own decisions but appreciated the support information. Expert Systems in my experience worked best in the "complicated" domain (viz Cynefin)...where the effort of logically breaking down a decision process was both viable and valued.
As for Maurie ... why was he so respected as THE expert when the knowledge base we built from his so-called tacit knowledge was not seen as anything special? Well I learnt that respect and expertise can be different things. Perhaps Maurie's technical expertise was not necessarily superior any more to the 20 year "juniors". His people and organisational skills in working with the other operators was superior ... hence the respect that he was given. As one operator quipped ... Maurie knows where everything is .... you want a shovel or a broom....Maurie knows where it is!
I've recently interviewed some chief engineers that will retire soon. I found the same thing...its not their technical "tacit" knowledge that is valued as much as their "organisational" knowledge...especially the "how do you get stuff dome around here" tacit knowledge.
After doing my knowledge engineering thing and extracting a few hundred "expert" rules, I began testing them with the "junior" operators. Anything special or insightful? No not really... the common answer was yeah you could do it that way. Would you change your action if this was recommended? Maybe ... not sure if it matters. Even Maurie was a bit ambivalent and supported them in saying yeah that could work too. This was pre- TQM days and shortly afterward the standard operating procedure (SOP) was born, so there was a lot more support for standardisation ... not so much from what might work or what might not, but a view that if we standardised actions we would at least have a measurement environment that operating performance drifts could be more easily identified.
When we implemented the system I would have to honestly say that the value the operators gained was not so much in the "insightful" recommendations the system made, but the "evidence" in terms of signals tracked and displayed to justify the recommendations that were most valued.
I continually experienced this in my Expert Systems days. A case based reasoning system for a consumer call centre was of most use to novices. More experienced staff would want to make their own decisions but appreciated the support information. Expert Systems in my experience worked best in the "complicated" domain (viz Cynefin)...where the effort of logically breaking down a decision process was both viable and valued.
As for Maurie ... why was he so respected as THE expert when the knowledge base we built from his so-called tacit knowledge was not seen as anything special? Well I learnt that respect and expertise can be different things. Perhaps Maurie's technical expertise was not necessarily superior any more to the 20 year "juniors". His people and organisational skills in working with the other operators was superior ... hence the respect that he was given. As one operator quipped ... Maurie knows where everything is .... you want a shovel or a broom....Maurie knows where it is!
I've recently interviewed some chief engineers that will retire soon. I found the same thing...its not their technical "tacit" knowledge that is valued as much as their "organisational" knowledge...especially the "how do you get stuff dome around here" tacit knowledge.
Labels:
expert systems,
recognition,
respect,
Value of Expertise
Friday, January 15, 2010
The Man Who Knew Too Much
Here was an older engineer (let us call him Mr. Gupta) in a large manufacturing organisation. The emphasis in the organisation was on 'activity'. Those that showed enthusiasm were rewarded better than those who really knew the job. Mr.Gupta's philosophy was 'prevention better than cure'. But this was not glamorous. Younger engineers would jump in & be part of the excitement in firefighting. Mr. Gupta would refuse to be a part of this firefighting, which according him could have been prevented in the first place if only they had listened to him, which point he would not hesitate to recite to any one who came in contact with him. This obviously made him unpopular with the management and a laughing stock among his peers.
Mr.Gupta became a frustrated man and a mental wreck.
Mr.Gupta became a frustrated man and a mental wreck.
Thursday, December 17, 2009
Promoted into Unhappiness
This is from a university. Promotion in science is based on scientific expertise but promotion puts scientists in management roles. But management ability is NOT valued, therefore there is poor organizational performance and an unpleasant culture.
Not Appreciated Until the Need Arises
Working as contractor – project manager for a big government organisation – hired by that organisation to teach project management. Found that inside the organisation, project management was not valued. Spent 1 year doing nothing. Then new legislation was created and the resulting change forced a project approach, so this expertise was shown to be more valued. Now the organisation sees the value and focuses on project management.
Expertise Not Discovered Until Almost Too Late
This story comes from the military. We had an NCO who was considered mediocre in his technical job and transferred to a Training Unit, where he could be out of harms way until he retired. This guy turned out to be expert at databases and he ended up creating an online training system. It became the standard system for the whole organization, after it was recognized externally and won awards. His expertise was not visible or valued (even to himself) until he got the right job. His expertise in his original role was not valued. This happened in his 19th year of service so he then retired, and his expertise was lost almost as soon as it was found. He resented being given his original job. Moreover, it was an external party who recognized his accomplishment first, and not his commander.
Labels:
motivation,
resentment,
Value of Expertise,
visibility
Wednesday, December 16, 2009
It's All Replaceable
Where I am, there is no retention or respect for expertise. “They think it's all replaceable.”
Not Recognising the Need to Manage Knowledge Work
In my organization, right now, lean six sigma is a huge initiative. However most activities in our organization are knowledge work, and they haven’t yet come to grips with that.
Age of the Dinosaur
Sometimes, you need to go back to the source. Legacy knowledge and people are sometimes needed. Don’t discount the old guys’ value or the grey beards.
Recognising the value of consultants
I work in a large government organisation as a consultant. I report to a senior manager within one of the departments. My expertise that has been gained from 20 years industry experience is highly valued and my opinion/insights are received very positively. This is within an industry where I have minimal experience in the core service, however I can make significant contribution in the management and governance around the organisation and delivery of those services. Areas where my expertise has been sought include internal team structure, vendor relationships, project evaluation, research data, project and program management and inter-departmental governance
Labels:
consultants,
government,
Value of Expertise
Monday, December 14, 2009
On Not Being Able to Validate Expertise
We have lots of examples of work on projects. We don’t know which are good or bad examples. The author is perceived as an expert but it is really unknown if he’s good or bad.
Monday, November 30, 2009
Discounting of Expertise
This is from Michiko Kakutani's review of Sarah Palin's book Going Rogue, published in the NYT November 14 2009:
'Yet Mr. McCain’s astonishing decision to pick someone with so little experience (less than two years as the governor of Alaska, and before that, two terms as mayor of Wasilla, an Alaskan town with fewer than 7,000 residents) as his running mate underscores just how alarmingly expertise is discounted — or equated with elitism — in our increasingly democratized era, and just how thoroughly colorful personal narratives overshadow policy arguments and actual knowledge. Ms. Palin herself had a surprisingly nonchalant reaction to Mr. McCain’s initial phone call about the vice president’s slot, writing that she was not astonished, that it felt “like a natural progression.”'
'Yet Mr. McCain’s astonishing decision to pick someone with so little experience (less than two years as the governor of Alaska, and before that, two terms as mayor of Wasilla, an Alaskan town with fewer than 7,000 residents) as his running mate underscores just how alarmingly expertise is discounted — or equated with elitism — in our increasingly democratized era, and just how thoroughly colorful personal narratives overshadow policy arguments and actual knowledge. Ms. Palin herself had a surprisingly nonchalant reaction to Mr. McCain’s initial phone call about the vice president’s slot, writing that she was not astonished, that it felt “like a natural progression.”'
Monday, June 29, 2009
Whatever It Takes
This story is about an IT expert, a brilliant guy. Many schools were under severe closure in this village, but we had results of 12 grades to issue. He sneaked out from the village where he lived and kept working for 4 days and nights to rush results out.
Scaling Expertise
One colleague here was a principal at a school. The school was doing well, and her supervisor was very happy. She was transferred here, and is doing strategy development for her previous school plus other schools as well.
Finding a Gem
This story is about a chemistry teacher who is socially not significant. I discovered by chance that his hobby was repairing old TVs. I got him to lead a class, on recycling old parts to make teaching aids for scientific study. Now he teaches lab technicians to recycle old apparatus. He has a lot of know-how in geography and geology too.
Restrictive Supervision
I worked in the Ministry of Education but left after 6 years. My supervisor / trainer who hired me knew me and what I could do. I had activities after school, and she allowed me to schedule my classes accordingly. But I was promoted to a secondary school. The new principal didn’t allow extra activities. I was going to hold an art exhibition, and the guest of honour was the Minister of Education. The principal didn’t allow me to go but I went anyway. The next day, I was told that I didn’t have a job anymore. The following month, I joined KHDA and I’m happy here.
One Man’s Trash…
We were shifting to a new police HQ, and were destroying the old building. A policeman walked by and found old boxes with photographs and files in the garbage. He took them to the police chief. It was a fortune of old pictures relating to the history of the police force. Nobody knew about it. We didn’t even know who the people in the photographs are. Eg, there were 400 photographs of a 1981 Hurricane taken by the police. Nobody else had documented in this way.
Disposable Expertise
Large consulting company has lots of data in their databases on previous project. Consultants are dispensable assets as they just get proposals, use templates, work hard, then they last a year or two and we throw away and get more consultants.
Thursday, March 19, 2009
He knows it all
We have this large collaboration system supporting all projects in the company which is internally built. Long long ago most people who worked on the code base have either left or have stopped touching it as they are no more sure where a change will impact. We now have only one person who can navigate through the code base and develop anything meaningful on this platform.
Subscribe to:
Posts (Atom)