Consider, currently we see things we want to buy through advertising or by seeing it in films or when around other people or places.
Why not; while having a coffee with a friend in their house you see a nice bowl and you say ‘buy bowl’. Your personal IoT ecosystem checks the area and finds three bowls, it asks ‘white bowl’ you say ‘Yes’ the bowl is ordered based upon your personal preference which could be Speed, Price, Colour or anything else, for this scenario it’s Speed it locates the nearest supplier and orders it for immediate delivery. You carry on chatting and the bowel is delivered to your home and waiting for you when you get home. Payment is automated, you unpack look at the bowel and say ‘Great Condition’ feedback allocated.
I’m just going to get this out there because there is a great deal of lying going on that IoT does not affect the UX profession and E-Commerce business.
IoT system design does not require UX wireframes as the are no GUI’s
The IoT is a complex ecosystem that not only changes interactions but also removes many of the common processes that have been adopted by people to use technology.
Situational Awareness Shopping #UI
Graphic User Interfaces are not a consideration for the IoT as the interactive methods used to select and buy are no longer through container websites, advertising (as a separate activity), payment gateways or any other existing copy of a shop.
digital versions of shops are irrelevant in a society run through situational awareness.
Recruiters requesting a UX portfolio can cause a breach of Intellectual Property Rights
So I posted this as an update on LinkedIn I got some great responses from people who read their contracts and got a whole load of really negative responses from people who did not understand the statement so I will try again here. I make no legal determination as part of this post, I am simply reporting an actual event.
First off this is from several actual experiences, years ago in one instance where a recruiter was found to be in Breach of Contract as the Contractor they supplied held on to client work (not in the public domain) and digitally published it as a portfolio breaching the Intellectual Property Rights of the Recruiters end Client. My involvement was discovering the content, explaining the context to legal teams and later hearing about the results.
The recruiter settled out of court, they were sued for $610,000,000, they paid $9,000,000 on the Government Contract, I don’t know what happened to the contractor, their portfolio was shut down in 10 minutes by the server company (a very well known one) after they were contacted, they also supplied a list of every IP that had visited the site.
Research Raw Data
Research Analysis and First Findings
UX Requirements Specification
Key Interaction Models (also known as Eco-systems)
User Logic Models
Demographics and Personas
UX Innovations based upon Insights from the Data, for Interaction Behaviour, Market Targeting/Capture, New Products or Services
Proposed Human Centered Business Models
UX Recruiting Protocol
UX Concept Testing Methods
UX Concept Testing Analysis
Interaction Design Testing
If you understand what UX is then the statement below seems quite reasonable.
The customer experience becomes the intellectual copyright of the client company, showing how it works to anyone opens up an unlimited financial risk to anyone who sees it. Hiding the client name is less important than exposing details of the customer experience that has been created.
One caveat to the above statement, clients cannot own the moral rights unless stipulated in the B2B recruiter contract and the contractor sub-contract, they remain as a veto for the contractor. Also the methods and IP of the contractor don’t become property of the client or the recruiter unless the contractor agrees and is paid for them (a separate contract, from their service contract, with another and more substantial fee).
If a recruiter requires the viewing of confidential information in their role adverts, they are liable as a participant in the contract breach.
Jophy covers it really well here in his update, in the corporate area information security is critical in UX projects disks are required to be wiped after projects and are subject to random checks by security. Having a copy of a project that has been completed for a client or that you leave is considered to be a form of theft.
When recruiters ask for portfolio’s it would be better that they stipulated personal projects only. Or that they change their contracts to allow contractors to show the work they produce as part of their portfolio.
In turn the contract between the clients and the recruiters will need to be changed as that is the point at which a breach is determined to have taken place from a client perspective.
ToddZaki Warfel said portfolios aren’t the problem.
I recently interviewed a few MA grad candidates. One of the best portfolio reviews came from someone who’s showed 2-3 personal projects. We use the review sessions to dig into process and the candidates thinking and doing. Having them use examples they are intimately familiar with is a good way to gain insight.
And that kind of exposes the problem, the recruitment industry has built up with a reliance portfolio’s when experienced recruiters prefer to understand the candidates skill, than look at a portfolio of things the candidate may or may not have created.
I’m only providing this information to help people, if you don’t want to know, then fine. Please don’t respond with self righteous explanations of why your practices are safe, just enjoy your view of the sand.
It’s just the most embarrassing thing to hear intelligent people say UI/UX. It makes professional people cringe because your left wondering should you care that they are exposing ignorance or just let them get on with sounding like an idiot. I mean their ignorance is not your responsibility after all, or is it?
So what’s so bad? Well not knowing that UI is a tiny subset of UX should not be that bad?
It’s the total lack of knowledge that irks, I think. I mean when you first went to school there was always some kid who thought it was funny to pee in the middle of the class room. You look at those who can’t tell this difference between UI/UX in the same way. It’s very funny for kids, but you are wondering why they persist in peeing themselves in public. It’s almost as if its now their party trick and they are scared they won’t get attention otherwise.
Maybe in this respect ignorance is bliss but for everyone else they seem like a slightly odd child.
There seems to be a huge level of confusion around user experience (UX), but one of the key things is that the user interface is not the user experience architecture.
User Interface – what the user sees
Interface Logic – what the user can do
Data Systems – the content the user creates and interacts with
Platform – the users delivery mechanism
user experience is defined by what users can do, not just what they can see
If you are paying for UX you should be asking “how did the UX change the interaction, logic, data systems and platform” if it did not influence it, you only got UI design.
The user interface is the top level component that users see.
The user experience is not a single component it is a set of features that is facilitated through several components.
An update about paying for UX, as business start to recognise that visual tweaks to a product after the solution stage are not enough for savvy consumers.
Also the non-system elements – customer service, marketing and POS material (is this consistent with the message being communicated on the system) etc.
The customer, client or worker doesn’t see the difference – they see one big system.
It is often frustrating to do a piece of research and find out all the weak points in an organisations’ “system” and be told, just tell us what the UI needs to do. It is a rare job indeed that they are interested in the other non-system fail-points of the user experience.
UX is a highly complex set of research tools and outputs, the use of which is dependant upon time, cost and the clients willingness to accept them.
Question 1, why are you there?
If the client were to think in best practice terms which for them would deliver exactly what they require then everyone would have a great experience of the process. Unfortunately it is pretty much a given that clients want to prove themselves knowledgable about well everything, in control and this is one of the main problems. I often hear clients say “I understand our users” or “I built this company so I know what users want” maybe they did or used to, but the fact they have called in an agency or consultancy means they don’t anymore. What clients mostly mean is I have my agenda and I want you to listen to it and agree with me. That way is the road to mediocrity.
What does the client really want?
It’s worth at this point asking the client what they want out of the process. If they only want a pat on the head and to be told they are great, best to give them that, do the job get paid and don’t put it on your CV.
If the client (really) wants their products or services to have higher impact, increased transactions, market share and gain advantage, then explain what your doing, how they gain and that great ux will fundamentally change how they work.
Question 2, what does your client understand about what your doing there?
UX is not UI, the experience is not only the interface, it’s what you can do with the interface, what tasks can be completed, what data can be inputted, transformed or called into the UI.
The real pitch for real UX.
The pitch to a new client is not we can make your product or service like your competitors it’s “we can make your offering stand out from the crowd”. Great ux is about shouting over the noise and changing the rules, “don’t catch up – great ux creates the opportunity to jump ahead”.
Question 3, how will your client know they have succeeded?
This is not a KPI hunt, clients are not really interested in you proving success, they already have their own success metrics, strategic plans and objectives they need to report up the chain. They may not be able to directly tell you as these things are highly confidential the important thing from an engagement perspective is can you work them out? Then can you articulate these back to the client in ux terms.
The real job of ux, find out about the users.
The real job of ux is to align the business with the users, from the user perspective. Users ask “what’s in it for me”, “what do I personally gain”. This means that user research is required by the clients customers, in order to work out what they want for from the business in order to take up their services or buy their products, how they will want to interact and what they will give the business for a relationship.