archive.Joe Lamantia.com

Lets build on the analysis of tag clouds from Tag Clouds Evolve: Understanding Tag Clouds, and look ahead at what the near future may hold for second generation tag clouds (perhaps over the next 12 to 18 months). As you read these predictions for structural and usage changes, keep two conclusions from the previous post in mind: first, adequate context is critical to sustaining the chain of understanding necessary for successful tag clouds; second, one of the most valuable aspects of tag clouds is as visualizations of semantic fields.

Based on this understanding, expect to see two broad trends second in generation tag clouds.
In the first instance, tag clouds will continue to become recognizable and comprehensible to a greater share of users as they move down the novelty curve from nouveau to known. In step with this growing awareness and familiarity, tag cloud usage will become:
1. More frequent
2. More common
3. More specialized
4. More sophisticated

In the second instance, tag cloud structures and interactions will become more complex. Expect to see:
1. More support for cloud consumers to meet their needs for context
2. Refined presentation of the semantic fields underlying clouds
3. Attached controls or features and functionality that allow cloud consumers to directly change the context, content, and presentation of clouds

Together, these broad trends mean we can expect to see a second generation of numerous and diverse tag clouds valued for content and capability over form. Second generation clouds will be easier to understand (when designed correctly…) and open to manipulation by users via increased functionality. In this way, clouds will visualize semantic fields for a greater range of situations and needs, across a greater range of specificity, in a greater diversity of information environments, for a greater number of more varied cloud consumers.

Usage Trends
To date, tag clouds have been applied to just a few kinds of focuses (links, photos, albums, blog posts are the more recognizable). In the future, expect to see specialized tag cloud implementations emerge for a tremendous variety of semantic fields and focuses: celebrities, cars, properties or homes for sale, hotels and travel destinations, products, sports teams, media of all types, political campaigns, financial markets, brands, etc.

From a business viewpoint, these tag cloud implementations will aim to advance business ventures exploring the potential value of aggregating and exposing semantic fields for a variety of strategic purposes:
1. Creating new markets
2. Understanding or changing existing markets
3. Providing value-added services
4. Establishing communities of interest / need / activity
5. Aiding oversight and regulatory imperatives for transparency and accountability.

Measurement and Insight
I think tag clouds will continue to develop as an important potential measurement and assessment vehicle for a wide variety of purposes; cloudalicious is a good example of an early use of tag clouds for insight. Other applications could include using tag clouds to present metadata in geospatial or spatiosemantic settings that combine GPS / GIS and RDF concept / knowledge structures.
Within the realm of user experience, expect to see new user research and customer insight techniques emerge that employ tag clouds as visualizations and instantiations of semantic fields. Maybe even cloud sorting?

Clouds As Navigation
Turning from the strategic to the tactical realm of experience design and information architecture, I expect tag clouds to play a growing role in the navigation of information environments as they become more common. Navigational applications comprise one of the first areas of tag cloud application. Though navigation represents a fairly narrow usage of tag clouds, in light of their considerable potential in reifying semantic fields to render them actionable, I expect navigational settings will continue to serve as a primary experimental and evolutionary venue for learning how clouds can enhance larger goals for information environments such as enhanced findability.

For new information environments, the rules for tag clouds as navigation components are largely unwritten. But many information environments already have mature navigation systems. In these settings, tag clouds will be one new type of navigation mechanism that information architects and user experience designers integrate with existing navigation mechanisms. David Fiorito’s and Richard Dalton’s presentation Creating a Consistent Enterprise Web Navigation Solution is a good framework / introduction for questions about how tag clouds might integrate into mature or existing navigation systems. Within their matrix of structural, associative and utility navigation modes that are invoked at varying levels of proximity to content, tag clouds have obvious strengths in the associative mode, at all levels of proximity to content, and potential strength in the structural mode. Figure 1 shows two tag clouds playing associative roles in a simple hypothetical navigation system.

Figure 1: Associative Clouds

