vanderwal.net

Say Hey - If I Knew

I have a deep love of digital technology as an assistive devise and even an enabling device. But, I need something that sits between the digital and the real so to join those worlds.

Here is the problem... I am continually not blanking at who somebody I know in a digital context (through e-mail, a social networking tool (one that works), listserves, blogs, etc.), but their face or just lack of some means of connecting those I know to who they are physically. It continually happens at conferences or when traveling. This happened three times to me at WebVisions with Matt May, Erin Kissane, and Kris Krug. With all three it took some time before it clicked, fortunately with Matt it clicked while I still had time to draw the lines. I would have loved to have chatted with Erin and Kris with the context of how I know them firmly in place. Part of the problem it did not register to me that they were going (I am not sure I checked close enough to the event Upcoming to see who was going to I could make a mental note (or otherwise) to say hey.

What would the solution be? The gap between digital and physical must close. I need my address book crossed with my digital social networks and get all of the pieces tied together with one identity that I can track. Sure everybody can keep their 16 screen names across different communities, but we need to aggregate those to one identity when it makes sense, such as meeting in person. I have been told Sxip can handle this, but I have not had the time to track that down.

The next step is to take the aggregated identity and go through events I am attending or places traveling and let me know who will be there. I am not see this as a privacy issue as there are established friend relationships and set with parameters of securely allowing access to our information, or it has be made public. I usually have a mental list of who I want to see and talk to prior to events, but that group is growing. There is also a group of people I normally only see at events and I always try to hang with that "floating island", but I am usually in contact with them long before.

It seems like a tool like Upcoming would be a perfect place to do this for a large chunk of events. It will still take aggregating the identities across all of the digital communities I belong, address books, and in-person communities. I would love for the next step to include an application in my mobile device that tipped me off to somebody on my friendly "say hey" list being with in "hey" range.

State is the Web

The use and apparent mis-use of state on the web has bugged me for some time, but now that AJAX, or whatever one wants to call "XMLHttpRequests", is opening the door to non-Flash developers to ignore state. The latest Adaptive Path essay, It's A Whole New Internet, quotes Michael Buffington, "The idea of the webpage itself is nearing its useful end. With the way Ajax allows you to build nearly stateless applications that happen to be web accessible, everything changes." And states, "Where will our bookmarks go when the idea of the 'webpage' becomes obsolete?"

I agree with much of the article, but these statements are wholly naive in my perspective. Not are they naive, but they hold up examples of the web going in the wrong direction. Yes, the web has the ability to build application that are more seemless thanks to the that vast majority of people using web browsers that can support these dynamic HTML techniques (the techniques are nothing new, in fact on intranets many of us were employing them four or five years ago in single browser environments).

That is not the web for many, as the web has been moving toward adding more granular information chunks that can be served up and are addressible. RESTful interfaces and "share this page" links are solutions. The better developers in the Flash community has been working to build state into their Flash presentations to people can link to information that is important, rather than instructing others to click through a series of buttons or wait through a few movies to get to desired/needed information. The day of one stateless interface for all information was behind us, I hope to hell it is not enticing a whole new generation of web developers to lack understanding of state.

Who are providing best examples? Flickr and Google Maps are two that jump to mind. Flickr does one of the best jobs with fluid interfaces, while keeping links to state that is important (the object that the information surrounds, in this case a photograph). Google Maps are stunning in their fluidity, but during the whole of one's zooming and scrolling to new locations the URL remains the same. Google Map's solution is to provide a "Link to this page" hyperlink (in my opinion needs to be brought to the visual forefront a little better as I have problems getting people to recognize the link when they have sent me a link to maps.google.com rather than their intended page).

Current examples of a poor grasp of state is found on the DUX 2005 conference site. Every page has the same URL, from the home page, to submission page, to about page. You can not bookmark the information that is important to yourself, nor can you send a link to the page your friend is having problems locating. The site is stateless in all of its failing glory. The designer is most likely not clueless, just thoughtless. They have left out the person using the site (not users, as I am sure their friends whom looked at the design thought it was cool and brilliant). We have to design with people using and resusing our site's information in mind. This requires state.

When is State Helpful?

If you have important information that the people using your site may want to directly link to, state is important as these people will need a URL. If you have large datasets that change over time and you have people using the data for research and reports, the data must have state (in this case it is the state of the data at some point in time). Data that change that does not have state will only be use for people that enjoy being selected as a fool. Results over time will change and all good academic research or professional researchers note the state of the data with time and date. All recommendations made on the data are only wholly relevant to that state of the data.

Nearly all blogging tools have "permalinks", or links that link directly to an unchanging URL for distinct articles or postings, built into the default settings. These permalinks are the state function, as the main page of a blog is fluid and ever changing. The individual posts are the usual granular elements that have value to those linking to them (some sites provide links down to the paragraph level, which is even more helpful for holding a conversation with one's readers).

State is important for distinct chunks of information found on a site. Actions do not seem state-worthy for things like uploading files, "loading screens", select your location screens (the pages prior and following should have state relative to the locations being shown on those pages), etc.

The back button should be a guide to state. If the back button takes the user to the same page they left, that page should be addressable. If the back button does not provide the same information, it most likely should present the same information if the person using the site is clicking on "next" or "previous". When filling out an application one should be able to save the state of the application progress and get a means to come back to that state of progress, as people are often extremely aggravated when filling out longs forms and have to get information that is not in reach, only to find the application times out while they are gone and they have to start at step one after being many steps into the process.

State requires a lot of thought and consideration. If we are going to build the web for amateurization or personal information architectures that ease how people build and structure their use of the web, we must provide state.

Annotated New York Times

The Annotated New York Times is the best interface for blog coverage out there. Feedster and Technorati are leagues behind in their presentation compared to this. I had not been to BlogRunner in a while, but it has grow-up too. The interface, interaction, and presentation are dead-on for an intuitive tool. Bravo.

I do wish it were easier to find book review annotations more easily, such as by author or book title.

Simplicity Through Granular Complexity

We must understand and embrace the granular and complex to make things simple for the person.

All the Blog that is Fit To...

From the blog realm. Elise Bauer provides an excellent overview of available blog tools. This is a very good article on the business of weblog tool development and what the tools offer.

The fine folks at Six Apart launched their redesign today. Not only is there a new look, but the navigation is improved and is now consistent. All of the Six Apart properties are now united, which is also very helpful. Their site is looking less like a blog and more like a professional software company, but the secret it is their sites are run by their blogging tools. Great job 6A and Mule who did much of the work!

Information Waste is Rampant

Fast Company published costs facing business. The top four relate to poor design and information use: Poor knowledge harnessing ($1.4 Trillion); Digital publishing inefficiencies ($750 billion); Data quality problems ($600 billion); and Paper-based trade processes ($400 billion). That is 3.15 Trillion U.S. dollars down the tubes with no benefit.

The solutions are not that difficult, but everybody seems happy to use the rear view mirror to view the future.

Christina stated, "What me worry" about design and business. The whole CIO is a sham as the CIO is a technology driven person, which is tangentially related to information and technology still hinders information flow if not planned for properly (more on this is coming in the near future here on this site). There needs to be a chief level position that cares about the information, the people using it, and the people who create the information. To Christina's post I responded with the following on her site (posted here so I can better keep track of it):

It seems like the 80s all over again. The focus on design in the to late 80s, mostly with unified branding and creative practices formally brought in-house. There was a lot of push around design, mostly labelled branding (nearly the exact same discussions, but slightly different terms). Much of this was around the brandhouses like Landor. The business community embraced the results and tried to incorporate the creative culture as part of their own.

What happened? The innovators were bought by large advertising or public relation firms and the firms changed their industry term to communication companies. Companies created corporate communication divisions (comprised of adversising, PR, branding, and other creative endevors) and had high level management visability.

By the early 90s the corporate environment had largely subsumed the communication into marketing and business schools that has embraced the creative mindset followed suit. Today marketing is often what trumps design and there is no creative in marketing. The creative departments by the late 90s had been gutted by the web craze. This left business types with little creative craft understanding as those driving what was once good.

It is not suprising that currently named "design" is taking off, as what was good about the creative was gutted and most companies lack central design plans. There is tremendous waste in cross medium design, as few sites are built with an understanding of the digital medium, let alone cross platform design or true cross media design. Part of the problem is far too few designers actually understand cross-platform and/or cross-media design. There is millions wasted in bandwidth on poor web design that is using best practices from the late 90s not those from today. There is no integration of mobile, with a few exceptions in the travel industry. There is still heavy focus on print, but very little smart integration of design in the digital medium. This even applies to AIGA, which is a great offender of applying print design techniques on the web. How can we expect business design to get better if one of the pillars of the design profession has not seemed to catch on?

There are large problems today and we need to break some of our solutions were have been trying to get to solutions that work. Not only do today's solutions not work today, they will not work tomorrow as they are only stop gaps. Cross-platform, cross-device, and cross-medium design solutions are needed, but technology is not here to deliver and few that I have run across in the design world are ready for that change as they have not made the change to today's world.

Today's designer focusses on getting the information in front of the user and stops there. They do not consider how this person or machine may reuse the information. There is so much yet to improve and yet the world is progressing much faster than people can or want to change to keep up. There are designers and developers who will not build for mobile (it is not that hard to do) because they do not see them in the user logs. They fail to see the correlation that their sites suck for mobile and mobile users may test once and go somewhere else for their information. The people that are seeing mobile users in their logs are the ones that have figured out how to design and develop for them properly (most have found that it is relatively inexpensive to do this). This is not rocket science, it is using something other than the rear view mirror to design for now and the future.

Model-T is User Experience Defined

Peter Boersma lays out Model T: Big IA is UX. I completely agree with this assessment and view. The field of Information Architecture is very muddled in the eyes of clients and managers as those pitching the services mean different things. Personally I think Richard Saul Wurman's incredible book on information design labeled "Information Architecture" caused a whole lot of the problem. The little IA was evident in the Wurman book and there are many concepts that were delivered to the IA profession from that book, but it was largely about information design.

Getting back to Peter Boersma's wonderful piece, the Model-T hits the correlated professions and roles dead on. This is essentially how things are organized. There are some of us that go deep in more than one area and others that are shallow in most, but also tend to provide great value.

Preview of Visual Rhetoric in a Digital World

I went on a little book buying spree this past week as I am finishing reading the last binge buy or two. I picked up a couple O'Reilly reference books (will review them later) and a few books from the interaction design, cogsci, and information design arena. The one that is standing out in as I preview them is the Visual Rhetoric in a Digital World : A Critical Sourcebook by Carolyn Handa. This book is a collection of essays and articles from various well quoted and referred to designers, writers, and academics. Looking through the references and end-notes the heros of communication research are used for the foundations of those chosen to write. Visual Rhetoric is focussed on the academic world, but if we are not learning every day we will never get better, and this book could fill in the gaps.

The book is broken into five sections: Toward a Pedagogy of the Visual, The Rhetoric of the Image, The Rhetoric of Design, Visual Rhetoric and Argument, and Visual Rhetoric and Culture. The names of the writers that jump out are Gunter Kress, Catherine L. Hobbes, J.L. Lemke, Rudolph Arnheim, Roland Barthes, Scott McCloud, Jeffery Keedy, Jessica Helfand, Keith Kenney, Michele S. Shauf, Richard A. Lanham, Robert Horn, and Bell Hooks drew my attention. I have a very strong feeling this will be a great resource. I don't think it will bump Digital Ground by Malcolm McCullough from my vote for the best book I have read this year, but it is proving 2004 is a very strong year for books.

Gordon Rugg and the Verifier Method

In the current Wired Magazine an article on Gordon Rugg - Scientific Method Man (yes, it is the same Gordon Rugg of card sorting notoriety). The article focuses on his solving the Voynich manuscript, actually deciphering it as a hoax. How he goes about solving the manuscript is what really has me intrigued.

Rugg uses a method he has been developing, called the verifier approach, which develops a means critical examination using:

The verifier method boils down to seven steps: 1) amass knowledge of a discipline through interviews and reading; 2) determine whether critical expertise has yet to be applied in the field; 3) look for bias and mistakenly held assumptions in the research; 4) analyze jargon to uncover differing definitions of key terms; 5) check for classic mistakes using human-error tools; 6) follow the errors as they ripple through underlying assumptions; 7) suggest new avenues for research that emerge from steps one through six.

