Last week we wrote about the most important feature of portal software; its relevance to the user. This week, we’ll take a look at Noodle intranet best practices for creating and managing portlets so you can make your intranet relevant to you at every turn. But first, what are portlets?
What are portlets?
Which portlets should I create on my home page?
Two strategies are commonly employed in setting up your intranet home page.
Top-Down Communication with restricted permissions and static portlets
Traditionally, intranets were used as a top-down communication tool, and this is still a common strategy today. Although intranets today can do much more, you can still accomplish this by pushing important information to employees with static portlets and by restricting permission controls. This strategy alone is useful for businesses that want the intranet to function as a static knowledge base. However, this can hinder intranet engagement, if that is the goal of your intranet.
Horizontal Communication with loose restrictions and dynamic portlets
With the advent of social media and Web 2.0, the intranet evolved to include a social aspect. This enabled employees at every level to participate in content creation. For companies with a more flat organizational structure or culture, looser permission controls and dynamic content can open up the lines of communication and increase engagement. Dynamic content requires less maintenance and content creation by pulling from readily available sources, such as rss feeds, or popular applications. By pulling from applications, you can ensure your portlets are directly relevant to individuals or groups.
So, what are the best practices for selecting portlets for your home page?
Noodle Intranet Best Practices For Managing Portlets
The best practice for managing portlets is to base them on your business objectives and what benefits you are looking to get out of your intranet. Keep in mind the pros and cons of each of the above strategies. Remember, relevance is key! Most businesses can benefit from a hybrid combination of static and dynamic content. Static portlets keeps employees informed if the information is relevant, however it’s unlikely that all your content is relevant for all your users or groups. Dynamic content will keep your content updated, however it may pull less relevant content, depending on the source. Relevant Noodle applications, such as a merged calendar or shared documents can provide functionality, and increase efficiency and engagement. On the other hand, rss news feeds could distract from day to day operations if the feed is not relevant.
Keep in mind that there are headline pages for each section, which can hold portlets that are more relevant to those sections. The homepage should contain high-level content that is relevant across the organization. For example, the merged calendar can show a birds eye view of different departmental calendars, and include an organization-wide calendar.
For more information on Noodle Intranet best practices, or questions on managing portlets, contact our Noodle Advisors.