I also expect navigation systems will feature multiple instances of different types of tag clouds. Navigation systems employing multiple clouds will use combinations of clouds from varying contexts (as flickr and technorati already do) or domains within a larger information environment to support a wide variety of purposes, including implicit and explicit comparison, or views of the environment at multiple levels of granularity or resolution (high level / low level). Figure 2 illustrates multiple clouds, Figure 3 shows clouds used to compare the semantic fields of a one focus chosen from a list, and Figure 4 shows a hierarchical layout of navigational tag clouds.

Figure 2: Multiple Clouds

Figure 3: Cloud Comparison Layout

Figure 4: Primary / Secondary Layout

Structural and Behavioral Trends
Let’s move on to consider structural and behavioral trends in the second generation of tag clouds.
Given the success of the simple yet flexible structure of first generation tag clouds, I expect that second generation clouds will not substantially change their basic structure. For example, tag clouds will not have to change to make use of changing tagging practices that enhance the semantic depth and quality of tags applied to a focus, such as faceted tagging, use of qualifiers, hierarchical tagging, and other forms. James Melzer identifies some best practices on del.icio.us that make considerable sense when the focus of a semantic field is a link. His recommendations include:

• Source your information with via:source_name or cite:source_name
• Create a parent categories, and thus a rudimentary hierarchy, with parent_tag/subject_tag
• Mention publications names with in:publication_name
• Flag the type of resource with .extension or =resource_type
• Use a combination of general and specific tags on every bookmark to provide both clustering and differentiation
• Use synonyms or alternate forms of tags
• Use unique or distinctive terms from documents as tags (don’t just use major subject terms)

The two element structure of first generation tag clouds can accommodate these tagging practices. However, with a semantic field of greater depth and richness available, the interactions, behaviors, and presentation of tag clouds will evolve beyond a static set of hyperlinks.

Cloud consumers’ need for better context will drive the addition of features and functionality that identify the context of a tag cloud explicitly and in detail. For example, clouds created by a defined audience will identify that audience, whether it be system administrators, freelance web designers, DJ’s, or pastry chefs rating recipes and cooking equipment and provide indication of the scope and time periods that bound the set of tags presented in the cloud. Flickr and others do this already, offering clouds of tags covering different intervals of time to account for the changing popularity of tags over their lifespan.

Moving from passive to interactive, tag clouds will allow users to change the cloud’s semantic focus or context with controls, filters, or other parameters (did someone say ‘sliders’ – or is that too 5 minutes ago…?). I’ve seen several public requests for these sorts of features, like this one: “It would be great if I could set preferences for items such as time frame or for tags that are relevant to a particular area etc or even colour the most recent tags a fiery red or remove the most recent tags.” Figure 5 shows a tag cloud with context controls attached.

Figure 5: Context Controls

Figure 6: Behavior Controls

Diversifying consumer needs and goals for way finding, orientation, information retrieval, task support, product promotion, etc., will bring about inverted tag clouds. Inverted tag clouds will center on a tag and depict all focuses carrying that tag.

Figure 7: Inverted Clouds Show Conceptually Related Focuses

In the vein of continued experiment, tag clouds will take increased advantage with RIA / AJAX and other user experience construction methods. Following this, tag clouds may take on some of the functions of known navigation elements, appearing as sub-menus / drop down menus offering secondary navigation choices.

Figure 8: Clouds As Drop Menus

Along the same lines, tag clouds will demonstrate more complex interactions, such as spawning other tag clouds that act like magnifying lenses. These overlapping tag clouds may offer: multiple levels of granularity (a general view and zoom view) of a semantic field; thesaurus style views of related concepts; parameter driven term expansion; common types of relationship (other people bought, by the same author, synonyms, previously known as, etc.)

Figure 9: Magnifying Clouds

Genres
Looking at the intersection of usage and behavior trends, I expect tag clouds will evolve, differentiate, and develop into standard genres. Genres will consist of a stable combination of tag cloud content, context, usage, functionality, and behavior within different environments. The same business and user goals that support genres in other media and modes of visualization will drive the development of these tag cloud genres. One genre I expect to see emerge shortly is the search result.

