Transformation: Solution Design
The Design phase is used to interactively develop User Journeys and Visual Design and is validated against organisational requirements defined during insights and planning phase. The purpose of this phase is to experiment with different ideas, flows and visualisations, iteratively improving them based on stakeholder and user feedback. At the end of this phase, designers should feel have the main flows and the Visual Design ready to be implemented.
Design : User Journeys
Interactive workshops are used during design phase to develop iterative way and test alternative ideas using conception and participatory design techniques. Validation is obtained from stakeholders and users. User feedback during evaluation is used to test various different design alternatives. Based on results of evaluations, feedback and results of feedback, a decision on final design is made. During workshop User Flow will be represented as a set of sketches, also known as wire frames, which represent the screens and controls that the user will interact with.
During the early design phases, User Flows Documents are producedfor Reviews by users where business rules, validations and substitution etc can be validated and stakeholders can ensure critical user requirements are being met. These documents are also used by business analysts to validate that it meets the business requirements as documented in planning phase. User Flows can also be used during evaluation to test how usable and understandable the emerging designs are to the target users of the system. This iterative and inclusive design process are used to design usable systems, that also meet project and organizational goals.
As designs develop, User Flows become more comprehensive and may include navigation designs, screen layouts, labels, values within controls, example copy such as instructions, error conditions and messages and validation and substitution rules. When Waterfall methodology is used, the completion of the UI specification is final activity in design phase as far as organisational process design is concerned. The UI Specification is handed over to a development team who use it as the definition of what needs to be built. Whereas if Agile development process, designing and development can run concurrently.
The UI Specification provides a complete definition for what needs to be included within a user interface and how the user interface should work. This is especially useful when a development team is not co-located with the design team or when development is being delivered by an external party. The UI Specification can be used to sign-off the design work and as part of a User Acceptance Test (UAT) to assess whether a solution meets the design requirements.
Insights & Analytics,
Infi Uk Ltd,
105 Holmwood Road,
Cheam, SM2 7JS
Ph + 44 0203 129 128 5