Process optimisation
Especially in larger corporations or companies with employees working from many different locations an intranet is often the central tool for internal communication and organisation. We can support you in optimizing the effectiveness of your intranet which leads to increased employee satisfaction and efficiency.
Benefits of a usable Intranet
Improving the usability of your intranet or internally used software such as time tracking systems can lead to many benefits such as:
- reduced error rates
- increased efficiency due to reduction of the time needed to complete a task and better informed employees
- improved productivity and higher work satisfaction which can reduce employee turnover
Target definition
Most intranets we observe go through three phases, and problems often encountered include integration of legacy systems and single sign on. Together we will define the business objectives, feasibility and possible technical limitations. The three phases are:
- Information (files, directories, handbooks, etc.)
- Communication (Wikis, Blogs, Videos, Webinars)
- Process integration (CRM, calculation tools, HR management, etc.)
Stakeholder interviews
In order to familiarize ourselves with your organisation and processes, we will conduct interviews with main stakeholders from each department. This will give us insight in their working habits, needs, restraints and wishes.
Usability tests and ethnographic research
We then perform usability tests or cognitive walk-throughs on your existing intranet. This will highlight the strengths and weaknesses of the current system. In addition, we will observe your employees during a typical working day. This often reveals the best insights in work habits and how the intranet can support their typical work tasks. More about Usability Tests.
Card sorting - building a logical structure
The main challenge in intranets is often the structuring of the abundance of information so that it is placed logically for each and every department. One method to support the definition of the information architecture is card sorting. Every possible content item is written on a card, and users are then asked individually to sort them logically. We then analyse the results and define the overall structure.
If an intranet includes many processes and applications, it might be necessary to look at each part individually to define user flows and typical scenarios.
Wireframes – concentration on functionalities
Once the overall structure is defined, we will look at the individual templates (page types) and required elements and define the wireframes. Wireframes are blueprints of a page without the visual design. They have the advantage that all participants can concentrate on the functionality without being distracted by the visual design. Wireframes also build the ideal basis for functional specifications, the guidelines for the technical implementation.
Visual design
After the structure, page requirements, and elements are defined and afterthe wireframes are completed, we will visualize the intranet based on your corporate design to strengthen internal identification with the brand. More about Visual Design.
