In this fifth and final post on Designing Intranet Structures I’ll be looking at what should happen once you have agreed the structure of your new or re-designed intranet with your users and stakeholders – mapping and continuously improving your intranet.
Posts Tagged ‘intranet maps’
In Part 3 I discussed how the design of URLs can play a big part in forming the initial structure of your new or re-designed intranet. In this post I’ll explain how users and stakeholders can contribute to defining the structure, why iteration is the key to a good intranet structure, why content is important and why thinking of the future is important.
In all of the posts and articles I’ve read about intranets I’ve never heard much mention of URL design yet this can be a key approach in designing your intranet and will also permanently help your users in finding the content they need. If you’re worried that this might sound a little complicated don’t be. The approach I’m proposing in this post is simple and low tech.
This post details the first step towards designing or re-designing your intranet – the system map. This map will define your intranet domains and give the first overall view of the domains that make up your intranet and the things that go in them.
Before any system map can be compiled it is important that in depth user and stakeholder research is carried out as well as a content inventory (see Content Value Analysis). The analysis of these activities will contribute towards populating the system map.