One area that Rugg has used this has been solving cross-discipline terminology problems leading to communication difficulties. He also found that pattern-matching is often used to solve problems or diagnose illness, but a more thorough inquiry may have found a more exact cause, which leads to a better solution and better cure.

Can the verifier method be applied to web development? Information Architecture? Maybe, but the depth of knowledge and experience is still rather shallow, but getting better every day. Much of the confounding issues in getting to optimal solutions is the cross discipline backgrounds as well as the splintered communities that "focus" on claimed distinct areas that have no definite boundaries and even have extensive cross over. Where does HCI end and Usability Engineering begin? Information Architecture, Information Design, Interaction Design, etc. begin and end. There is a lot of "big umbrella" talk from all the groups as well as those that desire smaller distinct roles for their niche. There is a lot of cross-pollination across these roles and fields as they all are needed in part to get to a good solution for the products they work on.

One thing seems sure, I want to know much more about the verifier method. It seems like understanding the criteria better for the verifier method will help frame a language of criticism and cross-boundary peer review for development and design.

Design Engaged Announced

A new design forum has been announced, Design Engaged has been organized by Andrew Otwell and will be held in Amsterdam, Netherlands November 12 to 14, 2004. The format sounds very tempting.

UXnet Aims to Unite the Splinters

Having trouble figuring what group will help you in your carreer as as a web designer that keeps information architecture, usability, interaction design, experience design, etc. in your toolbelt?