Conclusions
Reading over the list, I see this is an aggressive set of predictions. It’s fair to ask if I really have such high expectations for tag clouds? I can’t say tag clouds will take over the world, or even the Internet. But I do believe that they fill a gap in our collective visualization toolset. The quantity, quality, and relevance of semantic information in both real and virtual environments is constantly increasing. (In fact, the rate of increase is itself increasing, though that is a temporary phenomenon.) I think tag clouds offer a potential to quickly and easily support the chain of understanding that’s necessary for semantic fields across diverse kinds of focuses. There’s need for that in many quarters, and I expect that need to continue to grow.

For the moment, it seems obvious that tag clouds will spend a while in an early experimental phase, and then move into an awkward adolescent phase, as features, applications and genres stabilize in line with growing awareness and comfort with clouds in various settings.

I expect these predictions to be tested by experiments will play out quickly and in semi or fully public settings, as in the example of the dialog surrounding 83 degrees usage of a tag cloud as the sole navigation mechanism on their site that Rashmi Sinha’s post The tag-cloud replaces the basic menu – Is this a good idea? kicked off recently.

My answer to this question is that replacing all navigation menus with a tag cloud is only a good idea under very limited circumstances. It’s possible that 83 Degrees may be one of these limited instances. Startups can benefit considerably from any positive attention from the Web’s early adopter community (witness Don’t Blow Your Beta by Michael Arrington of Techcrunch).

The page’s designer said, “In this case it was done as a design/marketing effort and not at all for UI”. Since attracting attention was the specific purpose, I think the result is a success. But it’s still an experimental usage, and that’s consistent with the early stage of evolution / development of tag clouds in general.

I’m looking forward to what happens next…

Zeldman jokingly called tag clouds “the new mullets” last year. At the time, I think he was taken a bit by surprise by the rapid spread of the tag cloud (as many people were). A big year later, it looks like this version of the world’s favorite double duty haircut will stay in fashion for a while. Zeldman was discussing the first generation of tag clouds. I have some ideas on what the second generation of tag clouds may look like that will conclude this series of two essays. These two pieces combine ideas brewing since the tagging breakout began in earnest this time last year, with some predictions based on recent examples of tag clouds in practice.

Update: Part two of this essay, Second Generation Tag Clouds, is available.

This first post lays groundwork for predictions about the second generation of tag clouds by looking at what’s behind a tag cloud. I’ll look at first generation tag clouds in terms of their reliance on a “chain of understanding” that semantically links groups of people tagging and consuming tags, and thus underlies tagging and social metadata efforts in general. I’ll begin with structure of first generation tag clouds, and move quickly to the very important way that tag clouds serve as visualizations of semantic fields.

Anatomy of a Tag Cloud
Let’s begin with the familiar first generation tag cloud. Tag clouds (here we’re talking about the user experience, and not the programmatic aspects) commonly consist of two elements: a collection of linked tags shown in varying fonts and colors to indicate frequency of use or importance, and a title to indicate the context of the collection of tags. Flickr’s tags page is the iconic example of the first generation tag cloud. Screen shots of several other well known tag cloud implementations show this pattern holding steady in first generation tagging implementations such as del.icio.us and technorati, and in newer efforts such as last.fm and ma.gnolia.
Wikipedia’s entry for tag cloud is quite similar, reading, “A tag cloud (more traditionally known as a weighted list in the field of visual design) is a visual depiction of content tags used on a website. Often, more frequently used tags are depicted in a larger font or otherwise emphasized, while the displayed order is generally alphabetical… Selecting a single tag within a tag cloud will generally lead to a collection of items that are associated with that tag.”

In terms of information elements and structure, first generation tag clouds are low complexity. Figure 1 shows a schematic view of a first generation tag cloud. Figures 2 through 5 are screenshots of well-known first generation tag clouds.

Figure 1: Tag Cloud Structure

Figure 2: last.fm

Figure 3: technorati

Figure 4: del.icio.us

Figure 5: Ma.gnolia

