UX - User Experience Design
Business case analysis
A Business Case Analysis (BCA) provides a best-value analysis that considers not only time and costs required to acheive the result, but other quantifiable and non-quantifiable factors supporting an investment decision. In other words, I help consider UX pathways to deliver a project, an offer various solutions that should be considered as part of the solution offering.
Goal Mapping a project out with the recommended milestones that should be met to acheive a certain goal.
Mapping a users (or segment of users) contextual experience, on route and within an application. With the intent on helping them acheive thier goal. This helps us as designers to better understand the user by wearing 'their' hat. This will include who they are, where they are coming from, what they are expecting, what are they wanting to acheive, their pains and gains. .
Customer Segmenting and profiling
Segmenting users into customer types allows us to categorise users based on similar characteristic that helps inform product functionality or content. This helps us plan their plan their journies in a system around fulfilling needs and requirements to ascertain a business goal. We to this when informing our designs for whether to display certain content types, pages, or pathways. There are many ways we can segment users, for example they be along lines of; demographic, psychographic, geographic, behavioural and many more.
User journey and customer experience mapping
Similar to other mappings, it allows us in the design process to contextual the users expereince, by understanding the touchpoints they will need to consider to find their goal. These can be light or complex frameworks of decision making steps, that can include psychometric profiles, the customers origin, and the intended end-goal. It helps identify blockers, and find ways to design efficient journies for the user.
A user interview is a UX research method during which the focus is gain an understanding of the product (Architecture, journey, content) from the user's perspective. Specific questions will be created to test a user journey, time taken, understanding, feeling from individual users. These can be quantitively scored, so a baseline score can be given against any task or question from which an average score can be gained for the question. Typically in an interview session it best to have at least 5 users so an appropriate spectrum of users and thought processes can be derived. These are very helpful for gaining insight to help inform a business case, or test a prototype before going into development of a system, feature or product.
Data is a core component of our decision making process and lives at the heart of UX. Most data, in the form of traffic numbers, can be garnished from an analytic program of dashboard. Correlating numbers, pageviews and or goal conversions against their various drivers, whether marketing, notifcation event or infact natural repeat usage, helps us determine whether the user experience was a success, failure, or could do with improvement. Other data sources, are User Interviews with quantitive results, sales data and cost analysis data types, that help determine pricing mechanisms.
Problem solving with UI technology
UI technology is that of user interface technology such as; frameworks, modules, animations, and various artifacts that help inform the user experience. Having a large repository and up to date knowledge of latest trends and emerging technology, means that issues and potential blockers can be diagnosed early and various technology options can be prescribed. UI technology planning during systme and content mapping, allows for clarity when designing, costing, and resourcing a project.
Information Architecture (IA)
Information Architecture or IA as it is referred to commonly, is the structural design of the website. Normally noted as system diagram for complex architecture, or as a table list of parent and child touchpoint for more simpler sites. The process of IA is the strategy behind situational relations of the required touchpoints and user interactions within an app, system or website. This will oftern include various user states, such as not-authorised, and authorised-type users (Admin, Subscription type) etc. where access levels are denoted, with various page restrictions or functionality inclusions. The process will explore the best ways to disseminate information by page structure (not the internal page wireframe), but by highlighting the various content, template functionality types to achieve a certain business strategy. IE an eComerce site will have; home, product, cart and checkout pages.
Prototyping is the process of turning finished designs or wireframes into a clickable and actionable experience to help with design decisions. It allows us designers the ability to test assumptions and ensure that we are delivering a vetted experience. It also allows for user testing with groups or potential customers prior to get feedback prior to release. It is a critical element of the design process and should be completed in some form no matter the project. Also, in many cases it is what is used as the final deliverable for approval prior to sign-off by stakeholders and a point of reference for hand-over as a way to inform development, while holding the overall development deliverables to account.
Wireframe is commonly used to lay out content and functionality on a page which takes into account user needs and user journeys in a very basic structural way, without branding design embellishment. Wireframes are used early in the development process, mapped to each touchpoint in a system map, to establish the basic structure of a page and content types, before visual design and content is added. They help understand blockers and module structure, and can be used in the quoting and costing process for a project, as they are quick to mock up and have the ability to convey the size and scope of individual pages and touchpoints to help stake-holders get a clear picture of project size.