vanderwal.net

Gone to the Roses

I am off to the Left Coast, Portland in particular, the IA Summit more particularly. Stop and say hi. I will continue my usual nonsense from the City of Roses.

Social Networks with InFlow

Steven Johnson examines Vladis Krebs' InFlow software to find social networks. This is a visualization tool that draws the lines that make up the connections in our lives and interactions. More about InFlow and information about Krebs will help you under social networking from an automated perspective.

Graphviz provides similar (yet simpler) output.

Molly wants to discuss SXSW and flow of ideas

Molly asks what one gets from SXSW? I did not make it this year as I am somewhat burried with work, reviews for a great conference in June, and preparing for Portland. I get a great amout from SXSW Interactive infact part of why I am burried is because of a confluence at SXSW last year. The Model of Attraction solution to the failure of navigation as our metaphor of building interfaces to information on the Web. I have been whittling down over 5 pages of single spaced outline on MoA for the last 6 weeks trying to fit a solid understanding of it into 30 to 45 minutes.

Much of what can make SXSW great is the bright passionate people it draws in. The inspiration and spark from SXSW can last a year. I do agree there is a need for a higher level conference as a place to think and bounce ideas around to keep the growth horomones for design, research, and technology fresh. Some of that may come and I really want to be there. This is not to say that SXSW does not offer this, it does as follow on conversations after the panels. It would be great to have these discussions as small groups or as the panels.

The Web, information use, and the failure of the spacial metaphor

Francis Cairncross' book title Death of Distance is a wonderful understanding of the world around us in many way and should now apply to spacial relationships on the Web. The idea of spacial relationships on the Web have been a stretch of the truth for a long time. Initially the idea of a person going out and "navigating" other spaces helped those new to the prospect of what the Web held grasp the Web concept.

The problem with spacial explanations of the Web is they do not work very well. The truth is we go nowhere on the Web, information is brought to us. The Web user is ego-centric and rightfully so, as the world of information and commerce on the Web revolves around the user. The Web is truly omnipresent. Information is everywhere at once. The Web can even follow the user on mobile devices. The user does not go out and explore different places, the artifacts of the places come to the user's screen based on what is of interest to the user.

I was reading David Weinberger's book Small Pieces Loosely Joined and it was painful to watch him twist and turn to get the spacial metaphor to work. A whole chapter in the book is devoted to Space [on the Web] (the book as a whole is very enjoyable and worth the time to read). Weinberger first discusses how we use the Web, using surf, browse, and go to a site. This is wrapped with an analogy explaining the Web is like a library where the user does not have access to the stacks of books, but a librarian (or clerk) goes and retrieves the book, based on the request the user made, and brings it to the user. He also states:

... this is perhaps the most significant change the Web brings to the world of documents: the Web has created a weird amalgam of documents and buildings. With normal paper documents, we read them, file them, throw them out, or sent them to someone else. We do not go to them. We don't visit them. Web documents are different. They're places on the Web. We go to them as we might go to the Washington Monument or the old Endicott Building. They're there, we're here, and if we want to see them, we've got to travel.

.... the odd thing is that, of course, we're not really going any place, and we know it.

This is just painful to follow. We keep bringing up this bloodied and battered spacial metaphor trying to make it work to explain more than the very tiny bit it did explain well. The spacial metaphor has long overstayed its welcome and it now hinders us as we try to build the future information interfaces, which include mobile information access and internationalization of information.

Yes, I am saying mobile information use is hindered by a spacial metaphor. It is more than hindered it is crippled by it. When prepare information now location is largely irrelevant, but access, device, application, and information form and highly relevant. Before we prepared information on paper and sent that information to people (which can be done today) and we largely knew how that information was going to be used. Today, with digital information the ease of information reuse and the user's ego-centric view of the information world, we must think of the user and how the information will be used. The proximity of the information to the user through access, storage, or personalization is what is paramount. Proximity is the only spacial element that has significance. This equally applies to internationalization as language and culture are the barriers to the information not space. A Brazilian may be sitting on the T in Boston and want to read the most recent information on rollout of WiFi in Rio. The user should not need to find the Brazilian neighborhood in Boston to get the information in the proper language (Portuguese) with familiar cultural inflections. The user can attract that information form easily, which can be brought to the user if that information and access have been prepared and enabled. The user may have come across a resource for this information while looking for a client's most recent press release and the user forwarded the link to her mobile device to read later. Access to information can and should be based on the users actions and choices.

The user can (and has been able to for some time) create their own metadata and retrieval structures. Communication with live people or machines that can and will convey useful information at the user's desire is not only the reality of the wired world, but what mobile use is all about. The user can set their proximity to information they have come across and connectivity conduits are enablers of that information they have yet to discover.