Tag Clouds: Visualizations of Semantic Fields
The simple structure of first generation tag clouds allows them to perform a very valuable function without undue complexity. That function is to visualize semantic fields or landscapes that are themselves part of a chain of understanding linking taggers and tag consumers. This is a good moment to describe the “chain of understanding”. The “chain of understanding” is an approach I use to help identify and understand all the different kinds of people and meaning, and the transformations and steps involved in passing that meaning on, that must work and connect properly in order for something to happen, or an end state to occur. The chain of understanding is my own variation / combination of common cognitive and information flow mapping using a scenario style format. I’ve found the term resonates well with clients and other audiences outside the realm of IA.

How does the chain of understanding relate to tag clouds? The tags in tag clouds originate directly from the perspective and understanding of the people tagging, but undergo changes while becoming a tag cloud. (For related reading, see Rashmi Sinha’s A social analysis of tagging which examines some of the social mechanisms underlying the activity of tagging.) Tag clouds accrete over time when one person or a group of people associate a set of terms with a focus of some sort; a photo on flickr, a URL / link in the case of del.icio.us, an album or song for last.fm. As this list shows, a focus can be anything that can carry meaning or understanding. The terms or tags serve as carriers and references for the concepts each tagger associates with the focus. Concepts can include ideas of aboutness, origin, or purpose, descriptive labels, etc. While the concepts may change, the focus remains stable.

What’s key is that the tag is a reference and connection to the concept the tagger had in mind. This connection requires an initial understanding of the focus itself (perhaps incorrect, but still some sort of understanding), and the concepts that the tagger may or may not choose to associate with the focus. And this is the first step in the chain of understanding behind tag clouds, as shown in Figure 6.

Figure 6: Origin: Focus and Concepts

As a result, tag clouds are more than collection of descriptive or administrative terms attached to a link, or other sort of focus. The tag is a sort of label that references a concept or set of concepts. A cloud of tags is then a collection of labels referring to a cluster of aggregated concepts. The combination of tags that refer to concepts, with the original focus, creates a ‘semantic field’. A semantic field is the set of concepts connected to a focus, but in a form that is now independent of the originating taggers, and available to other people for understanding. In this sense, a semantic field serves as a form of reified understanding that the taggers themselves – as well as others outside the group that created the semantic field – can now understand, act on, etc. (This speaks to the idea that information architecture is a discipline strongly aimed at reification, but that’s a different discussion…). Figure 7 shows this second step in the chain of understanding; without it, there is no semantic field, and no tag cloud can form. And now because this post is written from the viewpoint of practical implications for tag cloud evolution, I’m going to hold the definition and discussion of a semantic field and focus, before I wander off track into semiotics, linguistics, or other territories. The most important thing to understand is that *tag clouds comprise visualizations of a semantic field*, as we’ve seen from the chain of understanding.
Figure 7: Semantic Field

I believe tag clouds are revolutionary in their ability to translate the concepts associated with nearly anything you can think of into a collectively visible and actionable information environment, an environment that carries considerable evidence of the original understandings that precede and inform it. In a practical information architecture sense, tag clouds can make metadata – one of the more difficult and abstract of the fundamental concepts of the digital universe for the proverbial person on the street – visible in an easily understood fashion. The genius of tag clouds is to make semantic concepts, the frames of understanding behind those concepts, and their manifestation as applied metadata tangible for many, many people.

Figure 8: Semantic Field As Tag Cloud

With this notion of a tag cloud as a visualization of a semantic field in mind, let’s look again at an example of a tag cloud in practice. The flickr style tag cloud (what I call a first generation tag cloud) is in fact a visualization of many tag separate clouds aggregated together. Semantically then, the flickr tag cloud is the visualization of the cumulative semantic field accreted around many different focuses, by many people. In this usage, the flickr tag cloud functions as a visualization of a semantic landscape built up from all associated concepts chosen from the combined perspectives of many separate taggers.

To summarize, creating a tag cloud requires completion of the first three steps of the chain of understanding that supports social metadata. Those steps are:
1. Understanding a focus and the concepts that could apply that focus
2. Accumulating and capturing a semantic field around the focus
3. Visualizing the semantic field as a tag cloud via transformation
The fourth step in this chain involves users’ attempts to understand the tag cloud. For this we must introduce the idea of context, which addresses the question of which original perspectives underlie the semantic field visualized in a tag cloud, and how those concepts have changed before or during presentation.

