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.
Knowing that you are protecting sensitive information across your intranet gives three main benefits:
- 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.
- 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.
- 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.
Posted in benefit, digital workplace, governance, intranet, search, standards
Tagged benefit, best practice, digital workplace, governance, intranet, publishing, search, standards, value
On day 2 of the WCMS14 conference I ran a workshop about mobile collaboration. People can help each other or can ask for help to collaborate. Having mobile access means you can do this whenever you need to and not have to wait any more. To achieve this there are four areas to focus on:
- Make it easy
- Manage it smartly
- Technology has to meet business needs
- Involve people with mobiles
1. Make it easy
The main point is to create an overall consistent experience for people whatever device they use. With more mobile devices than traditional PCs being sold now, organisations should put the need of mobile people first.
By removing the barriers, mobile users don’t need extra logins to be able to collaborate online. It should also be possible to collaborate while offline and the tool synchronise and update automatically.
Research with mobile users what they need most to help them collaborate online, what experience it needs to be and identify tools with the best adoption rates and understand why.
Manage it smartly
It is important that any governance is built to help people collaborate while mobile and not hinder this aim. By extending existing publishing standards to cover mobile use appropriately you continue with one governance framework. The same applies to roles and responsibilities for content and app owners as well as intranet managers.
The findability of content is critical. Having one search engine that covers all the information architecture helps to achieve this. The decision over whether you have one version of the content or app which is responsive to different designs or different versions for each size screen will depend on the information architecture you develop and on security needs.
How long is it before information become knowledge? Your answer to that will decide whether all your collaborative content stays online and is searchable or is archived after a period of time or inactivity or removed permanently. There are no right or wrong answers but you do have to decide what is best for your organisation.
Technology has to meet business needs
Make sure you have the right solution for the right business requirements. This means being very clear what you need before you start to research the technology that can meet your business needs. It will probably also mean you don’t choose the top solution, partly due to the costs, but also because it provides features and functions that you have no immediate or foreseeable need for.
Any technology for mobile collaboration bought or developed needs to be configurable and shown to work with existing systems and platforms.
You need to consider how many operating systems your organisation will support for the different mobile devices used for mobile collaboration. This needs to cover the issue of BYOD. A balance needs to be struck which may be something like x number of operating systems will be guaranteed to give a good mobile user experience and support y mobile devices. You can choose other mobile devices but you should not expect to be guaranteed a good mobile experience.
Involve people with mobiles
You should not assume what collaboration tools people with mobile devices need. You need to research their needs not just make something accessible from a mobile device and say the experience is good enough.
Involve people at the earliest stage of developing the user experience. As soon as the development is good enough for basic use it should be thrown open to mobile users to test out. They can feedback any problems or improvements that will help them to collaborate better to be acted upon.
A perpetual beta development status can be adopted for the mobile collaboration tools to avoid long delays in improvements, the need for major re-launches. Small, incremental, changes can be made quickly based on clear feedback and involvement from mobile users.
Lastly the testing can be a formal User Acceptance testing approach or more informal and open to anyone with a mobile device to use at any time. The process needs to be transparent and a playground/sandpit available where all development can be tested out. This may need IT to change its approach!
- Remove barriers that prevent adoption
- Have one governance framework
- Right mobile collaboration tools that meet needs
- Involve people who use mobile
Posted in best practice, beta testing, collaboration, governance, mobile, publishing, search, standards, usability, user testing
Tagged best practice, beta testing, collaboration, governance, intranet applications, search, standards, usability, user testing
In my last two posts about the digital workplace I have covered an example of how field-based people use the digital workplace. I then covered how people’s perception of the digital workplace should be more than just considering it is for office-based people only.
But is the digital workplace the best term to describe the new ways of working that people are adopting? Is a term like ‘digital working’ a better description than ‘digital workplace’?
Firstly I don’t get too bothered about terms. As long as there is a common understanding between me and the people I am communicating and working with then that is fine with me. But it does help if that understanding can be easily achieved using a term that is meaningful.
I describe this simply as ‘Work is something you do, not a place you go to’. In a digital workplace you can:
- Work from any location or while mobile
- Have the same or similar online experience
- Collaborate, search, and complete tasks online
- Choose what tools you can use to do this
- Feel comfortable whenever you are using it
- Be confident you can use it when you need to
- Have a better work/life balance
There are other, more detailed, definitions that describe the digital workplace.
But isn’t that explained as well by the term ‘digital working’? It removes any ambiguity about it only referring to office-based rather than field-based or mobile people’s ways of working.
Is it better and maybe more meaningful to use the active term ‘working’ rather than something passive like ‘workplace’? Does the increasing use and influence of mobile working also mean we should consider using ‘digital working’ now?
What are your views on these terms? What best suits how your people in your organisation now work? Is it ‘digital workplace’ or ‘digital working’ that we should be using? I would love to hear from you.
Posted in collaboration, community, digital workplace, engagement, governance, intranet, mobile, search
Tagged collaboration, digital workplace, engagement, governance, mobile, search