Up to this point the spacial metaphor only provided us with the navigation, but flat out failed us with what the user could do once they found what they were seeking. The user can browse, search, receive in e-mail (based on list subscriptions), read an information feed that brings to the user new information from sites the user likes or from aggregators, or a variety of other means. Once the user comes across information they have an interest in they want to keep that information attracted to themselves, via storage, putting it on a page that is accessible to a mobile or stationary device, and/or have the information delivered at a time that will be more convenient (getting a text message on your phone with the address and time of a party at an art gallery). Proximity also plays a role in location based services, such as bringing up restaurant listing and reviews when the GPS in our mobile device indicates we are near these establishments. The user should be able to identify favorites or preferences that can help provide "best options".

The realization of the failure of the navigation metaphor to provide for much other than a nice name for the grouped set of links that provide browsing options pushed me to investigate the Model of Attraction (MoA). The MoA is not perfect, but does provide a framework to think about information use and reuse as users currently interact with it. The MoA offers a method for us to work through how we allow the user to easily reuse information they found. The devices are just conduits for the attraction interaction to take place. MoA offers a framework that is also easy to understand, but is a literal description, which helps us see building, structuring, and preparing information and applications for the future.

Navigation -- R.I.P.

The future of UCD with attraction

Another snippet from Tanya from SXSW, this time from "Future of UCD" panel. Tanya picked out "users will not use item alone, but in a federation of devices", which is at the heart of the Model of Attraction (being presented at The IA Summit on Saturday March 22, 2003 right after the keynote). The future, which we are seeing pieces of now, gives more control to the user as to what they will do with the information and how the user wants to or will access the information. The body of research for Internet development has focussed too much time and effort on navigation (browsing is more encompassing or a term and more literal). Users not only browser for information, but search. The user is no longer constrained to a desk or building when they try to attract information they need to themselves and this difference greatly changes how we must think about providing solutions. It is long past time to retire navigations as a limiting metaphor and start working with a model that more closely represents what is literally happening. The navigation metaphor fails us as we try to encompass the future of information access, information use, and information reuse that has already begun to take hold around us.

One benefit of the Model of Attraction is that is provides a framework that includes information reuse. Many times an information application is built upon the perception that the output of the information form will be its only form. I have seen time and time again large organizations that have bought applications or built applications that only consider the initial output of information. That information form may be in a Flash movie, Acrobat PDF, PowerPoint presentation, Word document, dynamic Web site, or static HTML page (to name just a few options). What information creators do not consider is how the information will be reused. A PDF is great for printing or just reading, but pretty much fails for extracting information easily or having external pointers direct others to one piece of micro-content (a scentance, paragraph, or other delineated section). Each method of presentation of information has its own benefits and detractors. The one with the most legs is (X)HTML as is can be used on nearly all devices (desktop PCs, mobile handhelds, etc.) with little or no modifications, it is not the best medium for printing information, but if built to standards it can be easily converted and stored as the user desires. XML has the same promise, but one needs to work with a standard schema so that the information is widely useable and reusable.

Keep in mind the future is now. Our future needs metal models to help us build information applications and services for univeral usage.

Boxes and Arrows Birthday

Happy Birthday Boxes and Arrows. It is Boxes and Arrows one year anniversary. It seems like so much longer, but to some of us it has been a little longer. There have been a flood of great articles that have shared knowledge and experiences to help us all get better at what we do. I am looking foreward to the next anniversaries and looking back too.

Favorite IA Books

The NY IA Salon offers their favorite books, as captured by Mike Lee. Most of my favorites were captured, but I would have to add John Cato's User-Centered Web Design, Jesse James Garrett's The Elements of User Experience, the Second edition of the Polar Bear, and possibly Accessing and Browsing Information and Communication (on of my current reads that I am in the midst of) upon my completion of the book I may add it to my permenant IA favorites list.

There are two books I hand out to novices in the IA realm The Elements of User Experience and Christina Wodtke's Information Architecture: Blueprints for the Web. These two are easy to jump into and have a very good idea where things will be goind and why. This greatly eases the communication and understanding

Mike Lee points to a great snippet concerning dumb people with too much energy, which is from Mike's favorite Make it Bigger.

Information Accessing and Browsing book

I am really enjoying Accessing and Browsing Information and Communication by Rice, McReadie, and Chang from MIT Press. I am less than 100 pages into this academic review and assessment of how people approach, find, assess, and retain information. The book is wonderful as it takes an cross section of academic disciplines and the research from them on browsing information and information use. The book is uncovering new pools of information in the library sciences, organizational communication, and knowledge management fields that help one better understand how people find and process information. There is a lot of information that is echoing the Model of Attraction approach to user and information relationships as well as helping to better refine the approach (there are some updates to the MoA that I have clarified in the last three weeks, and this reading is helping gell).

