A lot of organizations these days interview user experience candidates asking them to provide a possible solution to a problem in form of a test. I was fortunate enough to take a few tests and made my share of mistakes. The learning has helped me advance better in my profession giving me a methodology of sorts to solve design solutions quickly.
- The solution should be arrived at within a few days time,
- Should exhibit your knowledge of UX methodologies,
- Should provide a set of assumptions that you have used to arrive at the solution,
- Provide good design documentation.
So here is my take on how a design solution documentation should be structured,
- The challenge: A clear brief of what you are supposed to do. Can be in form of notes you have taken or any written tasks you have got.
- The methodology: Describe the steps you would take to design the solution.
- Assumption & Issues: The brief must leave open a few gray areas requiring you to make assumptions. This is a good place to describe your assumptions.
- The BUS Model: The Business, User and the System model – what are the challenges and needs in each of these.
- Scenario: Identify story like scenarios where the user performs a few tasks.
- Personas: Build life like personas with motivation, goals and a typical day.
- Task Analysis: List down tasks or activities the user would perform.
- Information architecture – Create a information architecture schematic detailing how the user can complete tasks.
- Wireframes – Start with basic wireframes. Keep them as low on color as possible.
- Design Rationale – Include your notes on the design rationale for the wireframes. Why you choose one layout over another. What are the primary tasks you hope your design will solve.
- Visual Design – Create a high fidelity version of your wireframe displaying your aesthetic skills.
- Usability Engineering – Describe what type of Usability Engineering activities could enhance your tasks.