vanderwal.net

Social Machines in MIT Technology Review

In the August issue of MIT Technology Review in Wade Roush's cover story on Social Machines (posted on Wade's site) I get a nice quote. The article is well worth the read, even worth picking up the issue when it hits the stands. The article covers the social, mobile, and continuous computing world that some of us live in and many more will be doing soon. Those of us working at the front of the curve are working on ways to make it smoother for those who will follow along soon.

Convergence and the seamless transfer from stationary computing to continuous computing leads to drastically different interactions with information and media. We are already seeing the shift of people using mobile phones as just a voice communication medium to one that includes text and media interactions, or the from people listening to their mobile phones to looking at their mobile phones. Three years ago I made this shift and I was extremely frustrated as I had many more desires than my mobile phones could assuage. But, it is getting better today even if it takes more human interaction than is really needed to sync information, let alone have moved close to me (or whomever is the wanting to have the information or media stay attracted to themselves or have attracted in certain situations). It is this that is my focus of the Model of Attraction and the focus of the Personal InfoCloud.

Yahoo MyWeb 2.0 Goes Beta

Yahoo has launched Yahoo MyWeb 2.0 today. It has elements of Flickr but not the polish, nor the attention to detail. There are a lot of very rough edges, but there is a lot of potential also. I may spend some time playing around with it in the next few days and weeks. I surely will be sending a ton of feedback in. Hopefully MyWeb will iterate far more rapidly than their blogging software, which had rough edges and they still exist and no noticeable improvements have been made (I don't know many that will recommend it to nubies until the rough edges are fixed).

The tool from the very little I have looked at it seems like it has the broad folksonomy executed well. This seems to have many elements of del.icio.us integrated. I am curious is there is the capability to have community around tags (be same definition).

My curiosity is really piqued with the MyRank search engine. It seems to be a predictive engine of sorts, which really has my interest.

If you want to add me I can be found at tjvanderwal there in Yahoo! type places.

Designing with a Solution is the Problem

I finally put my finger on it. There has been growing frustration within me with where I work and as well with some of the leaders in the web design community of late. The problem and the solution has been known to me, but scattered in pieces and I did not pull all the pieces together until today. Why today? Well, it took a little doing, but I finally got my hands on this month's issue of Fast Company - June 2005, which I had been subscribed to until the May issue. It took a little bit of time to track down the issue as it was to the point in the month when the next months issues are getting put out. But, having that issue in hand (having read some on-line) I stumbled across my tipping point in the Be Cooler by Design column. I did not make it past the fouth paragraph when it hit.

It Begins with a Canyon

The paragraph has a header, "Show Them the Canyon" and discusses a designer at Ford, Giuseppe Delena, who would say, "Don't tell me you need a bridge, show me the canyon!" This was aimed at marketing people who would ask for specific design solutions, but not explain the problem.

That is my tipping point. Having to start with somebody's solution to design problems (most often solutions to the wrong problem). Not having the problems put forward, but an answer. An answer without anybody showing their work to how their arrived at the solution. For nearly four years I have been working, for the most part, with the end results of the work of others who started with a solution and worked that as a starting point, while never considering the problem (or in nearly all cases the multitude of problems they needed to solve). They did not understand the problems nor do they understand or know the standards and requirements that their end result must meet. Lastly they do not understand the medium in which they are working. In short it is a string of considerable messes that our team deals with continually. The sad complication is this is taxpayer money being spent (often quite nice sums) for end products that require incredible fixing to meet minimum standards and be usable on the web.

It is not my direct customer, who is in the same boat I am in as we support him (and he is one of the very few that really get what they are doing), but the "customer service" management and the management signing off on these projects that have become the problem. With the web, the business customer is not always right, the user is, as without the user their is no business customer. In our situation, by-and-large, the web being built is using what works for print and for multi-media, neither of which are solutions for text on the web. The business customer requires solutions for the wrong medium, which (as those who have sat through usability test find out) the tan text on brown background and all of the animated bits make using the information as is it is intended, nearly impossible.

Designers Must Explain Design Better

In part the design world is to blame as we have done a very poor job of educating the rest of the world as to what we do. We solve problems. We have spent an inordinate amount of time on learning everything we can about our medium, how people think, how people interact with our medium, how people interact with their devices (desktop, laptop, PDA, mobile, etc.) as they are all different, how to organize and structure for people interacting with what we design, how to build for people to give them freedom to choose the solution that is best for them, how to build for ease of use by people, and how to build for people to easily reuse what we provide (the list goes on). Yes, it is not a short list and I do not know a good designer who will truly claim they are done learning all of these aspects. We know what works best with everything we do know for the problems before us and we test everything we do and we iterate through our designs while always striving to make things better. Every designer I know loves to show how they got to their solution and document it for others to do, as their joy in designing is not repeating, but problem solving and innovating to better solutions. As designers we are always trying to learn what others do, so the good designers share in as much detail so others may learn what to follow and what to modify for even better solutions down the road.

In my current situation the lack of time to document and show our work is a major problem. The lack of documentation (or deliverables) is part of where the problem lies with the problems up the food chain (not that there are skilled designers or people that would understand up the food chain). If we had the time to show our work we could hand it to those at the beginning of the process so we could get better products with fewer problems when we receive them (although it is a very rare occasion that any of what we have produced for these purposes is ever followed). Many of the places up the food chain have sold a bridge with out ever seeing the canyon it is just a cookie cutter. It is rare when we get to solve the problems, either at the beginning or the end, we just get to fix it so it will just pass the minimum requirements, which are horribly low.

Understand and Explain the Problem First

This frustration has also flowed over to the web design community of late as there is excitement in the web community again. The excitement is not bad, actually it is great. But some of the new solutions are being framed as new wonder solutions without framing the problem they are solving. In the world of design (as it is with many other things) it is a realm where the answer to most every question is, "it depends". What is the solution? It all depends on many factors in the problem. Teaching how to understand problems and to walk through the decision process to get to the solution (or more correctly, one of many possible right solutions) is what raises the profession.

What has been happening of late in the web design/development community is looking at solutions that may be terrific implementations for a certain problem in a set environment, but proclaiming what is new is "the new way". For those that are not good designers or even designers at all, this approach reaches a problem point very quickly. It was not long after XMLHTTPRequest was coined AJAX that customers, and those I advise from farther away, started asking for their solutions to be AJAX. There are right places for AJAX, as it is just one of many solutions for problems where it may be one of the solutions. It is quite similar to aura around Flash as a solution, but AJAX has its benefits and detractors when compared to Flash.

Where the problem around the AJAX solution got tough was when AJAX was tied to a whole new exitement around the web. It was at this point the AJAX solution was being demanded from customers. I was hearing if from many corners, this great solution touted, was for customers the only way they would accept their final products. AJAX had quickly become the cure-all in customer's eyes, much like Flash had years before.

Our Responsibility

What we have to realize as designers, is people do listen and people want to believe there is one simple solution for all of their web problems, all of the information problems, etc. We know there is not a simple solution as of yet. In fact the digital information world is far more complex than it ever was, as Europe and Asia will attest, with the influx of mobile handheld use. (Europe and Asia have things a little better than the U.S. right now, as they have much less of a population that believes build for desktop (including laptop) solutions is the one way all design is heading.) Europe and Asia understand the world is far more complex and information far more useful when it can be used in context on a mobile device. The expanding of the devices and the realm of possibile solutions with their benefits and detractors across the many variables we monitor componded the problems we are solving. Simplicity is many designer's goal, but getting there is ever harder today and we must embrace the complexity (thank you Mike for turning that light on for me) and work through it. We also need to communicate the complexity to our customers so everybody understands it is not as simple as it seems.

It is this complexity of convergence around devices is also compounded by the flood of information people are experiencing, which is what has me loving the work I get to do around the Personal InfoCloud (and the Model of Attraction and folksonomy that are intertwined with it). This work is satisfying as it is not only defining the problems and working through possible solutions, but more importantly laying out frameworks to design and build solutions that others can use. There are increasingly people (who may become customers) that are coming and asking the right questions from the right perspective around the Personal InfoCloud, which may be another reason I really like working on it (we all love people asking smart questions). People are asking how to cross their canyon while describing the canyon and many times showing me the canyon they would like a solution designed for.

I think we all know what the next step is. It will not be happening tomorrow, but every day that passes makes the frustration that much worse. Knowing there is one point around which much of my frustration revolves may help me deal with it better.

Replacement RSS and XML Button

Mike just posted a killer international and language-free RSS logo button on his site. I really like it. Mainly is works for those of use who understand the RSS text version, but for those who are not as technically forward or in non-English/Western languages this could still work. The RSS and XML text on the buttons always need explanation to those not familiar with the terms. The end of many of the tutorials is often, "just click it, you do not really need to know what it means, just click". Something tells me Mike is on to something profound yet so wonderfully simple.

Heading to Los Angeles and SSAW at the Annenberg Center

I am off again this weekend. I will be in Los Angeles this weekend. So far I have most of Friday free. It looks like dinner may be taken on Friday evening as well as a beer or two to acclimate a Brit. Interesting things to see (other than my old house, junior high, and neighborhood) or meet-ups would be quite welcome.

I am at the Social Software in the Academy Workshop at the USC Annenberg Center on Saturday and Sunday. I will be chatting with Richard Cameron of CiteULike on Sunday. Not only does he run CiteULike, but he has been doing some interesting research on trends and patterns, which he is using to improve the probability the person using the service will find what they need more easily. We had a great chat last night and I am really looking forward to the public chat on Sunday.

The Art of the Pivot

We live life linearly, but there are many tangents and crossing points. Physical life makes surfing those tangents not an easy task, but it is part of the brilliance of digital life to surf serendipitously with purpose. Every now and then, with more increasing regularity I find myself in awe (yet with each occurrence with banality creeping in) of the tangential currents that draw life closer and the world smaller.

Flickr provided this evening's wonderful spark. While peering through the lens of my friends and "contacts" photos I clicked on one that had a familiar scene, it was not that I knew the people in the photo, but it was the table, cups, and feel of the place. It was a photo in the Pork Store on Haight Street. I have had so many wonderful breakfasts there from when I live behind the restaurant on Waller, to trekking over from where I lived on Arguello, to the pilgrimage on nearly every trip I make to San Francisco.

What made this particular photo special was not that I easily recognized the scene, but I double checked in Flickr's tags to see a "porkstore" tag. I clicked the tag to see if that photographer had entered more photos in the Pork Store, but no. I clicked to see "all other public photos tagged with porkstore". In doing this I saw in the thumbnail somebody I thought I recognized. I clicked to the larger photo to ensure it was somebody I had just met yesterday. The world just shrunk.

What was the point of this? It is the ability to pivot or surf in new direction that is related to where we are all thanks to the hyperlink and meta information. As the web has changed my perception of what is right and possible in the world, I increasingly find one of the major differentiators between physical life and digital experiences is the pivot. Including hyperlinks or means to pull information closer to you that is tangential to the current desire or direction. When relevant information is not hyperlinked it is lacking the pivot. Or when there is a lack of ease to find associated information that is relevant to what is in the browser and relevant to the person consuming the information or object on their screen it is frustrating for the user and disappointing as a developer knowing the ease of the solution and the great value it adds.

Oddly, one of the interfaces I love also bothers me for its lack of the pivot. The iPod is great, but it is missing one pivot option that is now driving me nuts. When in Shuffle mode and I hear a song I like by an artist I like often want to pivot and listen to more of that artist or that album. This should be an option on the center button, just like getting to add song rating, scroll through the song, etc. Not only is it in Shuffle mode it is when listening to mixed playlists or soundtracks. It should not be that difficult to implement, one of the screens clicked to from the center button, while listening to a song, should bring up a "listen to more by this artist or album" option. Then life would be so much better.

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.

Personal InfoCloud at WebVisions 2005

I, Thomas Vander Wal, will be presenting the Personal InfoCloud at the WebVisions 2005 in Portland, Oregon on July 15th. In all it looks to be a killer conference, just as it has been in the past. This year's focus is convergence (it is about time).

WebVisions is one of the best values in the web conference industry these days, as the early bird pricing is just $85 (US). You don't need an excuse, you just go. You spend a Friday bettering yourself and then Saturday in Powell's Books the evenings are spent talking the talk over some of the world's best beers served up fresh.

Crunch Time, as Usual

We are quite busy with articles, summaries, presentations, and e-mail these days. We have ideas and projects that need to get out of our heads on in to some functional space. Again we are looking for about 6 more hours in each day, that would do it. The other option would be to rearrange things we already have to put better focus on the stuff that will help the people who get it design and build for those that don't get it and shouldn't need to get it. What are we talking about time spent on the wrong things and working to spend time on the right things. What are the right things? We will tell you once we have time to knock some of them out.

Cryptic? It will not be once we have the key to set all of this free.

Yahoo360 and the Great Interaction Design Yardstick

Jeremy Zawodney talks about a Yahoo preview of Yahoo360 to which they invited "influencers" to provide honest feedback (Danah Boyd provides her wonderful view too).

What I really like about Jeremy's post is the repeated reference to Flickr when explaining things. The key thing is that Flickr (yes it is now owned by Yahoo) knocks the snot of of other's interaction design. Flickr set the standard and it is what many other web-based products are truly lacking. Getting the interface and interaction right is not half the battle, it is the battle. So few do it well and very few execs around the industry get that. What is lacking in so many products is design that creates, not just an ease of use, but a fun successful experience.

Flickr makes refindability of the pictures a person posts much easier by using tags that make sense to the person providing the tags. The interface for providing the tags is simple and does not take the user away from the interface (thanks to Ajax). The rest of the options are done simply from a person using the site's perspective. Everybody I know gets completely immersed in Flickr. This is something I can not say about Ofoto or other photo sharing sites, one goes to these sites to see the pictures somebody you know has taken. Flickr can be the most efficient photo sharing tool for uploading and managing one's own photos too.

Simply it is make things easy to accomplish tasks, focussing on what the person wants and need from the product. Accomplish this feat at the same time make it fun. There is no harm in making life enjoyable.

Outside of the 3rd World, Yahoo Buys Flickr

Once again we are back into living in the third world. It is the first day of Spring and we got a lightning storm and out goes the power. We have this to look forward to until Fall. Well, unless we move.

Once the power came on it was errand time, then time shout congratulations to Flickr and Yahoo!. The news was officially announced, that Yahoo! bought Flickr. The Flickr team is staying intact and in Vancouver. Flickr is one of the kick-ass products on the Web right now and with Yahoo! support it could stay at the forefront.

IA for the Personal InfoCloud

At the IA Summit 2005 (Montreal) I spoke on IA for the Personal InfoCloud, which seemed to go over quite well. The presentation of the slides of IA for the Personal InfoCloud (2.64MB PDF) can be downloaded. The time to present this was rather short, but I added a scenario to walk through a possible scenario that runs across environments (work, mobile, and home) with two contexts for each.

There is a lot I still have not presented on this that makes it more usable today in many environments. It is particularly helpful if you are designing across devices, building for personal management of the information, and/or designing for information use and reuse. If anybody would like me to present the full presentation and help them understand this better, please contact me (e-mail is above or use vanderwal on the gmail.com address).

I was asked about the cloud a few times. The Personal InfoCloud is the rough cloud of information that follows us as we go from place to place, this cloud keeps all the information the person wants to be kept nearby.

Dan Willis offered, not only great advice on my visuals, but replacement visuals. I will work to use these excellent replacements in the coming presentations.

Jef Raskin has Passed Away

In sadness and condolence to his family, Jef Raskin passed away. Jef was an inspiration to nearly every designer and developer, by helping us to aim to make products that were intuitive and extremely useful. It is my hope that is vision lives on in the lives and minds of all those he inspired and still inspires.

Peace.