Usability Testing

• A

  Show/Hide Password
  password • • Avante  

  2
  0
  Votes
  2
  Posts
  1
  Views

  B

  This is possible, technically. But I think this is not a good practice as the password will still be fetched from the databases and stored in the browser, which is dangerous. But on second thought, some systems will actually encrypt the password when it's stored in the database. The readable text will be encoded as a hash, a set of strings. So, I don't think this can be fetched for your hide/show purposes.
• J

  How can I better organize this table data, where rows are repeated since metrics have both a 'lights on' and 'lights off' value
  usability website design tables • • jules  

  2
  0
  Votes
  2
  Posts
  0
  Views

  G

  Does this work? This clears out the repeating info and gets those numbers together but I'm not sure if that's what you need. If users need these numbers, this a a good display. If users are looking at these numbers and then figuring out the range between them, or anything else like that, you should show them what they're trying to figure out. For example, if they're figuring out the ranges between these numbers, show them the ranges in a bar chart.
• R

  Designing with Night Shift
  color • • Raziyah00  

  2
  0
  Votes
  2
  Posts
  0
  Views

  

  When I am working on UX works (analysis/synthesis, mapping solutions, workflows, wireframing) I would like my device on a Night Shift mode, especially when I work at night. For work-related to UI (colors mixing, fonts etc), of course, the screen must be on a normal display.
• D

  What is best practice for sticky-navigation homepage logo; should it refresh the page or just scroll back to top?
  seo ux field response time • • Duquan  

  2
  0
  Votes
  2
  Posts
  0
  Views

  F

  The best practice for navigation links is to make them consistent across every page of your site. One way to achieve consistency is to make every primary-level navigation tab scroll back to the top of the page, if the user is already on it. Logos aren't always perceived as Home links, though - that's why https://www.nngroup.com/articles/homepage-links/ as part of your navigation. An advantage of smoothly scrolling back to the top of the page from a primary navigation tab is that you're affirming to the user that they are definitely already on that page. A reload might force them to take a moment to reorient themselves. So, my vote is for having the logo, and other tabs, scroll back to the top (but you should test that with real users). I can't think of any performance or SEO concerns out of allowing this. Page reloads seem worse for performance, and keeping the user on a page longer is better for SEO.
• 

  Should a tab selection persist after refresh?
  user expectation tabs refresh • • irl  

  2
  0
  Votes
  2
  Posts
  0
  Views

  D

  Yes, persist the tab. If a user is refreshing the page, most of the time it means something went wrong and they got stuck. It's a good practice to help them get back to what they were trying to do as quickly as possible.
• A

  Workflow between UI designer and UX conceptor
  design process concept • • Avante  

  2
  0
  Votes
  2
  Posts
  0
  Views

  J

  Over the past 20+ years, UX has swung from specialist roles to generalist, and back again, while some companies have held onto roles that worked for them. What you're describing sounds like information architect (IA) or UX architect work, which may be low fidelity but which drives a core part of design: how it works. I've worked at places where the IA/UX architect did flows and wires, and the UX designer/visual designer/interaction designer did interaction design, visual affordance, accessibility, branding styling, etc. Sometimes there are even more roles: editorial, content strategist, UX strategist (not an IA or wire "conceptor", but someone who creates principles and goals for design to work from and toward), taxonomist, etc. You can get a good idea of fundamental UX flow and activities from Jesse James Garrett's classic Elements of UX diagram: http://www.jjg.net/elements/pdf/elements.pdf . Everything goes from the bottom up. If the above is the case for you, then you and the "UX conceptor" should align on a workflow process. (You might also consider using something like Figma, which allows for things like an easy-to-use shared component library that might make changes easier in your work. Or, a living style guide if you work in code.) OTOH, I have worked in places where a PM or executive acted as a UX designer/architect, considering UX as a "common sense" job and themselves as the target audience. This can result in disrespect for the UX designer's work and repetitious, redundant work such as you describe. If that is the case, I would try to either work in a different department or find a new job.
• 

  How to ask the user to sign in or sign up (mobile app)
  mobile application • • jeanid  

  2
  0
  Votes
  2
  Posts
  0
  Views

  

  It’s a great realisation that you do not need to ask for sign in at the first screen! Seriously, enough colleagues in UI design simply do that unquestioned, because it seems like a best-practice. It is not, and rather frustrating for users, actually, leading to bounces. From https://developer.apple.com/design/human-interface-guidelines/ios/user-interaction/accounts/ : Ask people to create an account only if your app’s core functionality requires it; otherwise, let people enjoy your app without one. Delay sign-in for as long as possible. People often abandon apps when they’re forced to sign in before they can do anything useful. If Login is optional (which most of the time it is actually), it should never stand in the way of achieving a user’s goal. Most importantly, it should not be thrown in their face in a pop-up. But once they finished their task, and the app’s value became obvious, they are more open to additional engagement. The keyword here is https://www.lukew.com/ff/entry.asp?1130 . Twitter's recent sign-up redesign boosted new user conversion 29% by using gradual engagement. […] registration is either postponed, or handled behind the scenes and the first time experience is focused on giving people an understanding of how they can use a service and why they should care to. So confirmation pages might be a great place to motivate users to create their account. Great, you created your first event! Sign Up to synchronise events with your other devices. Your Sign Up option in the profile is a great idea as well, as users who actually plan to do so right away probably will find it there.
