Step 18: Testing (small group)
The Small Group Testing should include all the developers, designers, content aggregators and people involved in the production process. This is because these people will know the intranet best and be able to thoroughly test it ensure expectations are being met.
Upload the site to a live server, but don't activate it to the public yet. A good way of doing this is to have the root folder's default file (i.e. index.html) have a "coming soon" message and to have the test intranet's main page available at another location (for example, index2.html). Communicate that URL to the Small Testing Group and ask them to return comments, feedback and suggestions within a defined time frame.
When the comments, feedback and suggestions come back, review them with an open mind, but be careful about making changes to anything outlined in the Project Scope Document. Defer those for the next testing stage. For everything else, modify the various functions, content and design as necessary.
In larger organizations, remind your IT department to load-test your intranet server(s) to make sure they can deal with numerous simultaneous users. Having the site crash on the day it launches will not look good.
Note that Quality Assurance and Testing companies (known simply as Q/A firms) are available to do this testing for you, if you wish. They will evaluate a site's design, usability, content structure and overall impact for a reasonable fee.