Tag Archives: publishing

Is your digital workplace experience good or bad?

Intranets are now at a jumping off point to become digital workplaces. In 2015 organisations are no longer just talking about ‘digital’.  People are increasingly using different methods to connect whenever they need to.  When they connect it is to find information, use apps, share some news or ask for help with a work problem.

In my last post I recommended you have clear business requirements, the right direction set with a strategy, support from your stakeholders, and measures agreed that can demonstrate the benefits of your approach.

You also need people to have a consistently good experience every time, with every device, from every place to successfully transform your intranet into a wider digital workplaceWhat can you do make this happen?  I recommend you consider the following:

Within a governance framework you need to implement publishing standards for everything people use across your digital workplace.  People need to be familiar with what they access, no matter what device they use.  This saves time with people not stalling while they check everything before they start using it.

This is easier said than done though!  Firstly, you need to identify your business requirements for your publishing standards.  Once this has been done, you can then develop what publishers need to do to implement each standard.

The difficult bit is getting your publishing standards applied to all your content and apps, whatever device someone is using to access them.  But you have to do this to be consistent.  Without achieving this, people may doubt what they are using because it may look different and the experience vary too much.  For example:

  1. Ownership: Every piece of content and app has an owner who can be contacted for further information.  Think about how you need to show this for each device people may use.
  2. Timeliness: Every piece of content has a review date that gives people confidence they can rely on it being accurate and current.  Again, think about how this can appear for every device.
  3. Findability: Every piece of content and app, in whatever format is needed for each device, is indexed by your search engine so it can be found quickly.  Making sure it is properly tagged by your publishers will also help people find what they need more easily.
  4. Usability: Every piece of content and app should consider mobile users first.  That can be a big change of focus.  More and more, people will use a smartphone or tablet to access what they need.  Test your content and apps with these devices to get the user experience right.
  5. Navigation: Every piece of content and app needs to be linked together so you can quickly move from one to the other.  Menus need to work with every type of device and will need testing before implementation.  You don’t want oasis of content that are disconnected from each other by a digital desert.

You will need to include in your governance framework how you can achieve this.  Publishers will need to be trained on how to use the publishing tools obviously.  For collaboration tools that really should be by following simple guidance because they are very easy to use.

However it must also cover what your publishing standards are, why they need to be implemented and most importantly, how that will be achieved.  You need this for a common platform of knowledge and understanding across your publishing community.

Follow up the training for your publishers by educating them with simple processes to publish content, develop apps, etc., and support their publishing needs with guidance, Frequently Asked Questions, discussion groups.

Taking this approach will help give people a consistently good experience every time, with every device, from every place to successfully transform your intranet into a wider digital workplace.

 

Accessible content for everyone and every device

Everyone whether they have a disability or not needs to have the same experience when using any intranet information or applications. Employees with a disability may use devices to help them. Your intranet needs to be compatible with these to avoid risking breaking the guidelines and any law that applies in the country where the person works.

Accessible content is also easier to adapt to use with mobile devices e.g. smartphones, tablets, and laptops with their different screen sizes. Try thinking of accessible content as being a step further on from it meeting your usable standard.

If your intranet has information or applications that are not accessible to all employees, you will be breaking the web accessibility guidelines. Legislation and codes of practice based on the latest World Wide Web, Web Accessibility Initiative (W3C Accessible content WCAG 2.0 AA) guidelines will apply in most countries. US Section 508 and UK DDA 1995 are two examples. These guidelines are at three levels, A, AA, and AAA covering the most basic problems to the most advanced problems experienced by people with a disability when using your intranet.

Many organisations find it difficult to see the benefits from publishing standards.  I remove the barriers to show the benefits from each publishing standard in this series of posts.  Publishing standards aim to:

  • Reduce the risk of sensitive information leaks
  • Improve the overall user experience
  • Make people using your intranet more satisfied with it
  • Improve people’s productivity
  • Improve people’s quality of work

Benefits

Knowing that you are helping people with disabilities to use your intranet gives three main benefits:

  1. People with disabilities using your intranet will have the same or similar experience to anyone else. This will encourage more frequent and extensive use because the intranet is accessible and usable and meets the needs for everyone.
  2. You can encourage your publishers to make their content and applications accessible to meet their legal requirements. There is the added, sometimes overlooked, benefit that accessible content also displays well in other devices such as tablets and smartphones if it meets accessibility standards.
  3. Your organisation complies with a legal requirement. It can also see investment made in your intranet has the benefit of being available in other devices that help with new ways of working and while mobile.

My next post on navigation will be the last in this series.  I hope you have found them helpful.

Why is the Scottish referendum similar to intranet governance?

Last week the people of Scotland took part in an historic vote to decide on the level of democratic governance they felt best met their requirements.  Did they want to have a full devolved level of governance where they made all their own decisions?  Or did they want to have a framework balancing the right level of central direction or strategic governance while meeting local requirements?

I thought it sounded familiar and I realised how our intranets have a similar approach.  If your intranet is out of touch with what your organisation, users, and publishers need to help them then you haven’t got the balance of governance right.