How Cloud Consumers Understand Tag Clouds
Users need to put a given tag cloud in proper context in order to understand the cloud effectively. Their end may goals may be finding related items, surveying the thinking within a knowledge domain, identifying and contacting collaborators, or some other purpose, but it’s essential for them to understand the tags in the cloud to achieve those goals. Thus whenever a user encounters a tag cloud, they ask and answer a series of questions intended to establish the cloud’s context and further their understanding. Context related questions often include “Where did these tags come from? Who applied them? Why did they choose these tags, and not others? What time span does this tag cloud cover?” Context in this case means knowing enough about the conditions and environment from which the cloud was created, and the decisions made about what tags to present and how to present them. Figure 9 summarizes the idea of context.

Figure 9: Cloud Context

Once the user or consumer places the tag cloud in context, the chain of understanding is complete, and they can being to use or work with the tag cloud. Figure 10 shows the complete chain of understanding we’ve examined.
Figure 10 Chain of Understanding

In part two, titled “Second Generation Tag Clouds”, I’ll share some thoughts on likely ways that the second generation of tag clouds will evolve in structure and usage in the near future, based on how they support a chain of understanding that semantically links taggers and tag cloud consumers. Context is the key for tag cloud consumers, and we’ll see how it affects the likely evolution of the tag cloud as a visualization tool.

Update: Part two Second Generation Tag Clouds is available

This weekend, some of my earlier posts discussing the user experience of Lotus Notes surfaced in the Notes community. Ed Brill – in a posting titled Mary Beth has been taking on the critics – referenced my mention of how the head of the Notes UI team was employing user research as a bridge to customers. Ed complimented the design team for reaching out to critics in public. This is a well-deserved pat on the back. Yet it falls short of recognizing the more important point that direct user research should be a basic component of any company’s overall strategy and planning for long term success (or survival).

Why? User research helps build customer relationships, further design efforts, and identify new business opportunities when applied across audiences (internal and external constituencies) and perspectives (marketing, sales, product development), and with an eye for needs beyond immediate feedback. This sort of engagement with customers of a software product (or any kind of product) should *not* be special or noteworthy – it should happen all the time. Continuously. I’m thinking of Jared Spool’s remarks during his keynote at UI10, to the effect that the user experience perspective is most successful when it it is a basic component of a company’s culture, and thus an assumed aspect of every initiative.

In fact, in a socially transparent, networked, and aware environment like the current FuturePresent, user research serves as a fundamental, indispensable form of research and development that companies and organizations must support as part of their portfolio of methods for seeking broad based environmental feedback (also here). I’ll go so far as to say that user research may move beyond the realm of essential corporate R&D, and qualify as genuine basic research.

BTW: maybe it’s just me, but isn’t it a bit ominous that the tag line for Notes 7 is “Innovate. Collaborate. Dominate.” ? Sounds like something the Borg might say if you asked them how to make breakfast…

On Saturday and Sunday, I took advantage of the Blizzard of ’06 to:

1. imple­ment a tag cloud for navigation
2. tag all posts with sub­ject metadata
3. rebuild the some­what creaky col­lec­tion of stylesheets behind JL.com
4. add a recent com­ments tile

(And people say I don’t know how to have a good time…?)

The tag cloud is powered by the MoveableType plugin Tags.App. New stylesheets are loosely based on an OpenSource template from www.oswd.org called Phenom.

Between trips outside to shovel, I forgot to upload one of the new .css files. Following that, some Notes apologists justly sent me to school for displaying my comments in cripplingly small text font.

Thanks to the Notes faithful for the feedback, and condolences to any and all who contracted eye strain as a result.

In two earlier posts about Starbucks and product metadata, I mentioned the strange sensation of a product experience overwhelmed by packaging – specifically the metadata aspects of the packaging. Now I’d like to share two more examples of packaging burdened with metadata cruft. The first shows an awkward translation that is an attempt to smooth a significant semantic transition or boundary, one created by a high degree of relative cultural and conceptual distance between Dutch and English food categories. The second shows a phenomenon I call brand subsumption. These examples of translation and brand subsumption broaden the original problem into one of inconsistency and misalignment with the overall experience. Starbucks has built an empire on the repeatable, predictable customer experience, and so this inconsistency impacts the Starbucks brand. [At least for those who read the packaging for their food…]

