Tag Info

Hot answers tagged

9

Short Answer: They never intersect, as described, at a single "hail mary" point. They are different elements of the same process and should coexist together as part of that process. In the cases where one may be dependent on the other, the most ideal situation is that Information Architecture would guide the Software Architecture. Long Answer: When you ...


3

There's a trend towards using CSS and/or Javascript to show and hide secondary or additional content on the Web. Here's an older example from CSSNewbie: Click 'See more' to view hidden content: Click 'Hide more' to hide revealed content: I'll leave it up to you to determine which approach is 'best'. This approach—designing 'More Info' as a hidden div ...


3

Navigating as a side effect of some other action is not a good idea, I feel. Similar to pushing the user around... Why not show an empty Topic page where some stuff looks like it will look after approval, such as title and creator link (if any), while the content area (where posts will appear after approval) shows a message saying "Topic is waiting for ...


3

I would call it a "Drawer" (such as the app drawer on Android), but there are many possible terms for this kind of thing (tray, slide-up overlay, popup, etc.).


3

As per this article I found,the amount of time spent in searching for information has grown by 13% since 2002. To quote the article A recent IHS Knowledge Collections Webinar provided an interesting statistic by Outsell: an engineer’s time spent searching for information has increased 13% since 2002. A new survey by SearchYourCloud revealed ...


2

Market research people talk about customer/market segmentation analysis, which involves some of these types of segmentation (there are probably more): Geographical: based on the physical location/region of the customer Demographic: based on age, gender, racial, etc Behavioural: types of consumer behaviour (but we can convert this to user mental models) ...


2

Fuzzy logic No system is perfect; you're cataloging things based on layers of interpretation. I'm in the midst of defining such a process for a new team now. Every time I do this, I find myself reconsidering the format. But it gets the job done. Here's where I am at the moment. The specifics will change based on the application, but the fundamentals are ...


2

I would not show pricing for non-commercial customers on the page. Reasons: Those prices will be irrelevant to the vast majority of users. So it will just add unnecessary clutter and choice. The paradox of choice shows that having more choices actually makes it more difficult for users to buy, and you want to reduce, not increase purchase friction. Then ...


2

It helps that you stated your design intent clearly: it's about communicating volume/diversity of the changelog rather than the details. Some modern approaches to spicing up long, sectionalized content (use desktop browser to view the examples): Sticky section headers Parallax and scroll-updating navbars (scroll down to see effect) Timeline layout ...


2

The problem with having a piece of information next to each field is that in many cases it is not necessary i.e. it is repeated or obvious information. You will end up being obliged to fill it in for everything, even when you don't want to. It's fine in the two examples you have, but as an often used design pattern, you may soon wish you hadn't committed to ...


2

While (as @inkmarble mentioned) clicking may be more effort compared to a mouse-over we now also have to keep in mind the growing amount of users on touch-only devices. With the current state of the art, there simply is no way to mouse-over an icon on a touch device, thus making this help information inaccessible to this user group. Example: I recently got ...


2

It is ok to display a generic image of the product in the category page or as a primary picture. Even amazon does this. Only after the user goes into the details page will he/she get to know the available color choices and other options. As you already have a picture of the available product, it is ok to display it in the details page. This flow will work ...


1

There seems to be plenty of research around this particular topic, and not surprisingly it has been covered in a number of different psychology and marketing research papers (just google "optimal number of choices in a Likert scale"). Unfortunately, it is not easy to decide on what is the optimal number of choices because there are a number of different ...


1

I'm assuming this are items for sale, so, what does it mean a lot? You want to make a sale, and you should not save efforts in doing so. Plus, any info that helps you close the sale is always useful. Plus, based in your description, I think you don't have a lot of info, but you have some "noise". First of all: assuming these are items for sale as mentioned ...


1

