Up to now, the extant research has emphasized the employment of KM to gain competitive advantage for organization, but few studies address the relevance of KM environment to support the strategic objective. Gartner has proposed a classification scheme for KM implementation, which indicates that life cycle of KM practice, but the study still falls short of guiding organizations to implement the suggested KM category. The motivation and purpose of this study are induced.
This study attempts to investigate the impact on KM implementation based on the organizational learning perspective. The investigation is conducted through a case study approach, where some companies with best KM practice are included. The findings based on case study results indicate that environment uncertainty, organizational orientation, and task type can influence organizational learning behavior and subsequent the deployment of KM systems. In summary, organizations may implement different KM systems depending on the environment confronted by the organization.
This study is focused upon the difference in KM systems deployed by various organizations. Past research has assumed that all organizations have similar needs in KM and therefore proposed an uniform IT framework to suit organizational needs. This argument has been refuted by this research. We suggested that KM is a multi-facet phenomenon, in which many enablers contribute to the working of KM. An organization ought to establish its KM environment based on its organization imperatives and learning needs.
| Identifer | oai:union.ndltd.org:NSYSU/oai:NSYSU:etd-0722104-145336 |
| Date | 22 July 2004 |
| Creators | Wu, Kir-ying |
| Contributors | Ho Chin-Fu, Wu Wen-Hsiung, Lin Fu-Ren |
| Publisher | NSYSU |
| Source Sets | NSYSU Electronic Thesis and Dissertation Archive |
| Language | Cholon |
| Detected Language | English |
| Type | text |
| Format | application/pdf |
| Source | http://etd.lib.nsysu.edu.tw/ETD-db/ETD-search/view_etd?URN=etd-0722104-145336 |
| Rights | off_campus_withheld, Copyright information available at source archive |
Page generated in 0.0019 seconds