Tag: Requirements gathering
There is a great wave of projects and programs involved in creating engaging experiences for customers, all lacking the essential component of User Requirements. Market requirements, Business requirements, Technology requirements and User Requirements become Project Requirements Project Requirements Project requirements on a project with a UX focus are formed by an amalgamation of business requirements
A great deal of effort is being spent on customer experience and user experience that misses the point, experience is about desire, not process or fulfilment. Desire drives behaviour Thomas Hobbes (1588–1679) proposed the concept of psychological hedonism, which asserts that the “fundamental motivation of all human action is the desire for pleasure”. Georg Wilhelm Friedrich Hegel (1588–1679) claimed that “self-consciousness
Every dollar spent on UX brings in between $2 and $100 dollars in return. This is gained by spending on UX not making things look pretty, it’s not graphics its making the product, service or information system meet the business KPI’s and the customers expectations, desires and needs. Forrester Research finds that “implementing a focus
Investments for HNW and UHNW There are several types of on boarding that relate to both business and investors structure and size, their specific purpose for investing and their local regulatory constraints. The main participants in the investment process I will be focusing on four main participants in this post financial advisers (FA) and investors
Agile User Stories come from UX I have been involved in Agile for a very long time, mainly because it uses methods from the human computer interaction scientific process (CHI/HCI). I’m surprise no one else has blogged about the use of CHI/HCI processes in Agile before, but though I should say something as I keep
This is just a quick post showing the basic level differences between User Experience (UX) Roles and Information Architect (IA) Roles. I’m working on a full model post as well, but that is still being written. User Experience (UX) Roles. User Experience (UX) Roles Diagram User Experience Architect (UX Architect) Gathers requirements, defines the system
Best practice, puting the missing part in a puzzle Requirements gathering in Banking change programs are over detailed, over long and for the most part undeliverable. There is and has been a huge requirement for change in British banking for several years as senior bankers have sought to lever the capabilities of technology and distributed
2011/03/04 – Published UCD requirements gathering There are lots ways to elicit UCD requirements so I don’t intend on listing them all here, what I will note are some of the effective ways that I utilise. They can be described as structured, unstructured or a mixture of the two, but importantly the methods produce differing depth
2011/02/10 – Published People focused Capturing requirements is subject to other peoples availability, this remains one of the most painful parts of the process as few participants seem to understand just how important their experience is to the project. Often a participant can shape the final output without realising they have done so, I include a
2011/02/02 – Published Getting the requirements right It is an understood factor in travel that if the journey starts even half a degree wrong then the final destination will be considerably different from where the person intended to be, this is for many why there is a make do culture when working with technology requirements. Unfortunately