A UX process for websites

Although everyone follows a similar path during the UX design process it does differ depending on the size and complexity of the project. A ‘perfect’ UX process for building a website is hard to define and would also be hard to adhere to. However, what can be done is to define ‘a’ UX process which describes the various steps and tools that can be used and it is up to the UX designer to use those that best fit the project.

Key points to remember are that even though these steps are laid out in an order there is always going to overlap between them, and they are always going to be iterative. They have to be.

Strategy

Strategy as a first step in the UX process is vital as it helps define the business. It helps form a better idea of the brand, the goals of the project and the long term plan for the business. All this done before getting into too much detail. Generally, strategy will be defined in conversations or workshops with the key stakeholders of the business.

Discovery

Discovery is about research and the names are often used interchangeably. However, Discovery is used here because a large part of a project is ‘discovering’ the requirements of the project. This can be done best by speaking directly with the business, so workshops are often the most effective tool to use when determining requirements. Other common tools to use during Discovery include user analysis through interviews and personas, online competitor research and analysis, existing analytics review (if available), definition of key flows using customer journey mappings and more. Refer to UX techniques listed here for more information… 

Concept

Ok so the research has been done, requirements have been documented and analysis has been undertaken to provide some insights. Now it’s the ideas time. Tools that can be used here are: group brainstorming sessions, storyboards and rapid visualisation of key pages into sketched wireframes.

Prototype

The process during prototyping should be collaborative and iterative. By involving ideas from various people and constantly validating any ideas and assumptions the end result is a stronger design. Prototypes can be built to varying levels of sophistication. Sometimes fully designed and developed HTML prototypes are used, whist rapid prototyping tools such as Axure and Balsamiq provide a faster way of getting something to show and test to the users.

Testing

User testing can take two forms. Testing from within the business and testing external to the business. Both are important and the results from each may differ. Ideally, internal testing should happen first and any insights gained from this can be applied to the prototype before external testing is undertaken. During testing again any insights learnt should be applied to the prototype if possible so the next tester sees the ‘improved’ prototype. This is where the rapid prototyping tools described above are more useful than an HTML prototype.

Implement

This is where the tested high fidelity prototype produced above is turned into an actual functioning website. It’s an exciting time seeing it all come to life. In this step the UX designer’s role changes to that of a guide to ensure the vision for the project is realised.