Phase 6: Launch

    Overview
Launching Your Site
    Managing Handoff
    Promoting Your Site

Final QA/Release
You're ready to go live: all QA testing has been completed on the development/staging server and fixes have been made. Now it is time to move your site to the live server and get ready to track the results of your labor. Remember that you may not be able to catch everything prior to launch. Plan for a soft launch of your site in order to test within the live environment with actual users, without the pressure of advertising or promotion. Run through a series of tests on the live server including primary functional paths, content and product areas, customer service and order fulfillment as appropriate. If there was time dedicated to informal usability testing earlier in the project, the results should be available. Any minor changes should be completed, while major usability changes should be implemented after launch. Do a final check-in with all teams involved, and make sure all systems are "go."

Soft Launch

A site that goes live without the pressure of advertising or formal announcements to the public. It is a chance to test on the live server and get feedback from users. The public is usually told through a press release or a site link that this is a 'soft launch' where errors are still being fixed, and content and functionality is still being implemented in phases.

The Live Moment
The live moment has finally arrived. Finally it is time to pull the switch and make your site available for public viewing. If you have soft launched your site and completed testing and fixes, it is a time for announcement. Prepare for an advertising delay until a week or so after the projected live date just in case additional glitches occur upon actual usage. Monitor the site's performance (through logs) for errors during the first few days and be prepared to roll back to an old version of the site if any major problems arise. If the site is a relaunch, now is the time to track the success of the new site in comparison to the old site's performance (through usage, order fulfillment, feedback, etc.) Back up the site, take screen grabs for promotional use and begin to make plans for the next version of updates and fixes. Update all team members and departments (including Customer Service, Operations, etc) as to whether the push was successful or if a roll back was necessary. Have a drink with your team and client. Celebrate.

Advertising Delay

Don't set any advertising campaigns (tv, radio, print) to begin within the first week to ten days of a scheduled site launch, due to the likelihood of schedule slips and the first few days to iron out any potential problems/bugs. Email blasts, online banners or other announcements (which can be controlled and executed at the will of the client) should only be sent after the site has been cleared of all major glitches and errors.

Confirming Site Security
Keeping your site and customer information safe from viruses, hackers and other outside harm is an obvious priority - but how do you keep your site safe when you don't know who is attacking or how to defend yourself? For most companies, security is a tertiary issue (priorities being employees and equipment, and bottom line revenue.) Having complex passwords that change each month may be inconvenient, but after you've been hacked and attacked, security suddenly becomes a priority. Protect yourself by outsourcing site hosting to a large service provider that has firewalls (programs at the 'gateway' of the server that protects the contents within). Because security is such a complex issue, it is only mentioned to make sure it is addressed by the client or internal team. Stay aware -- hire the right resources to protect you and your company from attack.

Security Tips

While not a comprehensive list, these are some things to keep in mind. These tips will not make your site secure, but are basic protective measures. Outsource hosting to a large service provider - one that has firewalls (enforcing admittance or non-admittance) and proven security measures in place. For internal hosting, hire an IT (Information Technology) specialist to monitor and troubleshoot server issues, including security. Set up a multi-layered protection scheme. Avoid easy passwords. Use a combination of letters and numbers. Don't be concerned with combinations that are impossible to remember -- rather, find the balance between intuitive and non-obvious solutions. Change passwords frequently, and have them 'expire' after a certain amount of time (quarterly or bi-monthly). Restrict physical access to your equipment. Lock doors. Keep passwords out of desk drawers. Pay attention - if you know the warning signs, you have a much better chance of protecting yourself. Monitor your site and its activity. Check server logs. Be aware.

Managing Handoff >>

This original content was created for the Macromedia Techniques Site.
© 1995-2001 Macromedia, Inc.