Guys, I would like to know if anyone of you has been facing the challenge to capture non tacit knowldged from your techincal, I am looking for methods, procedures or tools. Saving Changes...
Sort By:
arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
Hi Nelson.
If you are looking on formal or explicit knowledge sharing from technical team members, some of the methods that I know that have worked in the past:
a. Pairing - technical team members share each others' knowledge in pairs.
b. Team Meeting - during team meetings, team members share their thoughts and solutions to technical problems or issues
c. Code Review feedback - Peer or Senior Member reviews other team member's codes and provide feedback
d. Analysis and Design Document Review and Feedback: Team member prepares an Analysis and Design document and a peer or senior member would review it and provide feedback. Saving Changes...
saurabh mahajanPMP, ITIL, PRINCE2| vodafonePune, Maharashtra, India
In my opinion the best way to have technical knowledge transfer is to make the new person work on tasks/activities.
1) This way he/she will face issues and will learn the way to tackle it.
2) This gives an opportunity to prepare documentation (KEDB) of the issue faced (if the doc is not in place).
3) Also, any untold technical knowledge to the new person in uncovered.
Saving Changes...
Arlene and Saurahb thanks a lot for the tips , it is really challenging ..
Your recommendations are excellent, I will include that in my presentation I am preparing for the next week ! Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Hi Nelson,
tacit means silent, so how get this knowledge talking?
Somebody has it and somebody else could need it.
So pairing 1:1 is a good way, as Arlene put it, Can take to forms of mentoring, coaching, assisting.
Also 1:n synchronous communication, like presentations, classes, peer2peer sessions is a good way.
For the last one you could extend it to 1:n asynchronous communication, meaning coding (which might be difficult with tacit knowledge) and storing the knowledge, somewhere where you can search and find it and at best track the usage. Tagging, keywords are techniques used with that.
The worst way would be 0:1, so just put someone on a task and let him figure out. Sometimes in that situation, specific survival techniques help, how to figure out how to do something. As an example, I see code reviews, also structured requirement reviews like function points, and I have seen observation techniques (e.g outsourcing application maintenance teams watch and record the upcoming issues and their solution by the old team for some weeks and then should be able to cover 80%-90% of all cases. The rest is research, but that's needed anyhow in trouble shooting).
As a prereq consider to create networks so everybody understands who knows what and how to reach them.
Hope that helps. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
See "Solution Selling" or "Spin Selling" selling method. It works for me from years. Saving Changes...
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons."
