Simon Evans's Blog

Making Intranets and Innovation Work!

What should be in the Intranet Governance Handbook?

Strong governance is key to the success of any intranet project.  My approach to this focusses on 2 key deliverables:

Make sure your governance handbook covers all the criteria you need for effective governance

  1. The Benefit Realisation Plan.  In this document we make the link between business success and what we are trying to acieve with the intranet.  So we discuss vision, strategy, benefits, measures, targets, change management and enablers (technical, cultural or process) etc
  2. The Governance Handbook.  This sets out the criteria by which we will govern, the rulebook if you like, e.g. the age old chestnut of who gets a link in the primary navigation.

It is the latter I wish to discuss in this blog.   Unless you have agreed clear rules/standards/guidelines (whatever you want to call them) you will find it hard to justify your position on any questions that are put to you in the governance team.  Agreeing clear criteria for decision making will save you a lot of hassle later on.

The handbook is then a critical document which will cover a wide range of subjects.  Your “starter for 10” – Below is a farly random (but long) list  of things that I have included in this document in the past.  What is your experience?  What have you included or want to include?  What is missing from this list?  I hope the list may prove useful to some people anyway as a list of things you need to think about and address at some point.

●    Define the purpose of the governance team
●    Document the mandate for the project
●    Scope of the governance activities (Terms of Reference)
●    Using the Benefit Realisation Plan- the most mportant!  Tracking benefit delivery
●    Governance Team structure
●    Define roles & responsibilities
●    Team meeting logistics
●    Maintaining the project plan
●    Exception handling
●    Self service model
●    Communication and promotion plan
●    Feedback/comment handling
●    Change control (for standards and the handbook itself)
●    Management of the information architecture especially the primary navigation (who gets a primary link?)
●    Deployment and uptake approach – marketing plans
●    Acceptable Usage policies, netiquette
●    Technical platform rules (often a separate document)
-Permitted technology framework
-Platform governance (if different)
-Security, Single Sign On and remote access
-Application integration
-Support SLAs
-Directory and profile management
-Service monitoring
-Disaster recovery
●    Content Rules
-Requirements to provide content – responsibility for content creation
-Definitions of different content types
-Editorial roles and responsibilities
-Workflow requirements
-Rules for use of local languages
●    Content Quality Standards-Guidelines for effective web communications
-Content quality measurement – introduce conpetition
-Metadata and tagging requirements
-Search Engine Optimisation
-Content review, retention and archive strategy
●    Brand compliance
●    Metrics – measuring success
●    Managing starters and leavers
●    Regulatory Compliance
-Data Protection,Confidentiality and Privacy
●    Training and support

All this and much more in my 1 day Governance Master Class – contact

Simon Evans

Consultant, EnigmaQuest ltd

October 25, 2012 - Posted by | Enigmaquest, Governance | ,

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: