Tag Archives: wiki

I wrote a book about governance: ‘Digital success or digital disaster?’

Posted on May 11, 2015 | Leave a comment

When an intranet loses its usefulness over time, and people become disengaged and end up working around it rather than through it, I often find that the strategy and governance have been neglected.

Even a strong and appropriate strategy will founder if the governance isn’t in place to execute it.

I see governance as the foundation of a great intranet, and by ‘great’ I mean an intranet that is useful, useable, and supports the organisation’s goals and people’s needs.

I often blog about intranet governance, but my brand new book offers a lot more than I could ever drip-feed via short posts. Writing a book has helped crystallise my thinking around governance, and delve deep into my past experience as an intranet manager, and as a consultant.

Take a look at my book now – it’s called ‘Digital success or digital disaster?’ and I mean for it to be relevant to intranets, collaboration, digital workplace and mobile workspace governance, while focussing on intranets.

I’m so pleased to have it published through Intranätverk, it’s been great to work with Kristian Norling and his team. Seeing the final book on my tablet has made the months of writing all worth the effort. I’m thrilled to be able to offer you my experience, guidance, and tips and hope you’ll consider my book a toolkit to better governance and a better intranet.

Please take a look at what the book offers you and your organisation – this is a ‘business book’ that should help organisations of every size, but I also hope it’s of interest to individual practitioners and ‘lone intranet managers’. I think this book can support you.

* Digital success or digital disaster? – Book available now.

* Follow me on – let me know what you think!

I agree the digital revolution is cultural, not technological, and….

Posted on April 22, 2015 | Leave a comment

In Gerry McGovern’s latest post he says ‘Digital transformation is cultural transformation first and foremost. Some time ago, I dealt with an organization that had just installed collaborative software. The problem was that the employees saw no benefit in collaborating. Surprise, surprise, collaboration didn’t happen. Collaboration, first and foremost, is a cultural thing, not a technological thing.’

While I agree with Gerry as far as he goes, I also believe the type of governance deployed for collaborative content can be a major barrier to people adopting these tools. Too often the governance used for accredited content e.g. policies and news articles, that are official and factual is also tried (and fails) for collaborative content.

A more ‘light touch’ form of governance is needed to remove the barriers that prevent people wanting to share their ideas or offer suggestions that may help someone with a work problem. Here are some examples of what I mean:

Posting on a blog or contributing to a discussion group should not need you to ask for permission before you start. It should be ‘on demand’ so there is no delay between when someone needs to use a collaboration tool and being able to. Often the need is urgent and passes quickly so any barrier preventing its use could mean the content is lost forever.
You should not need formal training before you use the collaboration tool. A) the tool should be so easy to use it isn’t needed and B) understanding how to comply with the publishing standards such as ownership and content review dates shouldn’t be required.
Usability and design shouldn’t be something you need to bother with. The important thing is your content. Make sure the template you use has the right functionality that people can just start using and understand easily.
Adapt and embed as many of your publishing standards that are relevant to collaboration into the templates e.g. navigation menus, field for contributor to enter their personal details.

Taking this approach shows how the culture has changed from a ‘command and control’ view of governance many years ago for a limited amount of corporate content. Now, many people can use a wide range of collaboration tools to publish their views and opinions and be comfortable with the experience and knowledge that the content is managed appropriately.

The governance adopted fits the cultural revolution and helps, not hinders, it. Long may that continue!

Turn company jargon into a knowledge gold mine

Posted on June 17, 2014 | 1 comment

I have worked with many clients to improve their intranets. I find that each client has its own language and specific terms that are known by more general terms with intranet professionals.

This can be an abbreviation, acronym, or term used within parts or the whole organisation. While it may help conversations online within an organisation it can often be a barrier to other people not familiar with these terms.

I call this jargon. The risk is people don’t ask every time they hear company jargon and take an educated guess what it actually means. Sometimes this is right and helps build up future understanding but many other times it will slow progress or even cause mistakes to happen.

The more jargon used, the harder it is to understand what is meant, and can lead to projects overrunning, costing more, or having a poorer outcome than expected. Some of these costs will show through to the bottom line.

What I don’t understand is why more organisations don’t recognise this and do something about it. Creating a corporate wiki that is open to every employee to create and edit is a quick, cheap and easy way to turn company jargon into a goldmine of knowledge.

Publishing all the jargon – acronyms, shortcuts, abbreviations – as items in a corporate wiki helps people to understand more easily and quickly what they are. It also helps to prevent mistakes being made and time wasted through misunderstandings.

It will also be a wonderful tool for any newbies being inducted into the organisation’s approach, culture and ways or working.

Why not turn all that company jargon into a knowledge goldmine and create a wiki that can contain them for every employee to view, add or edit to?

1 Comment

Posted in best practice, collaboration, community, engagement, help, intranet, social media, value, wiki

Tagged best practice, collaboration, engagement, social media, value, wiki

Strengthen employee engagement while working remotely

Posted on January 13, 2014 | 2 comments

Happy New Year to you! I hope you had a relaxing break and have recharged your batteries for 2014.

I was recently asked by Simply Communicate to follow up my 2014 predictions with one for internal communications. Here it is:

Organisations increasingly face the challenge of how to strengthen employee engagement while their workforce increasingly work from remote locations or while mobile. There is a great opportunity for internal communications to take a leading role with developing a plan that addresses these challenges with greater use of communications channels.

What is different now from previous years is the range of tools and know-how which can be used to successfully have engaged and mobile employees. The key to this will be the rich experience employees will have online as they are able to read communications when they need to, where they need to, and be able to share, feedback, rate the value of the messages with other people who share a similar interest.

An example of this could be combining collaboration tools with traditional online communication channels will help provide that rich experience so a key company announcement video, CEO blog post and detailed background information available is strengthened by a discussion forum managed by internal comms to continue the conversation with quick polls on the awareness and understanding of key messages.

It is how it is implemented and how it is managed within a wider governance framework will help decide how successful it will be. Good luck with whatever you do in 2014!

Read about more 2014 internal communication predictions from simple communicate.

2 Comments

Posted in blog, collaboration, communication, community, engagement, mobile, podcast, social media, value, wiki

Tagged blog, collaboration, communication, engagement, mobile, social media, value, wiki

Valuing information tip 3: how to manage collaborative content

Posted on October 7, 2013 | Leave a comment

In this series of posts ‘Showing the value of your information’ I help you with tips and advice. In my last post I covered how to make sure your accredited content is up to date so people using it can rely on its value. I now want to cover collaborative content in this post.

collaborative content

Collaborative content can be owned by everyone, an individual or community. It can be an opinion expressed in a discussion forum or blog post. It offers a personal view which may be right or wrong and may change frequently. Other people can support and build on that view or challenge and change it.

Collaborative content is less stringently managed because it needs lower levels of trust. Many of your publishing standards are optional for collaborative content e.g. no review date or security classification normally needed. However what you do need to see is the:

Name of contributor to a discussion thread
Name of blog owner
Name of person making a comment on blog post
Date (and time) when comments were made on discussion thread
Feedback link to raise issues with discussion forum owner e.g. report abuse

how to show its value

This is not so easy to manage! Normally comments made in discussion threads or to blog posts on the internet are managed by the amount of continuing interest shown by the large number of people updating it. The content remains on the internet but if fewer people use it, it won’t appear in the top search results or be prominent in discussion forums, unless you dig deep enough to find it.

When a comment in a discussion thread on your intranet is made that type of behaviour can’t be replicated. Even the largest intranets only have a fraction of the number of users compared with the internet. A different approach is needed which creates the dilemma I mentioned earlier.

You can remove discussion groups and blog posts if there has been no activity with them after a period of time. An advance warning of what is planned if no one adds to the discussions can prompt it re-energising. But if it doesn’t do this what should you do?

If the content can no longer be found then people don’t get distracted by out of date information when trying to share their views or solve a problem raised by someone else. However it may be that nugget of wisdom is buried within a discussion thread and lost forever because it can’t be found.

A strong governance framework can help you to decide what content to keep, remove, or delete and who is responsible for making those decisions.

4 ways and 3 benefits using a wiki to develop policies

Posted on April 15, 2013 | 4 comments

