Website design is more than following a simple template. Follow the process listed below to guide you to a more usable site or application.

What To Do	How To Do It
Plan before you start	Ask who is the user? What are they looking for? When do they need this information? Why? Develop a sample user profile summary. Gather workflow and task requirements.
Choose best practices	Design for probability not possibility. What works? Are there other resources/ other UC's? What kind of standards are we using? Outline the current process (Visio, Word, etc.). Create a navigational model and/or prototype of the new process. Choose phases of the new process if you can't accomplish everything by the deadline.
Design and prototype screens	Prototype screens with the end user to quickly develop functional and intuitive interfaces. Is it clear how to navigate, view, update, delete data? How many clicks does it take? Continue working closely with the end-users.
If you use the GUI template	Implement the consistent style sheets or Portal style sheets, header and footer for your basic template. For Portal applications, refer to How to Use GUI Templates for coding instructions. Make sure your application is WebAuth enabled. Group 'help' topics together, i.e., any user guides, demonstrations, or documentation. If your application uses tabs, limit them to between 6 and 8. If you feel you need more, maybe you should rethink your design. Spell out tab names (no abbreviations). Do not use ALL CAPS. Use sentence case. Example: Name.
Review reserve icon list and Portal style guide	It is recommended that you use icons. Refer to the reserve icon list . Check the Portal writing style guide for consistent language.
Develop system and review form guidelines	Left align columns are for text. Money (currency) should always be right aligned. Minimize columns to two. Guide the user to help. For example, use an icon where the user may need further instruction. Field labels on forms should be aligned to the left for easier scanning and be readable from top to bottom. In addition, the labels should be brief so that users can see the label and understand its meaning. Review the GUI Manual for detailed instructions. Obtain regular acceptance test signatures with your end users to verify system functionality against requirements.
Make your layout easy to follow	Use limited action verbs for command buttons. For example: Search or Go. Limit the use of command buttons. Keep them at the bottom. The common action should be listed first. If you have more than 2 options, re-think your formatting. Keep scrolling to a minimum. Error messages: Give the user an escape route and/or someone to contact. If possible, the error should be displayed as the user is filling out the form, not once they have submitted it. If this isn't possible, review the GUI Manual for detailed instructions. For more information about layout design, review the GUI Manual.
Test your prototype	If your application doesn't have a pilot test group, contact the OIT Web Content Management Group to set up a usability test.
Schedule application review by Team Leaders	An application must be reviewed and approved prior to general use.

Browser not supported