Every project has different outputs and needs. This framework approach allows me to focus less on a rigid process and more on addressing the business and customer goals. Depending on the nature of the project I will implement one of more of the following steps. For example, if the client requires a new solution definition, conceptualisation and evaluation may be necessary. If the project is already in progress only the evaluation may be required.
Definition – What is the problem space?
Definition is intended to establish what the intention of the project is, to understand what’s happening now and how it differs from what needs to be achieved. The focus is on understanding the business, technical and user goals and to tum them into measurable outcomes.
Key output: High-level functional specification
Can include: project scoping document, business case, stakeholder workgroups, user research plan, user research activities, mental models, personas, business process models.
Conceptualisation – What will the solution look like?
Conceptualisation turns the high-level functional specification into a full functional specification including: wireframes, prototypes and user journeys, which are delivered to the design and development production teams. Throughout these steps the solution is validated against business, user and technical goals and revised where necessary through a project control process.
Key output: Full functional specification
Can include: wireframes, user journeys, prototypes, information architecture, stakeholder management, supplier management, technical liaison
Evaluation – Does the solution meet the intended outcome?
Evaluation allows for the specific measurement of the project against the stated business goals. Evaluation can be implemented prior to the definition phase to provide a benchmark for the next phase of development.
Key output: Evaluation report and next steps
Can include: usability testing, expert review, keystroke level mapping, conversion optimisation, competitor analysis.