So, what are the lessons we can draw from this to help how we manage our intranets – whether they are based in Scotland or global?

  1. Keep in touch with everyone involved in how your intranet is managed and used.
  2. Find out what they require and plan how to meet their needs.  No last minute pledges that are not fully thought through!
  3. Have a framework with roles, responsibilities for all levels that can be flexible to meet new priorities.
  4. Make sure your approach to governance is in tune with the culture of your organisation and mood of people using your intranet.
  5. Don’t be afraid to ask people what their view is and hold the equivalent to a referendum to find out.

Can you risk your sensitive information leaking?

Can you risk your sensitive information leaking?  Many organisations find it difficult to see the benefits from publishing standards.  I remove the barriers to show the benefits from each publishing standard in my next few posts.  Publishing standards aim to:

  • Reduce the risk of sensitive information leaks
  • Improve the overall user experience
  • Make people using your intranet more satisfied with it
  • Improve people’s productivity
  • Improve people’s quality of work

Information needs to be correctly categorised so people can access all the content they have permission to view and use. Balance the different needs so information that people can access is easily available and does not hinder their work by unnecessary logins or passwords. Your organisation must also feel confident sensitive information is not at risk.

Permissions need to be correctly set so information complies with your organisation’s Information Retention Policy. This also applies to applications e.g. HR information about pay and performance, which can contain sensitive information. The different levels of permissions needed by your organisation will vary depending on its culture and purpose.

You also need to consider at the site level as well as at the organisational level. Here owners of a site can decide who has permission to use their site for different activities. This will vary depending on the publishing tool used and the culture within your organisation.

Data Protection, particularly Personal Data and European Union rules for its use and storage, may affect your intranet systems, particularly Human Resources systems. Within the European Union, it varies on what is published about individuals and even how it is published. Some information needs permission from an employee before it can be published. For other countries it can be shown without this within the same organisation.

You need to take advice from HR and legal experts to ensure your intranet and content owners comply. Sometimes it is better to take extra time and steps to keep good employee relations and follow your organisation’s values and culture even if strictly you do not need to for some employees.

Copying any content, especially an image, photo, or multi-media file, from another website to insert on an intranet site can be an infringement of copyright unless you have permission from the copyright owner.

Benefits

Knowing that you are protecting sensitive information across your intranet gives three main benefits:

  1. People using your intranet will be confident the information they are using has the right level of permissions set and they are able to rely on who has access to any sensitive content.
  2. For you it is also important from a governance view to have confidence the correct people are using the right information. You have integrated your training, guidance and support for publishers to help establish a common understanding. This prevents sensitive information being available to people who should not permission to see it.
  3. Your organisation can be confident your intranet complies with its information security policies. The risks of sensitive information leaking are reduced which could risk damaging to its brand and reputation.

Are there other benefits you have found?  Please let me know.

In my next post I will cover content needing to be found.

Is your governance good enough for SharePoint?

I have written many blog posts on SharePoint based on my first-hand experience from developing strategies through to the full implementation of features such as TeamSites, MyProfile, etc.

One of the most common requests I get from clients is “How is the best way to manage their intranet while using SharePoint?”  This question is asked because SharePoint is a ‘big beast’ and needs a more rigorous and broad governance framework that is good enough for the challenge.

Your approach needs to consider:

  • Restricting use: stopping some features from being used e.g. SharePoint Designer
  • Encouraging best practice: making sure guidance and training are available
  • Preventing problems: checking content before it is published

Each of these approaches can support your governance strategy for
SharePoint.  The key is to understand what you need to use SharePoint for most of all.

My first-hand experience at BT and from working with clients is that well planned and managed governance is good enough to gain the benefits from using SharePoint.  It is how you approach this which is the critical success factor!

You can out more information on how to build good SharePoint governance to help you.

How to manage your intranet

After you have developed a clear intranet strategy as explained in my post ‘How to develop an intranet strategy‘ you then need to follow this with an implementation plan, publishing standards and a governance framework.

While every intranet is different there are some common factors that need to be considered so your intranet supports your business requirements:

  1. The size of your organisation will affect how you manage your intranet.  If it is based in one location and you know everyone by their first name then it is likely you can manage your intranet on your own.  If it has many thousands of people in many locations you will need a different approach and involve other people to help you manage your intranet.
  2. The type of organisation will affect how you manage your intranet.  Is it streamlined on administration, informal decision-making?  Or is it more formalised, committee driven, when making decisions on how publishing standards and intranet roles and responsibilities?
  3. The culture of your organisation will affect how you manage your intranet.  Is it a very top down, command and control, culture with feedback discouraged?  Or is it more open, democratic and consensual?  Whether it is either or a mix of both will influence your approach to managing your intranet.

My first-hand experience and from working with clients is that intranets can be managed well no matter what size, type or culture your organisation has.  It is how you approach this which is the critical success factor!

You can out more information on how to manage your intranet to help you.

Chaotic or consistent: What is your intranet experience?

I recently wrote a guest post on how you can change a chaotic intranet experience into a more consistent and better experience.  I showed how a governance framework that has roles, responsibilities, and publishing standards that are implemented smartly can encourage people to use the tools and information more frequently and deeply with consistent design, features and structure.

You can read ‘Chaotic or consistent: What is your intranet experience?’ here.