3. Plan a phased approach
Since portals generally integrate a number of applications, these initiatives tend to be highly transactional and commonly incorporate advanced security features. Don't expect to get every feature into your first release. Rather, plan a phased project -- focused on the highest priority business scenarios first -- to ensure initial success. Once the most critical transactions are identified, concentrate subsequent iterations on advanced scenarios and features.
4. Establish a governance structure
Because portals integrate assorted experiences and applications from dispersed business units, there can be governance issues across the enterprise. Clarity around decision-making is critical. For example, if Customer Relations owns the CRM application and Human Resources owns the intranet, what is the process for deciding what to integrate and what to link out of the portal?
Establish and secure the resources required to support the initiative. Without support from the top down, the portal initiative will always be at risk.
5. Invest in training
If a commercial portal product is chosen, realise that portal infrastructures provide a different way of building solutions. To efficiently leverage the platform's capabilities, you need a solid understanding of how the portal platform works. Training thus should be scheduled once the platform is selected.
To gain experience with the portal technology, consider creating a proof of concept. The proof of concept may be structured to mitigate high-risk areas and/or to validate design or user experience. This step should be taken early in the process, both to validate your technical approach and to allow stakeholders to envision what they are ultimately going to get.
Finally, the initial implementation should set standards for the user experience and the technical implementation that should be followed as future portlets are integrated with the application.