As you said, since the user made a conscious decision to add the product in the wishlist, an image card can be a good thing to be shown as the main object, then try to the title of the product on that, but it is not that important, so if the text is tool long use "..." to just fit that in one line on top of the image card. For the last 3 items ("Good Deal" ...


1

Feedback If your entity creation process has "serious" implications for your users, and especially if it may involve them taking actions outside your app (booking a ticket somewhere, buying something and retrieving a tracking number), you may want to print a summary page where they get key information about how you identify the entity they've created and ...


1

The simple and nearly 'objective' answer is: Yes. Here's a example that proves the rule (reductio ad absurdum): an entire non-zoomable wiki page on a mobile screen. With that out of the way, maybe a more helpful answer starts by rephrasing your question to: Can one display too much information relative to the user's needs? As with most things ...


1

I think the answer is pretty obvious, but let's address a general problem. I will refer to Edward Tufte and Leonardo da Vinci Simplicity is the ultimate form of sophistication. Leonardo da Vinci (source) Principles of Visual Data Presentation The principles of effective information design are as old as classical rhetoric. Indeed, in the ...


1

It seems as a good solution. The result will depend a lot on visual and micro-copy you'll use. Maybe combination with an icon indicating there's some more information hidden would be nice to discover the hidden content if it fits the rest of your UI. Or a tutorial that tells the user about it when working with the UI for the first time. Just keep in mind ...


1

Have you tried using colors? if colors are not an options, then different shades of grey with different variations of weights should help. remember, just because one column is important that does not mean other columns do no needs any effects(like less important columns could be made thinner or with different shades grey to reduce importance) My suggestion, ...


1

I wasn't able to find anything specifically addressing this in the UI guidelines from Apple or Microsoft, but Chrome uses a similar method of conveying information in the Omnibox. It uses the globe to indicate a website and a magnifying glass to indicate a search. Chrome also uses color to distinguish the different types of selection, which may be ...


1

What I have done for cultivating a user research 'database' is actually several things: Personas User needs roadmapping - mapping all the themes I am hearing for new features along a timeline, with cross references to specific customers User maps - I take specific goals that customers are trying to achieve and segment maybe our top customers against that ...


1

Building up a database like this sounds pretty cool, and potentially very useful. The difficulty lies in understanding what the data will be used for. One way to start scoping this out would be to make a list of the top 20 questions you have about users at the beginning of any project. This will provide you a path to defining a clear list of dimensions and ...


1

Could you use an initial prompt when you choose to create the document, and split that dialog in two sections - those that are available in this location and those that aren't? But still give them feedback / info about how they can create the documents they want. Something like this perhaps? download bmml source – Wireframes created with ...


1

A user should be able to create a document anywhere in your system. Declaring its type is totally fine, as is it auto-filing the document. Assuming that to be true, after the user picks the type and saves the document, show a temporary notification in the UI acknowledging the system saved the document with a link to where it filed location. Another thing ...


1

Officially, no, you can request what you want, when you want it. However, if you adopt the idea that you can request contact information up front, you'll likely get a lot more false information. People don't want to enter their data unless they want to be contacted. If they haven't yet taken your survey, they don't yet know if they want you to contact ...


1

In "Design with the mind in mind", author Jeff Johnson dedicates chapter 14 ("We have time requirements") to the "durations of perceptual and cognitive processes, and based on those, provides real-time deadlines that interactive systems must meet to synchronize well with human users" in order to be effective and perceived as responsive. In the chapter you ...


1

One solution is to provide two modes to build flexible system: Scan mode auto-scans the subset of most important params (gray-filled) with delay of 1s. Manual mode is activated with additional key. Then displayed params are switched manually, by each key press. If no action is performed for 4s, then device automatically switches to Scan mode again. ...


1

You need to look further into ways you can group & condense the data. For example, some like "total experience" don't really need a title if it's placed beneath the different years of experience. Below's an example. I might have mangled the past experience section by pulling out the current(?) position. It felt strange when there's no name associated to ...


1

I know this was answered a long time ago, but FTR it's wrong to remove price ranges from sites that sell services. There's a huge body of UX and usability / market research around this issue; for example, see one of the Nielsen-Norman group's articles: http://www.nngroup.com/articles/show-price/ Companies rationalize reasons for not revealing prices ...



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