Showing posts with label visibility. Show all posts
Showing posts with label visibility. Show all posts

Thursday, December 17, 2009

Need Context to Locate the Right Expertise

This is about the effects of a lack of a phone book and directory. Some people would rather call to find an expert and start a phone tree instead of locating people online. We also have no ability to collect contextual information to help find people so the wrong people are getting calls.

When Self-Identification Didn't Work

This was a project to build a master expertise database for an organization. The experts’ self-descriptions were not precise or systematic or standardized. Some people criticized others’ expertise. We tried to use a standard taxonomy but that failed. Some did not want their expertise advertised.

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.

Wednesday, November 11, 2009

Invisible expertise on proposal teams

A proposal team is going through a debrief after the proposal is submitted. The proposal team manager admits that he really doesn't like to write and wishes the organization had more proposal writers available to support the proposal teams that are essentially made up of scientists and engineers. While the scientists have typically developed writing skills, the engineers haven't.

A member of the team present at the debrief timidly raises her hand to declare that while she's typically uncomfortable contributing in group settings, she's very comfortable with writing and she would have loved to play a greater part in writing the proposal. Her official role on the team only required her to write a half page. She could have contributed much more but she was never asked and she never realized her writing skills would have been appreciated.

On the same team, a scientist who knew nothing about the budget side of the proposal was successfully pulled in to help write the narrative related to the budget. Sometimes you've got to look beyond a team members' assigned role and look for hidden expertise.