<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:785538786;
mso-list-type:hybrid;
mso-list-template-ids:619118050 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText"><b><span style="font-size:14.0pt;font-family:"Times New Roman","serif"">What steps could be taken to support the introduction of good practice standards in the region?<o:p></o:p></span></b></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><b><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>We need Content Management Strategy and Roadmap: <o:p>
</o:p></b></p>
<p class="MsoNormal">An organization’s vision, mission, objective and long term goals should be understood before starting a Content Management initiative. The Content Management strategy must be aligned with the organization’s goals along with well-defined
Key Performance Indicators. When coming up with the strategy, one must understand the past and current business needs of the organization and envision the future state. This in turn helps to create the right Content Management strategy roadmap. In order to
help prioritize Content Management initiatives and ensure alignment with organizational goals, the Content Management strategy must be clearly communicated to the business and executive management. One must follow a holistic approach in leveraging existing
systems, applications, solutions and create a Content Management platform by consolidating and rationalizing the existing Content Management infrastructure and products without impacting the business. This helps in the standardization of Content Management
platform. Once there is a strong Content Management strategy and roadmap in place, it is easier to radiate and spread the change.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><b>Become disruptive to resistance to Change: Change is something which every human being will resist initially</b>.
<o:p></o:p></p>
<p class="MsoNormal">One must have a mindset of ‘change is something which is constant and will bring in opportunities’. There must be a clear plan for change adoption, first in terms of identifying the like-minded, change-avert people who can influence change
in the organization. They must be instilled with confidence and convinced with a strong business case that the new system is valuable and that change should be implemented. If this is successful, this team will act as your Change Agents across the organization
and will radiate the message and value proposition of the change to the entire organization. The key is to identify the right set of people who are change champions.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><b>Keep the project within the budget and keep the deadlines.</b><o:p></o:p></p>
<p class="MsoNormal">This is a common syndrome for many projects. It is highly common for Content Management implementations due to the lack of understanding on chosen Content Management Product features. Often times, most of the people look at the product
features and assume that they are out of the box features of the product. However, when the content use cases are realized and implementation starts, it may turn out that the use cases require customizations, which would involve more development effort, thus
impacting the project schedules. Hence while choosing the product; the emphasis must be placed on product configurations rather than customizations. More customizations would require more maintenance and support of lights-on projects. Because Content Management
implementations involve all the business and IT units in the organization, the dependencies within the groups must be thought out carefully and included in the schedule.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><b><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>How to overcome lack of Information Governance and Information Architecture:
<o:p></o:p></b></p>
<p class="MsoNormal">This is the key to any content managed site. Information Governance will help define the roles and responsibilities for content authoring, creation, review and approval – which are necessary to ensure that the right content is available
on the sites. This coupled with scalable Information architecture is the back-bone of any content managed site. Information architecture which deals with Content Taxonomy, SEO, Intuitive User interfaces, User experience, Metadata, searchable attributes etc
must be identified before the design of the site is laid out. Any wrong step in this process will lead to a non-user friendly and un-maintainable site.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">5)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><b>How to overcome lack of thoughtful, scalable and appropriate architecture:</b>
<o:p></o:p></p>
<p class="MsoPlainText">This is another key item which is necessary in order to build a strong, scalable content managed site. A great deal of forward thinking in terms of growth of user base, based on future business growth of the organization, must be taken
into consideration while sizing the hardware. Other key items which must be considered are content archival process, site availability, and disaster recovery.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">So that is my two cents….<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Black" size="1"><br>
The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the
sender immediately and delete this message.<br>
</font>
</body>
</html>