It seems there is a group that has come togther to help be the glue and bring all of these splintered groups together. UXnet aims to be the glue that draws the groups together. Many designers and UX/IA/ExD/Etc folks are lost in finding one good home and one or two good conferences. There are many resources, too many is what much of these designers and researchers say. Many of us wear many hats and need a good cross pollination to get better.

I have hope that UXnet will help close the chasm that keeps everybody apart. There are representatives from many groups as a part of the team pulling things together.

Profiled at InfoDesign

I am the current InfoDesign Profile - Thomas Vander Wal. This was harder than I thought it would be an many alternate answers ran through my mind, but I finally narrowed it down as much as I could. Peter has many other wonderful profiles and interviews at InfoDesign Special. I have been inspired and found new resources from these glimpses into other designers lives.

Web Standards and IA Process Married

Nate Koechley posts his WebVision 2004 presentation on Web Standards and IA. This flat out rocks as it echos what I have been doing and refining for the last three years or more. The development team at work has been using this nearly exclusively for about couple years now on redesigns and new designs. This process makes things very easy to draft in simple wireframe. Then move to functional wireframes with named content objects in the CSS as well as clickable. The next step is building the visual presentation with colors and images.

This process has eased the lack of content problem (no content no site no matter how pretty one thinks it is) often held up by "more purple and make it bigger" contingents. This practice has cut down development and design time in more than half and greatly decreases maintenance time. One of the best attributes is the decreased documentation time as using the Web Developer Extension toolbar in Firefox exposes the class and id attributes that provide semantic structure (among many other things this great tool provides). When the structure is exposed documentation becomes a breeze. I can not think of how or why we ever did anything differently.

