Appllying Knowledge Management to Improve Performance of Dispersed Teams 应用知识管理提升团队绩效.ppt
- 1、本文档共24页,可阅读全部内容。
- 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
- 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载。
- 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Appllying Knowledge Management to Improve Performance of Dispersed Teams 应用知识管理提升团队绩效
At what point does a team become “Virtual”? not all in one room not all in one floor of a building not on one campus not in the same city not in the same time zone not communicating and collaborating effectively First…A Little about CSM Our business is based on managing and transferring knowledge We train and consult in project management and system engineering Our clients are government agencies and large corporations, primarily telecom and aerospace Our products/services are tailored for each client This has created a large IP repository CSM’s Visualization Model Context Until 1999, we were located on one floor of an office building in the San Francisco Bay Area Our staff is now widely dispersed with the largest concentration in Northern Virginia Even where we’re clustered (Northern VA, Northern CA, and Denver), we are seldom in the local office. Problems we experience as a “Dispersed Team” Knowledge Management - CSM context The Good Old Days… Our functional, vertical organization was unambiguous Internally focused with central controle.g., a “Key Messages Czar” and a central course development department We managed our IP reasonably well IP was in the form of PowerPoint files and Word documents CM tools were spreadsheets and databases Internal collaboration and CM worked well, but growth was limited by development capacity and customer exposure CSM was Re-engineered in 1999 We reorganized as client-centered and horizontal Client Program Managers were heavily involved in IP development and tailoring Control was distributed (but the tools weren’t) We relocated and dispersed Geographical, time zone, and office separation The tools and processes didn’t adapt well We became dependent on e-mail Unfortunately, it slowed the use of other forms of collaboration, communication, and CM Proposal Writing: A Case Study in KM Pre-1999, when a new RFP was released, the marketing manager: Accessed his personal memory for all related past activities and
文档评论(0)