51

Worked on a project with this exact problem. We needed a way for the admin staff to add attribute to products. Because attributes are used for search purposes, we need to ensure if that attribute type already exists, it should be selected instead of creating a brand new one. We ended up using something akin to your first idea. download bmml source – ...


49

The concept is fine, but "Finish" is ambiguous as a label. It's better to more specific about what will happen if you press the button, for example "Save and exit".


40

In my opinion it would be better to distinguish between creating and editing the business object. For creation a wizard is fine. Besides the next button it could also have a finish button if the current and all following wizard pages only had optional information as input. For editing an existing object a tabbed dialog could be a good choice, since allows ...


32

Well, I guess there is a maximum number of miles someone can travel in a year, since there are a finite number of seconds in year, and one cannot exceed the speed of light. A more practical limit may be 1000 miles every three days, which would be about 100,000 miles in a year. I suggest using a normal slider but with a logarithmic scale. i.e. equal spaced ...


32

I've always been enamored at the way the iOS quicktime application works when viewing MP3s in Safari, and I think this method can be adapted for your use. We can stay with a normal slider bar - perhaps the handle could be changed from the normal circle to show a difference. We can add tick marks to the bar and numbers that change on either end. Then, ...


28

The first idea failed field testing and variants failed usability testing It sounds like we had the same idea as your option 1, and we implemented it. We were looking for a way to force users to search first without users realizing that we were forcing the search to occur. A variant of our first design actually tested OK with a small sample in usability-...


22

One interesting solution that hasn't been proposed yet is a sort of "odometer" that the users could set to the desired number. This would have the benefits of preventing users from having to scroll through smaller numbers to get to larger ones, allowing users to be as precise as they wish, and being as simple as plain text entry without messing with a ...


21

My answer shows simularities with others posted here but I want to emphasize how important the right communication is. For example: Reconsider the used language to make the intentions clear. For example use create company to add some weight to the action or use the word new to emphasize the difference. download bmml source – Wireframes created with ...


19

Keep the Finish button There is nothing wrong with the Finish button because it provides an exit shortcut for users who want to save and finish the process early. Otherwise, users who want to edit just the first page of the wizard, should click 4 times next until they can save and close the form. That's 4 unnecessary clicks. Add a Stepper progress bar The ...


13

Problem I think there are several usability problems in current design. Wide single line input limits the way that note could be expressed (no paragraphs, no breaks) and makes the reading much harder. Interaction style is non-convenient, as note-taking area is disjoined from appropriate order. This creates jump-and-search behavior while taking a note, ...


9

Reading @Henrik Ekblom's comment about circular controls reminded me of how the Timer app works on Android phones (image below is from the Timely app). You can add as many minutes/hours to the timer as needed by continuing to drag the cursor in a circle around the clock. Obviously the circular format works a lot better for clock-like functions, and it could ...


9

It is definitely a good idea. I have used this approach - at a particular point in our wizard, the wizard has captured the important stuff it needed, so we allowed our users to finish the wizard early if they wanted too. I had to make sure the appearance of the Finish button was really obvious - some early usability testing showed some people didn't see ...


8

Hear those crickets? That’s the sound of no guidelines for dense data presentations for any design language. There has been a need for such guidelines since GUIs first arrived, but there aren’t any I know of. For what it’s worth, I’ve been developing my own approach for dense alpha-numeric GUI presentations over the years, which I described at Coded, ...


8

I suggest you replace the slider with a dial by removing the thumb indicator and adding arrowheads on either side so it looks something like this: I use a program at work that uses a similar dial to control frequency during an online simulation, and I've never seen anyone get confused with it. Here's the interface:


8

User experience is different from data design Developers who move into UX often forget this important perspective change. Users don't think in terms of CRUD. They usually think in terms of what they want to get done. Some examples: For a micro blog, an author might want to create, update, and delete posts from the same convenient interface. For a large news ...


8

