Tag Info

Hot answers tagged

33

I'd say the best two options are: 1) Display terms and conditions as long plain legalese text as usual, in a left hand column, but then summarise it in much shorter, friendlier, simpler text on the right. 500px.com does this really well: 2) Format the text in a legible manner. Separate it into linked sections with proper headings, good typography and ...


20

Conventions and the conscious breaking of The vast majority of people don't have their mouse buttons swapped. Even people who use the mouse with their left hand, often keep the buttons as they would normally be (myself is an example for this). Thus, people who swap these buttons can be considered in UX as complementary personas (people with special ...


20

There are a number of other ways you can look at as well The walk-through approach : The walk-through approach walks your users through the app like how Google does it. Its also called the joyriding approach. To quote this article The “joyriding” approach walks the user through the features of an app or highlights the key features. It’s great ...


17

Oh, wow. You might call this an example of the “metaphor anti-pattern,” where they re-create a physical something in digital form and thereby replicate all its weaknesses; plus, since you can’t truly replicate everything you introduce new weaknesses. In this case for example, users can’t fan through multiple pages to skim to what they want. The result is ...


16

While Fat, Cholesterol and Sodium have attained a social stigma and are regarded as "bad", they're not technically bad for you; for the most part you'll die if you don't intake all of those things. If the labels actually attempted to pass judgement on which items are bad and good, people might actually attempt to get near 0% of the "bad" items and in excess ...


12

I would definitly recomend Steve Krugs book "Rocket surgery made easy". Just like his first book, "Don't make me think!", it's a pleasure to read and you'll get some new views on things. This might be the closest approach to agile usability engineering. He suggests that you schedule regular usability tests (once a month at first) and involve developers and ...


11

I know there's an accepted answer, and I usually do quite agree with Michael, but still this does bug my mind for two days. As a developer, I hated the Apple HIG It just didn't tell me what to do, how to do things in practice. The Windows Guideline was felt as "empty", but it could be that it did because it seemed, on Windows, actually noone follows them. ...


10

It seems like the work environment isn't that interesting for you, and I would suggest finding a start up or a small company to work for. But that doesn't seem to be the question. So here are some ideas to spice it up a little: Design your documents. Add some color, lay it out on a grid to give good example images. Take a look at skype's brand book for ...


9

Terms and Conditions, Privacy Policy, and similar documents are there primarily for legal reasons, not UX ones. So the reason that they are usually terrible to read is that they are written in legaleses rather than human speak. A good alternative is to add additional explanations in human speak next to the legalese. StackExchange is a good example to ...


8

It does, in the sense that it's important for the document to be clear, structured and readable. The principles of good technical writing are eventually aimed at providing good UX for the reader (short paragraphs, a funnel structure, coherent navigation within the document etc). The same goes for spreadsheets - if your user/reader can't find his way around ...


8

Flickr advanced search allows to restrict the sarch according to Creative Commons criteria (e.g., usable for commercial purposes). Due to the diversity of people using flickr you can find many different kinds of pictures using the search term 'portrait' for example: http://www.flickr.com/search/?q=portrait&l=commderiv&ct=0&mt=all&adv=1


8

This would probably be called UI Style Guide or UI Guidelines but there is no 'correct' name. Apple calls theirs 'iOS Human Interface Guidelines', Microsoft calls theirs 'Windows User Experience Interaction Guidelines'. Both covers pretty much everything that needs to go into a document like this. More examples are: ...


7

As others said, you should look into generating HTML files that you ship with your product for help. One of our products (used in an environment without internet access) has been doing this for years and many users prefer it to the PDFs we also ship because the navigation is easier, the content lays itself out to fit the browser window, and the chunk size ...


6

People don't read. The best help is no help. Of course to do that, you need to put a ton of time and work into the UX. So, assuming you do need help, I'd suggest the best would be context sensitive help that can link to your web site with the latest up-to-date help information. You'd publish help as HTML, saving you from proprietary CHM production ...


6

