10 things your intranet portal team should understand. Seriously!

Passageways Blog

There should be one AND ONLY ONE organizational portal. This may be obvious but is worth reiterating here.
Your Senior Management team should be completely sold on the idea of an Intranet portal, as an ongoing commitment and not just the upfront commitment.
Portal software is almost a commodity by now, so choose your vendor based on services, best practices, support etc.
Successful portals should automate some workflows and improve some processes otherwise employees look right through another pretty application which does not do anything for them.
Your portal should provide employees quick access to the information they need to become more effective and productive in their role.get their input.
Portal should be built such that publishing is easy and not too permission heavy. You want people contributing, not shying away.
Work with a vendor that has a track record of continued success.successful portal implementation is like an art.you either have huge success or you create a ghost town.
The portal should support "single sign-on"; that is, with a single user id and password each user can access most of the applications and data that she or he is allowed to use.
Organizations should plan for integration with core systems and other existing software, even if it is a second phase.
Portal landing page should be well discussed and should be flexible- one size does not fit all when it comes to the landing page.

Currently, there are no comments. Be the first to post one!

Post Comment
Name *
Email *
Website (optional)
Comment * Allowed tags: <a> link, <b> bold, <i> italics
Receive email when someone replies. Subscribe to this blog by email.

Passageways Blog