In the first example, Starbucks uses a marketing dictionary to transform stroopwafels into ‘Dutch Caramel Wafers’ that are ‘rich and caramelly-sweet’. I can understand the inclination to change the product name; stroopwafel is a Dutch word that’s likely outside the awareness of most Starbucks customers. And it’s certainly further away in terms of cultural distance than ‘madeleine’. But the resulting translation is awkward because it addresses a very narrow point of view: It’s only if you’ve forgotten the proper Dutch word while trying to explain the concept of a stroopwafel that you’ll need to fall back on a label that reads “Dutch caramel wafer”.

Caramel Wafers Label:

Example two is a branding mashup, involving Walkers Short Bread Cookies and Starbucks. In addition to the standard labeling from the madeleines, we’re now told the maker, the country of origin, and when the maker was established, for a total of six pieces of information. The new elements exactly match the standard branding of most Walkers merchandise. I call this phenomenon brand subsumption, when one brand subsumes another without breaking it down. The Walkers brand arguably has greater international recognition and a longer history than Starbucks, so I imagine the deal bringing their ‘delectably buttery’ cookies to Starbucks counters everywhere required this unusual compromise. The resulting experience is an uneven hybrid; not Walkers, not Starbucks.

Walkers Package Label:

Looking at all three products together, it’s clear the new product family attached to both packages, ‘International Treats’, contributes to the brand impact by introducing a puzzling inconsistency. Compare the original item that started us on this path – madeleines, designated ‘Traditional Favorites’ – with the Dutch and Scottish products labeled ‘International’. Labeling the madeleines French but not international makes no sense, until you turn over the packages: the stroopwafels are made in the Netherlands, the shortbread cookies are made in Scotland, and the madeleines are made in the US. The same product label on one package denotes a cultural category for food items, but on other packages defines the manufacturing location. The product family labels are used for different purposes, which belies their consistent presentation context across products, via similar style, layout, structure, colors, fonts, etc.

Altogether, the combination of metadata quantity, labeling inconsistency, and branding strategies of translation and subsumption, is unexpected from Starbucks – a company built on consistent customer experiences.

It’s only February, but I can already tell that I’m going to say “SharePoint is *not* an intranet!” many, many, many times in 2006…

At Peter Boersma’s invitation.
Who else has delivered newspapers?
Four Jobs I’ve Had
1. paperboy
2. radio DJ
3. pizza maker
4. entrepreneur

Four Movies I Can Watch Over And Over
1. The Blues Brothers (not the new one)
2. Le Samourai
3. In The Mood For Love
4. Last Life In the Universe

Four Places I’ve Almost Lived, And Still Plan To
1. Hong Kong
2. New York
3. San Francisco
4. Amsterdam

Four TV Shows I Love
1. Battlestar Galactica (the new one, the new one)
2. Iron Chef (not the new one)
3. The Daily Show
4. Arrested Development

Places I’ve Vacationed
1. Barcelona
2. Sorrento
3. Lisbon
4. Yuong Shua

Four of My Favorite Dishes
1. Seared Tuna
2. Osso Bucco
3. Pho
4. Spicy Fish Tacos

Four Sites I Visit Daily
1. Amazon – been buying a lot of books these past weeks…
2. allofmp3.com – where I get my music fix
3. cmswatch.com – indispensable when you’re working a cms gig
4. Coolhunting.com – when you need a break from the functional

Four Places I Would Rather Be Right Now
1. In an enoteca in Rome
2. Riding my Custom X
3. Sipping a mojito on the beach
4. In an art gallery

Four Bloggers I’m Tagging
1. Davezilla (much funnier than anything you’ll see here…)
2. Facetime (is there such a thing as italian motorcycle envy…)
3. Rashmi Sinha (rashmi’s blog is consistently of stellar quality – will she join in some frivolous sociability?)
4. Seth Gordon (seth’s in seattle now, will he have time to indulge an old east coast buddy?)