I would consider revealing the help gradually: If you set a standard where each field has a tooltip, you can avoid any special icon - the user will immediately know mouse over will result in a tooltip. Each tooltip should have a link in it (or alternatively the whole tooltip is press-able) to expand it for a more in depth explanation. This explanation can ...


6

Example Style Guides For example style guides applicable to applications, you can leaf through with the usual platform style guides (e.g., Windows, Apple, Gnome) for the organization, issues, and topics you may want to have. Many topics in these guides are not relevant to form-oriented UIs, but most of the guidelines for controls, messages, and dialog boxes ...


6

I don't have references to hand, and Google is failing me, but my (very fallible) recollection is that: bold text inline decreases reading speed / legibility bold text increases "scannability" when searching since folk can easily find the bolded text There are, of course, other options to highlight key points that will help readers find the important ...


6

To be frank, only a selected few are aware that the Enter and Return keys are not the same - whether you refer to it as Enter or Return, users will press either buttons (if they have both buttons). This is due to the fact that very few software products where the Enter and Return keys do different things (Avid's Pro Tools is the only example I can give). My ...


6

"Enter key" is a more popular choice than "Return key". According to Google ngrams. I'd therefore write "Press Enter" unless I could be certain that the users have a specific keyboard with a specific label on the key want them to use.


5

I find the Twitter signup page to do a pretty good job at this: They even use this for validation / feedback: It does require a few hundred pixels next to your input field, though. It does, however, leave you the freedom to just provide a short help text followed by a "more..." link.


5

First you design the system as if there will be no training. You have to consciously try to imagine that training will not be an option and make the system as usable as possible. This is no trivial thing, as some aspects may need training, no matter how good the UX is. Once you have done that, you then design the training. This way you should be able to ...


4

Make your big UX documents smaller by using cartoons. I'm serious. Usability test report/analysis - Show a map of the key routes through the site, with 'Users get stuck here'. Competitive analysis - Sketch key features of competitors, sized by relative importance. Interface requirements - Draw a cartoon with the different types of users/stakeholders, ...


4

As analogy, I just interviewed someone who had a 7 page resume. No page x of y at the bottom. The text was dry and boring. If I dropped the stack, Id have a rough time figuring out the order. It was hard to scan. It made me annoyed to prepare for the interview. In this case, I am the user and he is designng my UX. He is the application. Every person ...


4

OK, I must disclose upfront that this guy is a friend of mine, but this month he's launching a website that's supposed to make the whole process of working with personas easier. One of the features is just what you asked about - access to a very large set of portrait photos taken around the world, explicitly for this purpose (with agreement signed by the ...


4

We kind of follow this structure ( I admit its an adaptation of the process of documenting reusable components in software design) Pattern Name and Classification - A short, meaningful name for the pattern, The names are chosen with regards to the use and application of the pattern and the combination of predefined terms. For example,if the design pattern ...


4

I would guess that anyone actually working in UX would not have the time to do a full transcript for each interview. I typically get permission to record the interview with my phone and make a few short notes from time to time as i go. I will listen to the full recording later in case I missed something important. I find a simple spreadsheet document with ...


4

Here is a rough guideline of the document layout I would follow for such a document Problem statement : An explanation of the problem and the issues faced by the current company User research\audience research : An explanation of user base of the site and how they influence the problem statement Stakeholder analysis - A matrix which calls out the various ...


4

I have no legal training regarding terms and privacy policies, but I think one really good way to start moving web services towards resolving this problem is to approach privacy/terms/conditions in much the same way we've approached software licenses and general intellectual property licensing via common-use licenses like MIT, BSD, Creative-Commons, etc. ...


4

Now If you are working on a managed project, there should be Design Requirements, which should give you a foundation to build from. During development there is much in transition, but approved design documents can assist in creating help info. The final stages of system testing and user acceptance testing, should give you the chance to fine tune your ...


4

Is it reasonable to update the technical specification every time changes are made during the development of the project? Short answer: Yes, it's worth the time to update the specs. More context: Technical specification ≠ documentation, but often there is no documentation at all. So if changes are made during the course of long project there is ...



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