Endnotes 1 see zack michael an architecture for

This preview shows page 273 - 278 out of 482 pages.

Endnotes1.See Zack, Michael, An Architecture for Managing Explicated Knowledge,SloanManagement Review(forthcoming).2.Court, A. W., The Relationship Between Information & Personal Knowledge in NewProduct Development,International Journal of Information Management, vol. 17, no.2 (1997), 123–138.3.Lawton, George, Unifying Knowledge with XML,Knowledge Management, August(1999), 38–45, provides a list of companies using XML for knowledge management.4.See, for example, an argument on page 40 by Natalie Glance and her colleagues inBorghoff, Uwe, and Remo Pareschi,Information Technology for KnowledgeManagement, Springer, New York (1998).5.Borghoff et al.,Information Technology for Knowledge Management.6.Michael Zack cautioned that this must be reflected in the design of any such systemin his Sloan Paper. See Zack,An Architecture for Managing Explicated Knowledge.7.Such as positions taken by team members on issues and their arguments for thosepositions. Extensive research on this has been done by Ramesh, Balasubramaniam atthe J. Mack Robinson College of Business. See, for example, Balasubramaniam,Ramesh, and Kishore, Sengupta, Multimedia in a Design Rationale Decision SupportSystem,Decision Support Systems, vol. 15 (1995), 181–196. Follow-up work can befound in Ramesh, B., and Tiwana, A., Supporting Collaborative Process KnowledgeManagement in New Product Development Teams,Decision Support Systems(forthcoming).8.See, for example, Zack, M., Electronic Publishing: A Product Architecture Perspective,Information & Managementvol. 31 (1996), 75–86.
9.See Weill, Peter, and Marianne Broadbent,Leveraging the New Infrastructure: HowMarket Leaders Capitalize on Information Technology, Harvard Business School Press,Boston (1998), 86.10.Mankin, Don, Susan Cohen, and Tora Bikson,Teams and Technology, HarvardBusiness School Press, Boston, Massachusetts (1996).11.Ibid.Chapter 11. Developing the KM System
Now, if estimates made before the battle indicate victory, it is because careful calculationsshow that your conditions are more favorable than those of your enemy; if they indicatedefeat, it is because careful calculations show that favorable conditions for battle are fewer.With more careful calculations, one can win; with less, one cannot. How much less chance ofvictory has one who makes no calculations at all!—Sun Tzu in The Art of War
IN THIS CHAPTERDefine the capabilities of each layer of the KM system architecture in the context ofyour company.Create platform independence, leverage the Intranet, enable universal authorship,and optimize video.Develop the access and authentication layer: Secure data, control access, anddistribute control.Develop the collaborative filtering and intelligence layer.Develop and integrate the application layer with the intelligence layer and thetransport layer.

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 482 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Spring
Professor
JeffreyA.Bacha
Tags
knowledge management toolkit

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture