Tag Info

Hot answers tagged

13

Resolve the behavioral stumbling block You make a key observation that it's hard to get users to backtrack from a specific suggestion ("I want this button!") that they are psychologically anchored on. I agree. You can use reason and charm to get a user off a fixation on a specific UX suggestion, but the effort involved in doing that can result in ...


9

I've tried to solve this same question in the past. Here's my solution. Keep it short. Direct them to activities. Focus the issue with a choice: "I'm trying to do something that's not currently possible" OR "I'm doing something and the app isn't doing what I expected" Ask about activities: "What were you trying to do when things went wrong?" This changes ...


9

This won't fully answer your question since you already included part of the answer in your question :) For the part where the user (or the client in some cases) insists on "But I WANT a BUTTON", I have some useful techniques: I re-confirm the user/client problem. I shift him/her from proposing solution to identifying the problem. This may require a lot ...


3

Put it to them this way: these days, the word "integer" gets taught at elementary level. Most people are going to know what it means. I do see their point for more technical terms though - if people aren't going to understand, you have a problem. A possible solution is to add a clickable question mark icon next to technical terms that produces a definition ...


3

When you wireframe first, you are defining a solution before you know what you are trying to resolve. You have to define the problem before you know how to design the solution. Hence, requirements state what a product needs, not the solution. Also are your wireframes literally ideation pieces for discussion, or are you striving towards fully functional ...


2

In fact, this should be written in your agreement, where you agree to provide the system design services and they agree to get you info that you require. When it comes to UX or UCD (user-centered design), requirements, including TA description, PRD and use cases are the most crucial info you can get from your employer/client. That would be the first thing ...


2

There's two issues here to address: getting a proper understanding of what the suggested change is supposed to accomplish, and avoiding resistance or frustration from the customer because "why are you asking me about the problem, when I've already told you what you need to do to fix it?". In my experience it is extremely difficult to resolve this well ...


2

I'm sure this is going to upset several people but here it goes. I personally believe that this is not a user issue. A user is not going to have insightful UX requirements and this is the reason that there is a need for your expertise. Even the most educated people, which have used computers for 20+ years, struggle with computers and the internet as a ...


2

If the majority of the advanced search users are familiar with the difference between "Integer" and "Decimal". (And will I recommend you perform a quick user test to confirm this assumption.) Then consider putting in a small thing to explain terminology for the minority. download bmml source – Wireframes created with Balsamiq Mockups It's ...


1

I completely agree with tohster on this issue. What a great response. I'd post this as a comment, but I don't have enough reputation yet. I've used the "S-T-P" approach, which I see as the core of tohster's solution. That is, Situation Target Proposal Situation Start with the current situation. What are you doing today? How are you doing it? What ...


1

There is a document that is normally being used as the reference for UX definitions of a project, someone call it interaction design document, and I know that in some firms they are calling that UX document. This document normally consists a summary of discovery action about users needs, results of design research and for example outputs of card sorting or ...


1

User Experience desigenrs work with a number deliverables but a lot of these are flexible to adapt to the variety of business goals and work methodologies. Adding to that, the UX field is shifting heavily towards business strategy, which in time will generate new types of deliverables and frameworks. That being said, there is a number of approaches used to ...


1

This sounds extremely frustrating and a very old-school way of developing. Bringing in agile methodologies might just save you and your sanity. Start by working with the client about what features they want developed. This needs to include all dependencies and acceptance criteria - documented! All stakeholders (Marketing etc. ) need to sign-off these ...


1

The following depends on: Their reasons for staying quiet Are they shy & afraid of public speaking? Or busy & annoyed to be there? The culture you're in Do you have authority to ask them to do things, or will they be offended? Is there some seniority or cultural reason they might not voice concerns or ideas? How much time you have for the ...


1

You have a particular set of skills, as does marketing. You're concerned about the twenty percent that gets it, and they're concerned about the other eighty percent. The two perspectives are complementary. I wouldn't assume that your users know their data types as well as a programmer or mathematician would. Why not use "number" with a single input, ...


1

I think marketing have a point. I'd invest in doing some initial face to face user research to actually understand what your customers want and what they understand.


1

What about labeling it "Whole Numbers"? Also I suggest an A/B-Test on this: One with "Integer", one with "Whole Numbers". Which performs better? Btw about question mark icons: I ran a usability test for my bachelor thesis. Findings: No one considered reading the question mark info, even though the answer to successfully ending a task was completely ...


1

You should say to the marketing team, that if the customers are attorneys they have the obligation of knowing what an integer and a decimal are, because a cause can be lost on a court, just from not having the right words proffered. In the Law and Rights area, the attention to the little linguistic details in the text is very important.



Only top voted, non community-wiki answers of a minimum length are eligible