An organisation’s purpose involves how to manage how their people behave by encouraging, sometimes even mandating, how work tasks need to be carried out and by whom. In my last post I asked ‘Why not use a wiki to develop policies?’. How would using a wiki to develop work in practice? Here are four ways to consider:

You need to have the right culture which will encourage people to contribute and feel comfortable challenging what exists and being constructively critical.
You need ground rules, or terms and conditions, or guidelines which set out clearly what the expected level of behaviour is for anyone using the wiki.
Make sure the wiki is easy to create and edit as well as to read. Anyone who has used Wikipedia will know it is a very different experience if you want to create/edit an article compared with reading it!
I recommend the person responsible for the policy adds a draft – something which makes sense but its structure and content is loose enough to encourage people to edit – and asks anyone interested to contribute. It is much easier to comment upon what exists than to start with a blank screen.

It is best to start with a policy that affects most or all people working in the organisation. Choosing a Human Resources policy best fits that aim. A policy on employee’s terms and conditions; holiday – how much and when it is taken; flexible working hours – shift patterns; and grading and pay rates. All of these are policies people will have a view on what they believe is appropriate and will help build up a policy that is accepted by most other people.

Why should your organisation take such a risk?

My answer is “Why not?” I believe there is very little to be risked if you pick your first policy to be one that has widespread interest and is not seen as being contentious.

One way to encourage stronger engagement with people within your organisation is to ask for their views and listen and act upon them. Giving people the opportunity to shape a policy which affects them means there is a stronger chance of buy-in to the final version and the impact it has.

When organisations treat their people as adults with a chance to express a view you will generally find it is taken seriously and the outcome is very good. This applies to blogging, micro blogging, feedback, and discussions that are moderated by the members of the group.

Here are three benefits to consider:

It is probable that a better thought through policy will be developed that takes account of many more concerns and points than an expert or small project team could expect to include.
It is likely to be completed in less time with less effort. And if it doesn’t work an organisation should be honest and explain why e.g. too few comments, too negative, and pledge to learn from the experience.
Less time, effort, and costs will be spent policing the policy in future if everyone has had the opportunity to influence its development.

So, go on, why not use a wiki to develop a policy in your organisation?

4 Comments

Posted in collaboration, community, engagement, intranet, social media, wiki

Tagged collaboration, digital workplace, engagement, intranet, social media, users, wiki

Why not use a wiki to develop policies?

Posted on April 10, 2013 | 2 comments

Ever since organisations have existed there has been a need to manage how their people behave by encouraging, sometimes even mandating, how work tasks need to be carried out and by whom.

There can be various reasons for policies: business, regulatory, and legal are the most common. The way that policies are created, updated, and developed has changed very little in my experience working in or with organisations. There will normally be an owner, champion, or stakeholder who will have overall responsibility for creating and managing the policy throughout its life cycle.

When a policy is created or needs to be reviewed it will normally be the owner who will start some form of a consultation exercise. This may simply be an email to a few people across the organisation who are most affected by or can influence the policy asking if there are any changes they need to be made existing policies or what needs to be included to new policies.

It may involve a more robust approach being taken:

maybe a focus group
a request to a wider audience who have an interest in the area of the policy
or a project team who work through the detail and check back with their business function or stakeholder for guidance on the progress being made.

The variety of approaches used by organisations when creating new policies or reviewing and updating existing policies hasn’t changed much in recent years.

But the ways that organisations can now engage their people to create or update policies are changing. There are new approaches being used which help encourage people to be more involved in what their organisation’s purpose, aims, values, and culture – amongst many others – should be.

Adapting social media tools used successfully on the internet include:

people using blogs to give their views and opinions
feedback any questions to news articles
share information through discussion groups about a wide range of work related activities.

I believe a corporate wiki that any person in the organisation can use is a great way to create a new policy or to update an existing policy. It gives the chance for any person with an interest in the policy – maybe they are affected by it and want to improve it – to give their views.

Have you tried this in your organisation?

2 Comments

Posted in collaboration, communication, community, engagement, publishing, social media

Tagged collaboration, communication, engagement, publishing, social media, users, wiki

Tag Archives: wiki

I agree the digital revolution is cultural, not technological, and….

How can I help you?

Recent Posts

Archives

Mark Morrell

Follow “Mark Morrell Intranet Pioneer”