5
edits
mNo edit summary |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 70: | Line 70: | ||
===What did you change following your user tests?=== | ===What did you change following your user tests?=== | ||
{your text here...} | {your text here...} | ||
==Mentor Comments== | |||
===James Kalbach=== | |||
* Good summary of your research. It really helps to see into what you did upfront. The interviews seem a little short, though. Also, you might have done better to have given people a real life scenario and observed them as they interacted with a website they wanted to recall later. | |||
* I like the fact that you have alternative sketches. A little more detail would have helped to get a better sense of your idea. It still seems quite high level at the moment. | |||
* Are tag clouds an efficient way to re-find information? They seem more like a trend that's now outdated than something really useful. I'd consider other ways to organize your tags, perhaps in addition to the cloud. | |||
* Have a look at Zemanta--a tool for automatic tagging. | |||
* Also check out Facetag (http://www.facetag.org/), a way to browse tags by different facets. | |||
* In the business world, the ability to communicate your design ideas is as important as having them. Managers and stakeholders may have different priorities with a given project or initiative, and you will have to persuade them to see your point of view. Unfortunately, you didn't complete the template for your project so we can't see how well you put your thoughts in writing. | |||
Overall, you've done good research and have come to meaningful conclusions at the beginning. It's a shame you didn't follow through with more detailed designs and a complete description of your project. | |||
===Cennydd Bowles=== | |||
Your understanding of the problem and the principles behind your design are good. Given the cognitive burden bookmarks currently place on users, it makes a lot of sense to push this complexity to the browser instead and give users as little work to do as possible. However, generally there isn't enough detail here, particularly around information architecture. How will the browser generate the tags? Are there certain words it would have to eliminate? | |||
Your sketches look reasonable although again it would be useful to have more detail around the interactions. How does the search work? Is there a type-ahead to help guide people toward tags the system holds (since they didn't choose the tags themselves). What happens for international users who spell words differently (eg UK "colour" vs US "color")? Also, think of unintended behaviour. Is it likely that users would look for ways to get around the fact they can't add their own tags? | |||
===Eric Reiss=== | |||
You've really nailed half of the problem behind bookmarking: organizing the information. The other half is that bookmarks go out of date - although that is beside the point with respect to this project. You've also understood that even with the best tool, compliance is an issue - most people are too lazy to fill in the metadata needed to organize and re-find the information they've saved. | |||
Cennydd pegged some of the major problems with tagging. In fact, over the past couple of years, most experts agree that tagging just doesn't work very well in a multi-contributor environment. On a personal blog, where the writer always uses the same words and spell the same way, tagging can be moderately successful. But elsewhere it is often problematical. See Gene Smith's book on tagging for a very good review of the possibilities and problems. | |||
The details of your proposal are confusing at best. I can see where you're going from the sketches, but not the details. As Mies van der Rohe said, "God is in the details". I need to get a little religion here :) | |||
This questionnaire is still not fully populated, which is a shame. Perhaps I would have had fewer questions if it had been completed as we mentors had intended... |
edits