• D

  Repeat split button primary action?
  buttons • • derk  

  2
  0
  Votes
  2
  Posts
  0
  Views

  B

  https://www.nngroup.com/articles/split-buttons/ A split button has a default action. Clicking "Insert" above performs a general "insert", but clicking on the split part opens a menu of related actions. The Zoom menu below is on a split button - clicking Stop Video performs the default action, and the split menu has several video-related actions. A non-split button just opens the menu. It doesn't perform an action when you click on it. That's why you might see the label twice. When should you use a split button? From the https://www.nngroup.com/articles/split-buttons/ linked above: Split buttons are for presenting several related tools if one option is used most frequently. Making the most commonly accessed option a default lowers the interaction cost to use that option since it removes the need to open the menu before selecting the item.
• K

  Which guideline includes Accessibility when using Nielsen's Heuristics?
  accessibility heuristics • • Kadir  

  2
  0
  Votes
  2
  Posts
  0
  Views

  J

  I think the issue lies in the question. It assumes inclusion of accessibility in the heuristics, while you cannot treat accessibility as an isolated rule like the others. As we often say, accessibility is not a single person’s responsibility, neither can be handled as a phase or a last checkpoint. There was some work done to map WCAG rules to Nielsen’s heuristics, which shows the nature of their relation. Accessibility is not one of the rules, but there’s a big overlap of what’s necessary for accessibility and the heuristics. https://blog.myplanet.com/usability-and-accessibility-213c3185314f https://www.researchgate.net/publication/336472653_Mapping_WCAG_Guidelines_to_Nielsen%27s_Heuristics So personally I would say that Nielsen’s heuristics are necessary but not sufficient for accessibility.
• K

  Problem statement in design thinking
  design design thinking • • kalena  

  2
  0
  Votes
  2
  Posts
  0
  Views

  M

  If there is no overlap between the problems then the best way forward is to craft a solution for each problem one at a time. It is best to find a system that works for you in terms of finding a solution. My process is as follows: Define the problem Find why out the problem is occurring Craft a solution Test the solution Launch update For instance, I take one problem. In this case it is difficulty/frustration with booking an appointment. Then I set out to find out the cause of it. In this situation I run a round of usability testing and see that people have difficulty finding the "booking" button. Next, I create drafts for a few different solutions for the issue and do A/B testing to see which one works best. Finally, I run another round of usability testing to make sure the product is working. If it is, then I implement the change. Now, I can move on to the next problem. As you can see, since you already have a system, you know what your plan will be in terms of tackling each problem. So your next step is to pick the most serious one and start working on it. Hope this helps
• D

  Editor's autosave UX
  editor feedback autosave • • derk  

  2
  0
  Votes
  2
  Posts
  0
  Views

  C

  I think all you need is a quick, disappearing toast message (like you showed in your question) when the version is being saved, and optionally a "Last saved at [time]" message somewhere less prominent on the page. Not sure the user needs to know when autosave fails - they can't do anything about it, and it's disruptive enough to pull them away from the task they were concentrating on. If the app isn't autosaving frequently and the user risks losing data by leaving, make sure they can save upon surfing away from the app via a prompt.
• 

  Assumptions related to PainPoints?
  ux field best practice • • emmalee  

  2
  0
  Votes
  2
  Posts
  0
  Views

  Z

  Yes, those are all assumptions. In Steve Krug's book "Don't Make me Think" a big point he talks about is that people often have the wrong idea with what they think their users will like/dislike. It really isn't until you start to do research that you get an idea for what actually bothers them. One big point, is that we assume if it bothers us, then it must be an annoyance to everyone else as well, which is not always the case. It is only a pain point if you can show users dislike/have difficulty with it. If you can show that users have these difficulties with similar services it will make your points a lot more valid. If you don't have clients yet you can try to send out surveys or conduct interviews with people working with other companies or renting out their property alone. Find out what they think is frustrating about their process. Another alternative is to present it objectively, "People renting out a property have to keep a lot of paper work with them.","Homeowners renting out a property have to find potential tenants and schedule appointments on their own, which can be time-consuming." Then you can provide how your company offers solutions.
