Enterprise Knowledge Portals is a very practical and ready-to-use book for KM practitioners looking to bridge the gap between theory and implementation. The level of details regarding portal tools and implementation roadmaps makes for an excellent step-by-step guide for KM practice. The nine chapters are divided into four sections: portal definitions, programs, projects and infrastructure. The material includes lots of templates, questionnaires, activities, tasks, draft memos, screen snapshots, checklists and suggestions. Heidi Collins is Knowledge Officer at Air Products and Chemicals, author of Corporate Portals and a prolific writer on KM topics. “The enterprise knowledge portal is the intersection between knowledge management and the enterprise portal,” Collins begins. It helps provide consistent views of the organisations, personalised access for employees, layered presentation, cross-media communication, improved involvement, and learning behaviours for quick adaptation to changed surroundings. Key objectives of a KM solution should be to facilitate communication, be organised around work processes, focus on the future, support business objectives, promote innovation and maintain a knowledge-creating organisation for multiple target communities. “Challenges of change management, intellectual growth and partnership development in the organisation should not be overlooked,” Collins cautions. Workers need to be “self-starters” and take the initiative, and managers should continually plan for “what-if” scenarios. The enterprise portal server is a collection of servers providing services like directory and security, rules (for workflow), components (applications), personalisation, metadata, business intelligence, transaction, and library objects. Vendor selection should be governed by considerations like presentation (intuitive interface), application integration, knowledge organisation, search/index and personalisation features. The early stages of portal vision should include documentation of organisation mission and KM objectives; Collins provides a sample questionnaire with 45 items covering issues ranging from success indicators and process improvement to mentoring roles and employee empowerment. These can then be cross-tallied and ranked in a table which includes IT-enabled tools (e.g., messaging, mining, and balanced scorecard), depending on whether the features are viewed as critical, must have, important, or nice to have. The output of this analysis will be a request for a proposal to portal vendors. The next phase after this portal map exercise is creating the enterprise knowledge portal (EKP) program. The program covers methodology, timeline and roles for portal design and implementation. The EKP Program Charter should address portal scope, stakeholders, benefits, risks, budgeting and communication. The Portal Requirements Template should address IT framework, work processes and product features. Program Tasks include policies (e.g., compliance), standards, monitoring and archives.