If there's some usage statistics available for your users, something like the 80/20 rule or Pareto Principle is a general indicator of where you should be focusing your efforts. It is a more objective way to show the stakeholders that perhaps only 80% of the users (or whatever the figure might be) ever view or edit 20% of the fields, and therefore spending ...


8

Separate the User Lookup Task from the Add Task In other words: Remove the "Did You Mean?" section. In the provided example, it's easy for a user to get distracted and wander off from the key task of adding a new user. Example: "I need to see if Thomas Jones is already in the system. Oh, there are two people called Thomas Jones... I wonder if ...


7

Not commenting on the usability of this design pattern. The New Relic sign-up form uses this pattern. Example: Country drop-down/search field.


6

It seems like your users need something that first selects a less detailed milage area, with big steps. When that area is selected it's time to fine tune. One way of doing that could be something like my image below shows. As soon as the user clicks and drags in the span control (A), the red marker follows and a more fine tuned area (B) shows up. The user ...


6

There are too many decisions to make at the same time on this. You should use JavaScript to progressively invalidate later choices, but maybe not in the way you were thinking. In a case like this, I would try to break it into steps and auto generate a much narrower form from the first choice. You can remove any illegal combination when you display the new ...


6

You normally design form fields to match the expected input. Do you have a maximum character count for this field? If so, you can display a countdown, decrementing that number as the user types, to provide them with real-time guidance on how wordy they are allowed to be, and also to circumvent the awkward flow of accepting their typing and then erroring out ...


6

Swift/BIC codes follow this convention: AAAA BB CC DDD AAAA Bank code A-Z 4 letter code. It usually looks like a shortened version of that bank's name. BB Country code A-Z 2 letter code. It says which country that bank is in. CC Location code 0-9 A-Z 2 digit location code that could be either 2 letters or numbers. It says where that bank's head office is....


5

You could use your described system (hiding every entered character after input) but still showing every special symbol as in dots, slashes, underscores etc. giving the user the opportunity to check the length before and after those characters. Further I think it would be ok to show the TLD. Additionally - since you are using a touch screen - you could let ...


5

It sounds like your customer is, like everyone else I know in finance, very much hooked on Excel. It might seem horribly cluttered to you, but this person is likely used to working with giant workbooks containing lots of sheets (accessed by tabs). They rarely want to learn a new workflow, so don't break your head trying to force other solutions on them. ...


5

I like your general idea, but it seems that your users are not getting the metaphor. Which leaves you with two options: Make it very skueoumorphic, hoping that they will get the hint. Instead of using a slider, use something which looks like a physical lever that can be pushed more or less to the left (or right), and beside it a spinning number display ...


5

Good question, but the Wolfram reference is terribly incorrect. The use of the period . in user interfaces is almost universal nowadays, and I would advise against trying to overload the comma. The spread of the decimal point is a pretty interesting case on the effects of globalization and technology. In this case, the broad standardization of global ...


5

I would describe this situation as: dynamic nested workflows. Dynamic because you cannot tell ahead of time how deeply nested the workflow will be (user may not create any new objects, or may create multiple carriers and persons). Nested because the workflows for creating a carrier and then a person are nested within each other. The dynamic nesting makes ...


5

What about something like this? Basically a double range slider where the user sets the boundary between the OK and Warning, and Warning and Critical alerts. The "normal" value is highlighted (popped out) of the usual number range. The user could either drag the little boundary markers or you could make the labels (currently 19, 45, 85, 108) an input field ...


5

The primary benefit to a wizard, rather than displaying all the input fields at once, or in categorized tabs, or some other UI element, is that it organizes steps that must be taken in a specific order. An additional benefit is that the Next step may be different, depending on the input performed in the Current step. Allowing the user to Finish early ...


5

This is indeed a matter of phrasing. What you need to know is biological sex, not gender. Gender is personal, a sort of sense of self. Biological sex is what others have assigned you when you were born as a method of classification. Since this would be for medical purposes, use biological sex. Gender at birth would be confusing to some, as there are people ...


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