• O

  Hierarchical checkboxes interaction during search
  search checkboxes • • Oba22  

  2
  0
  Votes
  2
  Posts
  0
  Views

  

  I'm not sure I understand. As far as I understood, the checkboxes don't affect whether the tree search searches these nodes, but rather they affect some other filter (not part of your screenshot). So the tree search itself should be agnostic of the state of the checkboxes, and checking them shouldn't affect the search results within the tree. If they do affect whether the tree search applies to these nodes, it seems to me that this component has an unusual "circular" logic, leading to the problem you're in - and I would check whether the approach itself is justified.
• S

  How do I design a state machine?
  usability forms design patterns tabs • • simrah  

  2
  0
  Votes
  2
  Posts
  0
  Views

  N

  I'm a bit wondering why not use a simple dropdown, which will make an easy way to select one out of 5 steps Or use selection cards
• R

  Is "Assistance Order" acceptable terminology in the context of a furniture business app?
  terminology desktop application • • rosemadder  

  2
  0
  Votes
  2
  Posts
  0
  Views

  C

  "Assistance Order" is a bit of a vague term. I have not see any other companies using this term and I do not think people would understand what it means right away. You best bet is to use something that everyone is familiar with. If I ordered something on website and something went wrong I would immediately look for a button that says "report a problem", "request help", "is there a problem with your order", etc. Use something that is industry standard, that way people will recognize it immediately. Hope this helps
• C

  Confusion with Empathy Maps
  maps research • • Cleofas  

  2
  0
  Votes
  2
  Posts
  0
  Views

  Z

  With an interview, the best you can do is simply ask them what they would think/feel/do in a particular situation. For example, you can ask them what they would do in a particular situation. Then you can ask them what they would be thinking in that situation and how it would make them feel. I think the hardest differentiation would be between think/say using this approach. In a survey, you would have to take the same approach, asking opening ended situation based questions. You can attach images of a page to the survey and ask them what they think this page is for, what they would do on the page, how it makes them feel, etc. Ideally, you would be able to give them a usability task which you can view. If you're doing this remotely then attach a survey afterwards asking them what their thoughts and feelings were during specific tasks.
• 

  Filtering and Sorting a Table that has more than 1 row per user
  filter tables design patterns data tables sort • • Demir  

  2
  0
  Votes
  2
  Posts
  0
  Views

  C

  I think the problems you raise in your questions are not really problems of ordering or classifying data within a table, but that you are seeing the issue only in two dimensions as a double-entry table when in reality interactivity allows you to use more than one x/y reading. The duplicates problem in a table is not something new, there are font management applications that allow performing a search for duplicates, offering the result in a visible way. Or spreadsheet applications with duplicate rows... First of all, I would highlight the repeated data with color, text indenting, semi-transparency... Secondly, I would use the interactivity as a top layer, allowing the user to decide if they want to see the duplicate information: Alerting there are duplicate data. With an icon/button next to the most relevant item I think is enough Showing duplicated data by clicking on the icon Showing the matched items when hovering one of them
• 

  Full-width H1 vs "normal" size
  website design web design • • inna  

  2
  0
  Votes
  2
  Posts
  0
  Views

  Z

  Normally it is not a good practice to have large, lengthy h1 tags. Looking around your site, however, I think what the designer has done is appropriate. The h1 headers are one or two words, not lengthy lines that can cause users to https://baymard.com/blog/line-length-readability . The rest of the pages don't seem to have a large amount of content that the user urgently needs to get to. The titles are elements of the visual design, as one would see in a traditional magazine ad. The markup structure appears correct and I don't see any UX issues with the headings. I do think your menu items are problematically large, and would bump those down a bit - I had to scroll to get through a not-very-long list of items, and that felt unnecessary.
• O

  Daily maintenance tasks vs. set-and-forget
  navigation information architecture • • Oba22  

  2
  0
  Votes
  2
  Posts
  0
  Views

  

  As always, user testing will be your best friend here. Keeping all admin tasks under a single tab seems to make sense from a logical standpoint. "Maintenance" sounds very nonstandard, so I suspect most won't have any familiarity with it—it's certainly not intuitive to me what I would find there. It's difficult to give advice without seeing the full picture, but it's generally best to have admin actions contextual with role-based gates. e.g. if there's a Users page, the "Add user" button should be on top of the table only visible to admins. Assuming that's not the case here, I would probably make your label a little more specific to what you're editing, not who you are, so I'd go with something like "Account Settings". (or swap out "Account" with whatever you're editing)
• D

  Filtering and Sorting a Table that has multiple rows per User row
  filter tables data tables sort • • Duquan  

  2
  0
  Votes
  2
  Posts
  0
  Views

  A

  Firstly, I would change the colours column to fit colors vertical not horizontally. This would allow , for your example : "BUT what if.. you wanted to then SORT the Red & Blue filtered results by Amount?:" to also change the order in table and the order in the colours column.