Tweaking the Botox Pixels

We have made some minor tweaks to the presentation of the site. The menu bar has had the underlining removed on hover. Each of the items in the menu now has borders that change with hover and selection to create a little cleaner look.

The date bar in the weblog has been padded and has a slight border to off set it from the page and make the date more readable, the date has bugged me for a long time.

The permalink (comments) page now has a title of the entry. The entry titles have been added to the monthly archive pages also.

Lastly, the link to the Quick Link RSS feed has been added next to the Quick link title. This should make it easier to follow those links, should you wish. The Quick Links get updated far more regularly of late and there are some good gems that get nestled in there.

Future of Local Search on Mac

One of the best things I found to come out of the Apple WWDC keynote preview of the next update of the OS X line, Tiger, Spotlight. Spotlight is the OS file search application. Not only does Spotlight search the file name, file contents (in applications where applicable), but in the metadata. This really is going to be wonderful for me. I, as a user, can set a project name in the metadata and then I can group files from that point. I can also set a term, like "synch" and use AppleScript and Search to batch the files together for synching with mobile devices, easily. Another nice feature is the searches can be saved and stored as a dynamic folder. This provides better control of my Personal InfoCloud.

Steven Johnson provides the history of search in Apple, which has nearly the same technology in Cosmo slated for release in 1996.