I may write a full review when I finish the book. I am reading the book on the train to and from work at the moment. I may need to read at home so I can check information that is being referenced.

WaSP Buzzing

The current Buzz is that the Web Standards Project is growing and offering a new perspective and as is noted in the WaSP press release I am now a member of the WaSP clan. This takes advantage of what I already do in my free time, try to build a better Web and work on structuring information for use and reuse. This is smart group dovetails very nicely with the smart group of information architects that absorb another chunk of my free time.

Understanding Referrer Systems

Rashmi Sinha's Recommender Systems overview on Sig-IA is a great overview of the tools used to bring information closer to those that may have an interest in that information. Essentially this gets to the heart of the Model of Attraction. Recommender Systems can provide tools that group information through links that are based on others similar interests. Finding information is what many spend much time doing. Lessening this time and providing methods to predict interests are helpful. This of course takes patterns. Patterns need a breadth of data to be useable.

In particular you may be interested in Rashmi Sinha's "Interaction Design for Recommender Systems". [hat tip Matt]

Information Design the meta discipline for business

Information Design: the meta discipline for business. [hat tip InfoDesign]

Build your ideal creative team and other articles

Boxes and Arrows serves up three great articles right now. George Olsen shares his R&D (Relevant & Desirable article discussing the need for vision driven design in user-centered design. Scott McDaniel offers up What's Your Idea of a Mental Model?. My favorite of this current bunch is Erin Malone's Modeling the Creative Organization in which Erin walks through how to put together her idea of an ideal creative team. Her discussion is provides insight into a great approach.

Content management interview with Bob Bioko

Elearningpost interviews CMS wiz Bob Bioko. The article has an e-learning bent to it, but it is a great interview discussing content management. I really enjoy Bob's approach as it separates information from technology and stresses the importance of understanding the information and its needs prior to digging into the technology. This is brought out in this quote from the interview:

Firstly, technology changes a lot and focusing on technology is not the right thing to do. What's really important to me is figuring out what exactly you want from your learning system or information system. From my point of view, I have certain information resources that I would like to deliver to certain people in a certain way. That's not a technology question. That's not about what system I have. Rather its about what information do I have, who wants it and how do I deliver that information in the best possible way. Now obviously I would need a system to do that, but the infrastructure follows from the need I have, not the other way around.

When someone makes the decision the other way around, focusing on the platform, the software, the features etc., they limit and constrain themselves to what the system allows them to do. This is not to say that technology wont be a determining factor in what you actually have to, its just that technology should be a response to the problem not a definer of the problem.

Two other bon mots in this article include discussions of "context management" and the perenial question of "build versus buy".

Moblogging and Joe Average persona

The Online Journalism review offers up Moblogging the next big thing, which brings "Joe Average" into play. I am not sure Joe Average would want a Hiptop or find a use for a Hiptop. I do like the idea of the Smartmobs, but it is not for everybody.

In a discussion at the DC IA book reading group (this time it was The Tipping Point) we ventured on the topic of using mavens as a persona candidate. The person said they were looking for somebody less adept at finding information, like a "Joe Average". This is often how many of us build personas we go for the less adept, or make sure they are represented across our personas. The discussion later came to how to keep the mavens intrigued, which is also a valid discussion.

Fusebox FLiP's for user centered design approach

While going through the Fusebox application development site (a coding framework for ColdFusion, J2EE, PHP, and ASP that helps separate coding from presenation by building reusable components and templates) I stumbled upon FLiP. The Fusebox Lifecycle Process (FLiP) section focusses on application development and project management "best practices". FLiP the steps are Personas and Goals, Wireframe, Prototype / Front-End Development, Application Architecting, FuseCoding, Unit Testing, Application Integration, and Deployment.

I was so happy to see personas, wireframing, prototyping, and application architecting as well as the suggested order. This is the path I have found to provide the best path for success. I was introduced to this process in the very early 1990s when working on a project to replace a mainframe application and moving it to the PC. The approach seemed solid and achieved some quick results with few hiccups. That approach has stayed with me and the focus on the user being the extremely important. Application developers often want to jump right into the coding and interface designers want to start crafting the visual design. Doing either with out proper understanding can easily lead to complications that are costly to correct.

The field of information architecture structures its approach to development on these tasks and roles. A great overview for application development is wonderfully laid out in Jesse James Garrett's The Elements of User Experience. Many that build applications have become familiar with these steps. Those wanting to learn programming and application development have found this the user-centered design approach is a great preparation. Why? Once the users are defined, the information structure defined, the interaction elements outlined, the interface outlined, and the framework for the application decided upon the coding becomes easy to focus upon. The coding portion of development becomes much easier because the interactions for the users are defined and the coding solutions are largely pre-defined.