Hot answers tagged

15

For starters I recommend looking at this excellent article from UX Matters which talks about how to extend Jesse James Garret’s visual vocabulary to reflect rich interactive applications which recommends highlighting the interactions as synchronous (requiring a page load)and asynchronous (happening within the page). To quote the article For user ...


9

This is a good question. I've been wandering if there is a better way to document interactions for over a year now and have been trialling a few different things. I've taken inspiration from a lot of different places and below are the different types of methods I've created/trialled in the past with some success. The images below show interaction with an ...


9

Organizations are so hung up on deliverables that it turns a proper UX process into a deliverable process instead. Which is bad UX. The ideal is to educate the organization that UX isn't a step in the process with a set of defined deliverables, but rather it is part of the process itself, and the deliverables will change from project to project and even ...


8

I vote no for UX and yes for SEO (with a caveat). If your site requires a sitemap for a user to find their way around, then that's a smell that you have a poor information architecture. I don't buy the argument that they support users who know what they are looking for - like an index in a book. A website and book are sufficiently different that the ...


7

Jesse James Garrett's Visual Vocabulary for IA has the concept of a "conditional area", represented by a dotted line grouping the elements. http://www.jjg.net/ia/visvocab/#conarea The example he gives is the following: In your example, you'd have the condition based on their role and throw some sort of error when the user tries to access a page outside of ...


6

1ST ANSWER: I normally don't really care about the terminology used to describe the assets that are created using a UCD process, but I do care about the quality and accuracy of the information it captures. So to me I think your description of the two types of information captured is pretty close to the mark, but I couldn't tell you if that's the exact ...


5

It's worthwhile creating a sitemap that's part of the IA documentation. You'll find that a microsite is always a few pages bigger than expected. This includes Terms & Conditions, Privacy Policy, Response pages and Landing Pages if part of a campaign. It's also a useful negotiating tool if client has signed off on a project and wants to add more content. ...


5

I'd have to point you to this BBC Internet Blog post for an excellent reference. This blog post describes the technology strategy the BBC Future Media department is using to evolve from a relational content model and static publishing framework towards a fully dynamic semantic publishing (DSP) architecture. You will need to define and describe a set of ...


4

To my observation most popular eCommerce sites skip site map because of lot of interlinking between the pages. check Amazon, http://www.oliveandmyrtle.com/, http://www.quikr.com/, http://www.20north.com/, Rather they focus more on product classification and grouping, which make the user to understand where they are and what they want. Also they make their ...


4

I'd (rather laboriously) go through the site page-by-page and log it all down in a spreadsheet, such as the example I've attached: Give each page a reference number based on the hierarchy in the site, list the usual details (title, URL) and a brief summary of the content. I've also started listing out all the features found on the page (text, imagery, flash ...


4

A flowchart is a flowchart regardless of which device it is viewed on.


4

Sitemaps are a simple visualization of the pages that the website will consist of. I use sitemaps when developing a website for a client so we can agree on the pages and their content. It's as simple as a square with a word and maybe a small description. Like 'frontpage' with the description 'small introduction'. It's a simple visualization for the client ...


4

Yes Yes is the answer to your question. Why would you invent additional levels? Sitemap - the term The term sitemap is ambiguous, it may denote: The hierarchical navigation taxonomy A group of links at the bottom of a page providing the most relevant links to other parts of the site Like at the bottom of this page With an on-going argument regarding ...


3

What do you want the sitemap for? For your own piece of mind, so a user can look at it and decide where to go? The latter will happen in your taxonomy, which is why getting the taxonomy right in eCommerce is so important. Any eCommerce sitemap is going to be category and product listing specific.


3

Site maps are still useful in the same way that an index is still useful in a book that has a table of contents. It provides a different way of organizing information. A great website will naturally lead the users to where they want to go normally, particularly if they don't know exactly what they are looking for, but a site map is invaluable for quickly ...


3

If your home page (or first landing page) is not intuitive enough, then a sitemap will be useful for not-so-tech-savy users. Also, sitemaps always help in making your site more accessible to search engines no matter how much SEO has moved on.


3

I think this could be handled by providing simple affordance. If it looks like a generic link, it will be a link. If it looks like a button, it will be a button. If you want to increase the affordance in your Mega Menu, you may want to consider: A down-pointing arrow next to each horizontal menu item or a right-pointing arrow next to a vertical menu item ...


3

A list of all pages and their hierarchy is often referred to as an organization structure.


3

Typically the reason you're showing all the screens is to illustrate how they navigate from one to the other. It's not uncommon to see "navigation overview" or "application flow" used to describe this type of diagram.


2

It depends on the project, but I tend to merge the user flow with whatever stage of design I'm at. For example, if I'm getting down the use cases, I put those into a flow. If I'm figuring out the sequence of screens, I use those to depict flow. If I'm in wireframing, I assemble the wireframes into a flow. This approach usually requires me to escort the team ...


2

Flowcharts are the most common tool for visually representing site structure, as far as I know. Here are a couple of examples:


2

I would think no, not always needed. Particulars broken down by audience: For the sake of the page builders, content creators: no, not needed for 5 pages. You would likely just list these out in other documentation (or be creating the pages yourself). For the sake of the end users: no, it just becomes an extra link with little value, and is possibly ...


2

If you mean publishing a sitemap page for the users to use it, IMO it's only needed when the navigation is not clear enough.


2

A simple icon, such as a keyhole lock, that can show the page is locked (and therefore unlockable with the correct key), is a good way of identifying which pages are behind the login or firewall. Using a dotted line pointing away from the lock to an error page/box, along with other lines that connect the page to represent typical navigation, should be make ...


2

Create the full map first, then edit it with the user in mind. I've done this before for large-scale e-commerce sites. A typical first edit might be an inclusionary edit--mark off what you definitely want to include, like product categories, as others have said. Look at your processes, such as your shopping cart, and try to view them from a user's ...


2

This is an "it depends" answer, and I apologize for that. But I think the question can only be answered if we knew the goal of the SEO activities. If the main goal is to draw attention (that is visitors PPC) then yes. You would want to get attention from using the right keywords and get (ultimately) a lot of hits. But ... … if you want to sell anything and ...


2

I would speak to your Project Manager and explain that the sitemap is a living document as stated above by DA01. Site maps change constantly and never sit still, even during the development stage the site map can change, UX is about testing and refining so quite how they expect you to product a sitemap before hand is baffling. A PM is all about ...


2

It's a reality of the Internet that the sitemap for any given site is never "fully worked out"; websites need to be designed from the get-go to be scalable and to adapt to change, especially since most sites nowadays are driven by a CMS that allows people to add new articles and even pages as necessary. For me the information architecture (IA) is designed ...


2

Every design decision should be justified by either empirical or logical means (which are ideally based on previous research and empirical testing) . Surely if you think your design is better, you have a way of arguing it? As far as site maps are concerned, analytics is an invaluable resource for their design. User testing is the next thing to do to affirm ...


2

Been thinking about this for an hour; have to admit "architectural blueprint" had me stumped. Do you actually mean a wireframe? I think you are looking for the following document definitions: Sitemap - Site architecture in a hierarchy, with clear categorization of pages. It's where the pages "live" in the organization, but not necessarily the order users ...


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