Comments on: “Do We Really Need An Intranet Portal?” – How Valuable Is The Technology You Represent? http://www.intranetexperience.com/ourblog/2009/03/do-we-really-need-an-intranet-portal-how-valuable-is-the-technology-you-represent/ Topics relating to Intranets, portals, enterprise content management, internal communications, and social media in the workplace Tue, 07 Sep 2010 02:19:41 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Senthiljee http://www.intranetexperience.com/ourblog/2009/03/do-we-really-need-an-intranet-portal-how-valuable-is-the-technology-you-represent/comment-page-1/#comment-43 Senthiljee Tue, 28 Apr 2009 07:33:46 +0000 http://www.intranetexperience.com/ourblog/?p=32#comment-43 Good post Sean! Often we forget the basics and talk only the latest creamy thoughts. If we actively think through the basics, lot of ideas would evolve. Keep Helping Good post Sean!
Often we forget the basics and talk only the latest creamy thoughts. If we actively think through the basics, lot of ideas would evolve.
Keep Helping

]]> By: Peter Laird http://www.intranetexperience.com/ourblog/2009/03/do-we-really-need-an-intranet-portal-how-valuable-is-the-technology-you-represent/comment-page-1/#comment-4 Peter Laird Thu, 26 Mar 2009 23:12:15 +0000 http://www.intranetexperience.com/ourblog/?p=32#comment-4 Great post Sean. A few more: 11. Centralized coarse grained authorization policy enforcement (who has visibility to what apps). 12. Tailored user experiences (HR employees should have a different experience than Sales) 13. Process centric user interfaces - a portal can front many back end applications with a unified app experience. This eliminates the need for a CSR to be aware of the myriad of legacy apps necessary to complete a single task. Also, on the topic of alternatives... An alternative to the master intranet portal that sometimes is proposed is the master intranet wiki. The wiki is expected to become the single source of content within the org. This is attractive because it is cheaper than a custom portal deployment. Some wikis are powerful and can be extended with macros, so are attractive options. I am a big fan of wikis, and believe no organization should be without one (or many!) but I believe some of your 10 points speak to requirements that aren't satisfied by using a wiki instead of a portal. Specifically: 2, 3, 4 and my 11, 12 and 13. Great post Sean.

A few more:

11. Centralized coarse grained authorization policy enforcement (who has visibility to what apps).

12. Tailored user experiences (HR employees should have a different experience than Sales)

13. Process centric user interfaces – a portal can front many back end applications with a unified app experience. This eliminates the need for a CSR to be aware of the myriad of legacy apps necessary to complete a single task.

Also, on the topic of alternatives…

An alternative to the master intranet portal that sometimes is proposed is the master intranet wiki. The wiki is expected to become the single source of content within the org. This is attractive because it is cheaper than a custom portal deployment. Some wikis are powerful and can be extended with macros, so are attractive options.

I am a big fan of wikis, and believe no organization should be without one (or many!) but I believe some of your 10 points speak to requirements that aren’t satisfied by using a wiki instead of a portal. Specifically: 2, 3, 4 and my 11, 12 and 13.

]]> By: Dan Kneeshaw http://www.intranetexperience.com/ourblog/2009/03/do-we-really-need-an-intranet-portal-how-valuable-is-the-technology-you-represent/comment-page-1/#comment-3 Dan Kneeshaw Mon, 16 Mar 2009 16:02:03 +0000 http://www.intranetexperience.com/ourblog/?p=32#comment-3 I love the statement about having to have "courage" to ask "why". We need more people doing that. I love the statement about having to have “courage” to ask “why”. We need more people doing that.

]]>