Endnotes 1 see zack michael an architecture for

Endnotes
1. See Zack, Michael, An Architecture for Managing Explicated Knowledge, Sloan
Management Review (forthcoming).
2. Court, A. W., The Relationship Between Information & Personal Knowledge in New
Product 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 in
Borghoff, Uwe, and Remo Pareschi, Information Technology for Knowledge
Management , 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 system
in 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 those
positions. Extensive research on this has been done by Ramesh, Balasubramaniam at
the J. Mack Robinson College of Business. See, for example, Balasubramaniam,
Ramesh, and Kishore, Sengupta, Multimedia in a Design Rationale Decision Support
System, Decision Support Systems , vol. 15 (1995), 181–196. Follow-up work can be
found in Ramesh, B., and Tiwana, A., Supporting Collaborative Process Knowledge
Management in New Product Development Teams, Decision Support Systems
(forthcoming).
8. See, for example, Zack, M., Electronic Publishing: A Product Architecture Perspective,
Information & Management vol. 31 (1996), 75–86.

9. See Weill, Peter, and Marianne Broadbent, Leveraging the New Infrastructure: How
Market Leaders Capitalize on Information Technology , Harvard Business School Press,
Boston (1998), 86.
10. Mankin, Don, Susan Cohen, and Tora Bikson, Teams and Technology , Harvard
Business 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 calculations
show that your conditions are more favorable than those of your enemy; if they indicate
defeat, 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 of
victory has one who makes no calculations at all!
—Sun Tzu in The Art of War

IN THIS CHAPTER
• Define the capabilities of each layer of the KM system architecture in the context of
your company.
• Create platform independence, leverage the Intranet, enable universal authorship,
and optimize video.
• Develop the access and authentication layer: Secure data, control access, and
distribute control.
• Develop the collaborative filtering and intelligence layer.
• Develop and integrate the application layer with the intelligence layer and the
transport layer.