<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
author-Robertson, James
<channel>
	<title>Robertson, James</title>	<link>http://tc.eserver.org/authors/Robertson,_James</link>
	<description>A bibliography of works by Robertson, James in the field of technical communication.</description>
	<language>en-us</language>
	<atom:link href="http://tc.eserver.org/authors/Robertson,_James.xml" rel="self" type="application/rss+xml" />
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Robertson, James</title>
		<link>http://tc.eserver.org/dir/Robertson,_James</link>
	</image>
	<item>
		<title>The Intranet as a News Channel</title>
		<link>http://tc.eserver.org/31430.html</link>
		<guid>http://tc.eserver.org/31430.html</guid>
		<description>While the use of a news section on the company intranet&apos;s home page is widespread, communicators need to ask themselves how effective this is as a way to avoid mixed messages and information overload. Does it reduce information overload, or increase it? And how can the news section be used to effectively cut through informational clutter?</description>
	</item>
	<item>
		<title>Avoid Long-Term Strategies</title>
		<link>http://tc.eserver.org/29750.html</link>
		<guid>http://tc.eserver.org/29750.html</guid>
		<description>When it comes to information management or content management strategies, particularly at the enterprise level, there is a strong tendency (and desire) to create long-term plans. This briefing will explore some of the issues encountered when creating and executing long-term plans, and will argue for an approach that delivers benefits on a much more frequent basis.</description>
	</item>
	<item>
		<title>Does Your CMS Vendor Have Product Expertise?</title>
		<link>http://tc.eserver.org/29747.html</link>
		<guid>http://tc.eserver.org/29747.html</guid>
		<description>Choosing a content management system (CMS) is not just about finding the product with the right functionality. It&apos;s also about dealing with a vendor who can support your needs for the lifetime of the solution. This briefing explores the way most CMS vendors have evolved, what this means for the way they work, and what you should be looking for when purchasing a solution.</description>
	</item>
	<item>
		<title>Eleven Usability Principles for CMS Products  </title>
		<link>http://tc.eserver.org/29752.html</link>
		<guid>http://tc.eserver.org/29752.html</guid>
		<description>The functionality of the content management system (CMS) is obviously a key deciding factor when purchasing a new product. Equally important is the usability of the CMS.</description>
	</item>
	<item>
		<title>Using Scenarios to Select a CMS</title>
		<link>http://tc.eserver.org/29746.html</link>
		<guid>http://tc.eserver.org/29746.html</guid>
		<description>Scenarios are narrative descriptions or stories that concisely outline how something will work in practice. In the context of a content management system (CMS) project, scenarios are a very effective way of documenting key CMS requirements, and they complement the formal lists of functional requirements typically found in tender documents. </description>
	</item>
	<item>
		<title>Your New Site Will Be 20% Different from Current Site</title>
		<link>http://tc.eserver.org/29748.html</link>
		<guid>http://tc.eserver.org/29748.html</guid>
		<description>Despite all of this opportunity for change, the simple rule of thumb is that the new site will be at best 20% different from the current site. There are fundamental reasons for this, which will be explored in this briefing. The implications of the rule for the design and technology aspects of the project will also be discussed.</description>
	</item>
	<item>
		<title>Demolition Derby</title>
		<link>http://tc.eserver.org/29469.html</link>
		<guid>http://tc.eserver.org/29469.html</guid>
		<description>I started The Myths of Innovation in a positive frame of mind, generated by my interest in the topic (and the excitement of seeing my photos in print). I ended the book similarly enthusiastic. While it isn&apos;t a long read (I started in Cambridge and finished before I touched down in Los Angeles), good books don&apos;t need a lot of words to make their point. Scott Berkun clearly presents his arguments, demolishing many of the misconception about innovation. For those of us running businesses or developing new products, it&apos;s a must-read.</description>
	</item>
	<item>
		<title>Top Ten Mistakes When Selecting a CMS</title>
		<link>http://tc.eserver.org/28502.html</link>
		<guid>http://tc.eserver.org/28502.html</guid>
		<description>Selecting a content management system (CMS) can be a complex task, and organizations often run into pitfalls with processes, politics, and understanding the CMS environment. James Robertson outlines a common-sense approach to avoiding the most common mistakes.</description>
	</item>
	<item>
		<title>Succeeding at Information Architecture in the Enterprise</title>
		<link>http://tc.eserver.org/28010.html</link>
		<guid>http://tc.eserver.org/28010.html</guid>
		<description>This article explores some of the approaches needed to ensure that we are successful at implementing IA within organisations, with the goal being to encourage further discussion in the community about these issues.</description>
	</item>
	<item>
		<title>After the CMS Implementation Project</title>
		<link>http://tc.eserver.org/27997.html</link>
		<guid>http://tc.eserver.org/27997.html</guid>
		<description>Much effort is focused, on the selection and subsequent implementation of a content management system (CMS). While it is obviously vital to ensure that the initial implementation project is successful, this is only the beginning of an ongoing commitment to growing and enhancing the use of content management throughout the organisation. </description>
	</item>
	<item>
		<title>Choosing an Intranet Project Sponsor</title>
		<link>http://tc.eserver.org/22085.html</link>
		<guid>http://tc.eserver.org/22085.html</guid>
		<description>Numerous surveys across a diverse range of IT projects have identified that the lack of support from senior  management (project sponsorship) is one of the biggest causes of project failure.  This briefing explores the need for a project sponsor, the role they need to play, and how to choose one.</description>
	</item>
	<item>
		<title>Choosing the Right CMS Authoring Tools</title>
		<link>http://tc.eserver.org/22094.html</link>
		<guid>http://tc.eserver.org/22094.html</guid>
		<description>There is no single best authoring environment provided by a content management system. Instead, the authoring tools must be matched to the job at hand to ensure they are easy and efficient to use.</description>
	</item>
	<item>
		<title>The Difference Between Usable and Useful</title>
		<link>http://tc.eserver.org/22087.html</link>
		<guid>http://tc.eserver.org/22087.html</guid>
		<description>In the past, many sites were redesigned solely on the basis of the vision of a designer. Some of these sites worked  well for users, most did not.</description>
	</item>
	<item>
		<title>Drawing Clear Lines Between Information Systems</title>
		<link>http://tc.eserver.org/22089.html</link>
		<guid>http://tc.eserver.org/22089.html</guid>
		<description>In many organisations, the intranet competes with e-mail, file shares, the document management system and records management. Information is scattered between these systems, making it difficult for users to know where to look. What is needed is a clear policy about when these information systems should be used, and what they are for.</description>
	</item>
	<item>
		<title>Dynamic or Batch Publishing?</title>
		<link>http://tc.eserver.org/22093.html</link>
		<guid>http://tc.eserver.org/22093.html</guid>
		<description>There are two main publishing models used by content management systems: dynamic and batch publishing, and each has its strengths and weaknesses.</description>
	</item>
	<item>
		<title>How to Revive a Zombie Content Management System</title>
		<link>http://tc.eserver.org/22099.html</link>
		<guid>http://tc.eserver.org/22099.html</guid>
		<description>Without care and attention, a CMS can slide into a state of living death. Such systems can be revived by implementing a number of practical (and non-technical) activities.</description>
	</item>
	<item>
		<title>The Importance of Staff Induction</title>
		<link>http://tc.eserver.org/22088.html</link>
		<guid>http://tc.eserver.org/22088.html</guid>
		<description>Staff induction activities are designed to provide new-starters with the information they need, as well as getting  them up to speed on how the organisation works. Induction processes are vital to ensuring that new staff are productive as quickly as possible, and should play a  key role in knowledge management initiatives.</description>
	</item>
	<item>
		<title>Knowledge Management for Front-Line Staff</title>
		<link>http://tc.eserver.org/22096.html</link>
		<guid>http://tc.eserver.org/22096.html</guid>
		<description>The front-line environment must be understood when implementing knowledge management initiatives.</description>
	</item>
	<item>
		<title>So, What is a Content Management System?</title>
		<link>http://tc.eserver.org/22098.html</link>
		<guid>http://tc.eserver.org/22098.html</guid>
		<description>A content management system (CMS) is critical to the success of almost every website and intranet, and yet many organisations are not familiar with this technology.</description>
	</item>
	<item>
		<title>Sources of CMS Uncertainty</title>
		<link>http://tc.eserver.org/22086.html</link>
		<guid>http://tc.eserver.org/22086.html</guid>
		<description>Not all aspects of a content management system (CMS) project are equally easy. While some elements can be installed  &apos;out of the box&apos;, others have proved difficult to implement. The starting point for improving the management of CMS projects is to recognise the sources of uncertainty, and how these affect project outcomes.</description>
	</item>
	<item>
		<title>Understanding the CMS Marketplace</title>
		<link>http://tc.eserver.org/22090.html</link>
		<guid>http://tc.eserver.org/22090.html</guid>
		<description>An important first step is to gain an understanding of the CMS marketplace. This briefing outlines a few of the practical ways of doing so.</description>
	</item>
	<item>
		<title>The Value of Intranet Feedback</title>
		<link>http://tc.eserver.org/22091.html</link>
		<guid>http://tc.eserver.org/22091.html</guid>
		<description>A simple intranet feedback mechanism is an effective way of keeping an intranet up-to-date, and assisting with change management and cultural change processes.</description>
	</item>
	<item>
		<title>What is the Purpose of a CMS Tender?</title>
		<link>http://tc.eserver.org/22092.html</link>
		<guid>http://tc.eserver.org/22092.html</guid>
		<description>There are a number of processes used to select and purchase a content management system (CMS). Many of these  involve the creation of a tender document. Beyond this core goal, it is worth reviewing what the purpose of a CMS tender is.</description>
	</item>
	<item>
		<title>XML and Content Management Systems</title>
		<link>http://tc.eserver.org/22097.html</link>
		<guid>http://tc.eserver.org/22097.html</guid>
		<description>This article explores the role of XML in the context of content management systems, focusing specifically on the business issues.</description>
	</item>
	<item>
		<title>Definition of Information Management Terms</title>
		<link>http://tc.eserver.org/22081.html</link>
		<guid>http://tc.eserver.org/22081.html</guid>
		<description>There is considerable confusion in the marketplace regarding the definition of various information management terms. The scope and role of specific information systems is particularly blurry, in part caused by the lack of consensus between vendors. With the aim of lessening this confusion, this briefing provides an at-a-glance definition of terms for a range of information systems.</description>
	</item>
	<item>
		<title>Information Design Using Card Sorting</title>
		<link>http://tc.eserver.org/22076.html</link>
		<guid>http://tc.eserver.org/22076.html</guid>
		<description>At the beginning of any information design exercise, it is normal to be confronted by a very long list of potential subjects to include. The challenge is to organise this information in a way that is useful and meaningful for the users of the system. A card sorting session can go a long way towards resolving this problem.</description>
	</item>
	<item>
		<title>Intranet Search Reports</title>
		<link>http://tc.eserver.org/22078.html</link>
		<guid>http://tc.eserver.org/22078.html</guid>
		<description>A range of statistics are typically gathered on intranet usage, but of these, search engine reports are by far the most useful.&#xD;&#xD;This briefing explores two key search engine reports that should be implemented on all intranets, and looks at how they can be used  to improve the effectiveness of the site.</description>
	</item>
	<item>
		<title>Intranet Teams: a Leadership and Coaching Role</title>
		<link>http://tc.eserver.org/22082.html</link>
		<guid>http://tc.eserver.org/22082.html</guid>
		<description>The intranet team often becomes viewed as a gatekeeper or  bottleneck that does little more than say &apos;no&apos; to business units. The business then reacts by rebelling against this centralised  control, or simply working around the intranet team.&#xD;&#xD;There is a better way.&#xD;&#xD;Intranet teams should instead look to playing a leadership and coaching role in the organisation. These two  approaches provide a range of techniques for encouraging organisational change and supporting staff activities.</description>
	</item>
	<item>
		<title>More Than Just Finding Policy Documents</title>
		<link>http://tc.eserver.org/22079.html</link>
		<guid>http://tc.eserver.org/22079.html</guid>
		<description>Corporate policy documents have had a long and difficult history within many organisations. While much effort has been put into  creating and maintaining them, they are often more ignored than followed.&#xD;&#xD;This briefing looks at the role of corporate policies within an organisation, and the need to better communicate their message to  staff.</description>
	</item>
	<item>
		<title>Open-Source Content Management Systems</title>
		<link>http://tc.eserver.org/22080.html</link>
		<guid>http://tc.eserver.org/22080.html</guid>
		<description>Open-source CMS has now matured to the point where it should be considered alongside commercial products, but is not without its weaknesses and issues.</description>
	</item>
	<item>
		<title>Why Every Small Website Needs a Content Management System</title>
		<link>http://tc.eserver.org/22084.html</link>
		<guid>http://tc.eserver.org/22084.html</guid>
		<description>While the web design house did a great job, you don&apos;t want to have to go back to them for every change.</description>
	</item>
	<item>
		<title>34 Ideas for Promoting Your Intranet</title>
		<link>http://tc.eserver.org/19151.html</link>
		<guid>http://tc.eserver.org/19151.html</guid>
		<description>The promotion of an intranet is never-ending. From the day it&apos;s launched, through to its eventual retirement, an intranet must be constantly advertised to staff.&#xD;&#xD;Without this, many staff will remain unaware that the intranet even exists. Others won&apos;t recognise the full value of the intranet, or use anything but a tiny corner of the site.&#xD;&#xD;This article outlines 34 ideas for promoting an intranet, ranging from the obvious through to the very unusual. Somewhere in this list should be a few approaches that you can apply to your own intranet. </description>
	</item>
	<item>
		<title>A Better Approach: Requirements-Focused CMS Selection</title>
		<link>http://tc.eserver.org/19155.html</link>
		<guid>http://tc.eserver.org/19155.html</guid>
		<description>Your organisation is unique, and as such, has a unique set of content management system (CMS) requirements.&#xD;&#xD;There is also no single &apos;perfect for everyone&apos; content management system. Each product has its own set of strengths and weaknesses, and distinctive design principles.&#xD;&#xD;Unfortunately, the selection process followed by many organisations doesn&apos;t recognise this, leading to the purchase of a CMS which does not match business needs.&#xD;&#xD;Selecting a CMS does not have to be a lottery. By following a requirements-focused methodology, instead of a features-driven approach, the right CMS can be identified, and the business risks minimised. </description>
	</item>
	<item>
		<title>A Consumer Survey of CMS Vendor Websites</title>
		<link>http://tc.eserver.org/19150.html</link>
		<guid>http://tc.eserver.org/19150.html</guid>
		<description>In March 2003, an online survey was conducted of consumer opinion about CMS vendor websites. This was extensively promoted through the CMS mailing lists, and on key CMS websites such as CMS Watch, the Intranet Focus and Step Two Designs sites.&#xD;&#xD;In total, 168 responses were made to this survey, representing consumers from across the globe, and in every type of organisation.&#xD;&#xD;This briefing provides a high-level summary of the results of the survey.</description>
	</item>
	<item>
		<title>A Content Management Project Presents Unique Challenges</title>
		<link>http://tc.eserver.org/19153.html</link>
		<guid>http://tc.eserver.org/19153.html</guid>
		<description>At a basic level, implementing a content management system (CMS) is like deploying any other large software package.&#xD;&#xD;Fundamental project management principles must be followed, along with best practice technical guidelines.&#xD;&#xD;Beyond this, however, a CMS project presents a number of unique challenges. These must be recognised and addressed for the project to be successful. </description>
	</item>
	<item>
		<title>Five Minute Intranet Self-Evaluation</title>
		<link>http://tc.eserver.org/19152.html</link>
		<guid>http://tc.eserver.org/19152.html</guid>
		<description>How well is your intranet working, and is it meeting business needs? These are the fundamental questions facing many intranets.&#xD;&#xD;Having grown organically for years, most intranets are now suffering from major structural and content issues.&#xD;&#xD;This briefing presents a simple checklist that will allow you to judge just how much work will be required to bring your intranet back to top performance.&#xD;&#xD;Work through this checklist, and tick all those statements that apply to your intranet.</description>
	</item>
	<item>
		<title>The Importance of Content Management System Usability</title>
		<link>http://tc.eserver.org/19146.html</link>
		<guid>http://tc.eserver.org/19146.html</guid>
		<description>The rollout of a content management system (CMS) has the potential to impact on more users than any other system since e-mail.&#xD;&#xD;More crucially, the success of a CMS depends entirely on how much it is used, whether it is authors creating content, or users accessing the published site.&#xD;&#xD;It is these two challenges that place usability as a central issue to be raised and addressed. </description>
	</item>
	<item>
		<title>Is it Document Management or Content Management?</title>
		<link>http://tc.eserver.org/19156.html</link>
		<guid>http://tc.eserver.org/19156.html</guid>
		<description>There is considerable confusion in the market between document management systems (DMS) and content management systems (CMS). This has not been helped by the vendors, who are keen to market their products as widely as possible.&#xD;&#xD;These two types of systems are very different, and serve complementary needs. While there is an ongoing move to merge the two together (a positive step), it is important to understand when each system is appropriate. </description>
	</item>
	<item>
		<title>Metrics for Knowledge Management and Content Management</title>
		<link>http://tc.eserver.org/19157.html</link>
		<guid>http://tc.eserver.org/19157.html</guid>
		<description>Metrics are a concrete way of defining what a knowledge management or content management project will achieve, and whether it met those goals.&#xD;&#xD;In an environment of tight budgets and high expectations, metrics are an appropriate next step for an industry that prides itself on delivering big benefits.&#xD;&#xD;Defining metrics is not easy, however, and much study and further practical experience will be needed before implementing such measures becomes simple or commonplace.&#xD;&#xD;This article reviews the benefits of metrics, outlines some commonly used measures, and presents some practical tips and tricks.&#xD;&#xD;It is hoped that this article will further stimulate the current discussions on the use of metrics in the knowledge management and content management communities.</description>
	</item>
	<item>
		<title>Roles Needed in an Intranet Team</title>
		<link>http://tc.eserver.org/19147.html</link>
		<guid>http://tc.eserver.org/19147.html</guid>
		<description>A multi-disciplinary approach is needed when establishing an intranet team. Due to the diverse range of responsibilities, a large number of skills are required. This briefing outlines the major roles in an intranet team.</description>
	</item>
	<item>
		<title>The Two Faces of Intranet Success</title>
		<link>http://tc.eserver.org/19149.html</link>
		<guid>http://tc.eserver.org/19149.html</guid>
		<description>There are two fundamental aspects that must be satisfied if an intranet is to succeed: the intranet must meet staff needs; sufficient content and functionality must be created to meet these needs.&#xD;&#xD;These are the &apos;two faces&apos; of the intranet, one looking towards staff and organisational needs, the other at the infrastructure and processes needed to meet it.</description>
	</item>
	<item>
		<title>Where is the Knowledge in a Content Management System?</title>
		<link>http://tc.eserver.org/19148.html</link>
		<guid>http://tc.eserver.org/19148.html</guid>
		<description>This column aims to answer the question: where is the knowledge in a content management system (CMS)? In doing so, light will be shed upon the long-term value of a CMS in capturing organisational knowledge, and the role a CMS has to play in a broader knowledge strategy.&#xD;&#xD;Interestingly, the knowledge is not in the content itself. Instead, it&apos;s in the processes and practices that surround a content management system.&#xD;&#xD;By recognising the importance of these supporting activities, the greatest benefits can be gained from implementing the CMS, and the goals of the broader knowledge strategy can be met.</description>
	</item>
	<item>
		<title>Worlds Apart: The Difference Between Intranets and Websites</title>
		<link>http://tc.eserver.org/19154.html</link>
		<guid>http://tc.eserver.org/19154.html</guid>
		<description>Beyond a common use of HTML, intranets and corporate websites (internet sites) are very different animals.&#xD;&#xD;The needs they meet, the content they contain, and the users that access them are all very distinct.&#xD;&#xD;These differences need to be understood by site designers, and reflected both in the design process and the final product.&#xD;&#xD;This article summarises some of the key differences between intranets and websites. </description>
	</item>
	<item>
		<title>How To Evaluate a Content Management System</title>
		<link>http://tc.eserver.org/14169.html</link>
		<guid>http://tc.eserver.org/14169.html</guid>
		<description>Selecting and implementing a content management system (CMS) will be one of the largest IT projects tackled by many organisations. With costs running into the millions of dollars, it is vital that the right CMS package be selected. &#xD;&#xD;This article outlines some of the lessons that we have learnt when assisting clients to chose a CMS. It offers ideas and tips, and provides an approach for identifying your business&apos; actual requirements for a CMS. </description>
	</item>
</channel>
</rss>