vanderwal.net

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.

Removing the Stench from Mobile Information

Standing in Amsterdam in front of the Dam, I was taking in the remnants of a memorial to Theodore van Gogh (including poetry to Theo). While absorbing what was in front of me, I had a couple people ask me what the flowers and sayings were about. I roughly explained the street murder of Theo van Gogh.

While I was at the Design Engaged conference listening to presentations about mobile information and location-based information I thought a lot about the moment at the Dam. I thought about adding information to the Dam in an electronic means. If one were standing at the Dam you could get a history of the Dam placed by the City of Amsterdam or a historical society. You could get a timeline of memorials and major events at the Dam. You could also get every human annotation.

Would we want every annotation? That question kept running reoccurring and still does. How would one dig through all the digital markings? The scent of information could become the "stench of information" very quickly. Would all messages even be friendly, would they contain viruses? Locations would need their own Google search to find the relevant pieces of information. This would all be done on a mobile phone, those lovely creatures with their still developing processors.

As we move to a world where we can access information by location and in some cases access the information by short range radio signals or touching our devices there needs to be an easy to accept these messages. The messaging needs some predictive understanding on our mobiles or some preparsing of content and messaging done remotely (more on remote access farther down).

If was are going to have some patterning tools built in our mobiles what information would they need to base predictions? It seems the pieces that could make it work are based on trust, value, context, where, time, action, and message pattern. Some of this predictive nature will need some processing power on the mobile or a connection to a service that can provide the muscle to predict based on the following metadata assets of the message.

Trust is based on who left the message and whether you know this person or not. If the person is known do you trust them? This could need an ensured name identification, which could be mobile number, their tagging name crossed with some sort of key that proves the identity, or some combination of known and secure metadata items. It would also be good to have a means to identify the contributor as the (or an) official maintainer of the location (a museum curator annotating galleries in a large museum is one instance). Some trusted social tool could do some predicting of the person's worthiness to us also. The social tools would have to be better than most of today's variants of social networking tools as they do not have the capability for us to have a close friend, but not really like or trust their circle(s) of friends. It would be a good first pass to go through our own list of trusted people and accept a message left by any one of these people. Based on our liking or disliking of the message a rating would be associated with this person to be used over time.

Value is a measure of the worthiness of the information, normally based on the source of the message. Should the person who left the message have a high ranking of content value it could be predicted that the message before us is of high value. If these are message that have been reviews of restaurants and we have liked RacerX previous reviews we found in five other cities and they just gave the restaurant we are in front of a solid review that meets our interests. Does RacerX have all the same interests?

Context is a difficult predictive pattern as there are many contextual elements such as mood, weather, what the information relates to (restaurant reviews, movie reviews, tour recommendations, etc.). Can we set our mood and the weather when predicting our interest in a message. Is our mood always the same in certain locations?

Where we are is more important than location. Yes, do we know where we are? Are we lost? Are we comfortable where we are? These are important questions that may help be a predictor that are somewhat based on our location. Or location is the physical space we occupy, but how we feel about that spot or what is around us at that spot may trigger our desire to not accept a location-based message. Some of us feel very comfortable and grounded in any Chinatown anywhere around the globe and we seek them out in any new city. Knowing that we are in or bordering on a red-light district may trigger a predictive nature that would turn off all location-based messages. Again these are all personal to us and our preferences. Do our preferences stay constant over time?

Time has two variables on two planes. The first plane is our own time variables while the other relates to the time of the messages. One variable is the current moment and the other is historical time series. The current moment may be important to us if it is early morning and we enjoy exploring in the early morning and want to receive information that will augment our explorative nature. Current messages may be more important than historical messages to us. The other variable of historical time and how we treat the past. Some of us want all of our information to be of equal value, while others will want the most current decisions to have a stronger weight so that new events can keep information flowing that is most attune to our current interests and desires. We may have received a virus from one of our recent messages and want to change our patterns of acceptance to reflect our new cautionary nature. We may want to limit how far back we want to read messages.

Action is a very important variable to follow when the possibility of malicious code can damage our mobile or the information we have stored in the mobile or associated with that mobile. Is the item we are about to receive trigger some action on our device or is is a static docile message. Do we want to load active messages into a sandbox on our mobile so the could not infect anything else? Or, do we want to accept the active messages if they meet certain other criteria.

Lastly, message pattern involved the actual content of the message and would predict if we would want to read the information if it is identical or similar to other messages, think attention.xml. If the Dam has 350 messages similar to "I am standing at the Dam" I think we may want to limit that to ones that meet some other criteria or to just one, if we had the option. Do we have predictors that are based on the language patterns in messages? Does our circle of trusted message writers always have the same spellings for certain wordz?

All of these variables could lead to a tight predictive pattern that eases the information that we access. The big question is how is all of this built into a predictive system that works for us the moment we get our mobile device and start using the predictive services? Do we have a questionnaire we fill out that creates our initial settings? Will new phones have ranking buttons for messages and calls (nice to rank calls we received so that our mobile would put certain calls directly into voice mail) so it is an easier interface to set our preferences and patterns.

Getting back to remote access to location-based information seems, for me, to provide some excellent benefits. There are two benefits I see related to setting our predictive patterns. The first is remote access to information could be done through a more interactive device than our mobile. Reading and ranking information from a desktop on a network or a laptop on WiFi could allow us to get through more information more quickly. The second benefit is helping us plan and learn from the location-based information prior to our going to that location so we could absorb the surroundings, like a museum or important architecture, with minimal local interaction with the information. Just think if we could have had our predictive service parse through 350 messages that are located at the Dam and we previews the messages remotely and flagged four that could have interest to us while we are standing at the Dam. That could be the sweet smell of information.

Personal Mobile Usage Pattern

One of the things that bubbled up while using a phone other than my usual phone on my trip to Amsterdam was my normal use patterns. I use my mobile phone (Palm Treo) not only to communicate with others, but also to communicate with myself.

I often send myself e-mails with ideas for projects or articles. I also send e-mails to myself on things to spend time thinking about later or to research later. I had one of these moments in talking with Peter Bogaards about Paul Otlet, whom I have problems remembering. I started reaching for my tool to send a note and had a different phone, which took a little more effort, but got the job done.

I also SMS myself with the cross streets of where I parked my car, or what garage level and other metadata. This solves an ongoing problem, particularly in Georgetown, where my normal parking patterns are ousted, I am parking in a completely new location, or parking in long term at an airport. All part of my mind occasionally not being on the task at hand or I am just deep in thought and did not make a conscious effort to remember where I parked.

One other usage I have is taking a photo of my radio display in my car or the song name and performer. This mostly happens when listening to XM Radio (satellite) as the options are broad and deep, which works wonders for coming across new music I like. The radio in my car does not have a means to save the song name, or even better would be to e-mail me the song info, a link to listen to a snippet, and buying information. I resort to the tools at hand. Yes, I only (well usually) take photos while stopped. I usually have 5 to 10 photos of my radio on my mobile at any one time. It makes it handy when I go into a music store or wait until I can put it in a wishlist online. I use my Amazon Wishlist to find items of interest in a store or to add to my Wishlist and having that live access has made things far better for me as a consumer (my only desire is to have a better mobile interface to one's own Wishlist on a mobile it would seem to have immense benefits for Amazon).

I also browse the web and read articles that I save down to my device to I have access in no-signal zones or zones that I do not have MMS or web access and just phone (DC METRO while underground). I often save down Boxes and Arrows articles for such trips. I also push articles and presentations I am working on to my mobile as back up as well as for review in down periods.

How do you use your mobile?

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.

The User's Mind and Novelty

My commute-time reading of Steven Berlin Johnson's book, Mind Wide Open included the discussion of attention today, toward the end of Chapter 5, as Steven pointed out that Dopamine regulates the "novelty-seeking" axis. I began to think about MTV, Web development, advertising, and other entertainments. It seems much of the creative force in entertainment and design is aimed at triggering the novelty-seeking part of our brain to draw attention. I throw Web development in there as there is a desire for over decorating and using cool Flash (I love Flash, but it is often used as a container for content, which inhibits the easy consumption of the information) where it is not best used.

This also reminded me of a rough theory about executives and content owners and their understanding of Web design. The content owners and managers that get involved with their Web development want exciting and flashy sites developed because they are bored with their content. They have been working with their content for years and it is not interesting to themselves any longer, in short it is work not fun and the Web is fun. There seems to be a correlation to the formality of the content and the desire for Flash and over-the-top visual design. The finance and budget people want a banker lamp with words moving out of them. The legal department wants highly-graphic backgrounds for their text.

The cure for this injection of excitement is turning the focus to the users of the content, that are not bored with the information and need to find the information and are often craving the information. Focussing the content owner on how to make the words that are important and the text of desired information easy to consume helps turn the situation from decoration that distracts the user. The next step is to user test and show the roadblock, if not worse, that stands between the user and their desired information.

In terms of "novelty-seeking" for the users, their desired information is often the novelty. On information sites the users what to come and get what they want easily and quickly. Providing clarity to help the user get that which they need is the best service. The design should not be boring, but should be well though out to help direct the user's attention to what will help them the most. Information design skills and a solid understanding of how to use the medium well will benefit the user greatly as it will the content owners.

Malcolm McCullough Lays a Great Foundation with Digital Ground

Today I finished reading the Malcolm McCullough book, Digital Ground. This was one of the most readable books on interaction design by way of examining the impact of pervasive computing on people and places. McCullough is an architect by training and does an excellent job using the architecture role in design and development of the end product.

The following quote in the preface frames the remainder of the book very well:

My claims about architecture are indirect because the design challenge of pervasive computing is more directly a question of interaction design. This growing field studies how people deal with technology - and how people deal with each other, through technology. As a consequence of pervasive computing, interaction design is poised to become one of the main liberal arts of the twenty-first century. I wrote this book because I ran into many people who believe that. If you share this belief, or if you just wonder what interaction design is in the first place, you may find some substance here in this book.

This book was not only interesting to me it was one of the best interaction books I have read. I personally found it better than the Cooper books, only for the reason McCullough gets into mobile and pervasive computing and how that changes interaction design. Including these current interaction modes the role of interaction design changes quite a bit from preparing an interface that is a transaction done solely on a desktop or laptop, to one that must encompass portability and remote usage and the various social implications. I have a lot of frustration with flash-based sites that are only designed for the desktop and are completely worthless on a handheld, which is often where the information is more helpful to me.

McCullough brings in "place" to help frame the differing uses for information and the interaction design that is needed. McCullough includes home and work as the usual first and second places, as well as the third place, which is the social environment. McCullough then brings in a fourth place, "Travel and Transit", which is where many Americans find themselves for an hour or so each day. How do people interact with news, advertisements, directions, entertainment, etc. in this place? How does interaction design change for this fourth place, as many digital information resources seem to think about this mode when designing their sites or applications.

Not only was the main content of Digital Ground informative and well though out, but the end notes are fantastic. The notes and annotations could be a stand alone work of their own, albeit slightly incongruous.

Project Oxygen Still Alive

Project Oxygen has progressed quite well since we last looked in (Oxygen and Portolano - November 2001). Project Oxygen is a pervasive computing system that is enabled through handhelds. The system has the users information and media follow them on their network and uses hardware (video, speakers, computers, etc.) nearest the user to perform the needed or desired tasks. Project Oxygen also assists communication by setting the language of the voicemail to match the caller's known language. The site includes videos and many details.

Project Oxygen seems to rely on the local network's infrastructure rather than the person's own device. This creates a mix of Personal Info Cloud by using the personal device, but relies on the Local Info Cloud using the local network to extract information. The network also assists to find hardware and external media, but the user does not seem to have control over the information they have found. The user's own organization of the information is important for them so it is associated and categorized in a manner that is easy for them to recall and then reuse. When the user drifts away from the local network is their access to the information lost?

This project does seem to get an incredible amount of pervasive computing right. It would be great to work in an environment that was Project Oxygen enabled.

Tanya on Virtual Teams

Tanya offers up a wonderful brief discussion of virtual teams. This is a topic I really enjoy (I have products that I greatly favor (Groove and AIM/iChat) as it really helps productivity, but also the documentation process.

Tog explains good design on bad products

Bruce 'Tog' Tognozzini writes When Good Design is => a Bad Product.

You take a mediocre product and rework the design to make it better. Your design is a success, by any reasonable measure, but the resulting new release is actually worse. You redouble your efforts and matters become untenable. It doesnít matter how brilliant and effective your designs, the more they improve the product, the less usable the product becomes.

The article is filled with wonderful illustrations that will help us better understand how to make better products.

Guide to Ethnography Wiki Lives

Peter Van Dijck relaunched Guide to Ethnography Wiki. This is a very good resource for understanding ethnographic studies and research.

Information structure important for information reuse

John Udell's discussion of Apple's Knowledge Navigator is a wonderful overview of a Personal Information Cloud. If the tools was more mobile or was shown synching with a similar mobile device to have the "knowledge" with the user at all time it is would be a perfect representation.

Information in a Personal Information Cloud is not only what the user wants to have stored for retrieval when it is needed (role-based information and contextual) but portable and always accessible. Having tools that allow the user to capture, categorize, and have attracted to the user so it is always with them is only one part of the equation. The other component is having information that is capable of being captured and reused. Standards structures for information, like (X)HTML and XML are the beginnings of reusable information. These structures must be open to ensure ease of access and reuse in proper context. Information stored in graphics, proprietary software, and proprietary file formats greatly hinders the initial usefulness of the information as it can be in accessible, but it even more greatly hinders the information's reuse.

These principle are not only part of the Personal Information Cloud along with the Model of Attraction, but also contextual design, information architecture, information design, and application development.

RSS on PDAs and information reuse

Three times the past week I have run across folks mentioning Hand/RSS for Palm. This seems to fill the hole that AvantGo does not completely fill. Many of the information resources I find to be helpful/insightful have RSS feeds, but do not have a "mobile" version (more importantly the content is not made with standard (X)HTML validating markup with a malleable page layout that will work for desktop/laptop web browsers and smaller mobile screens).

I currently pull to scan then read content from 125 RSS feeds. Having these some of these feeds pulled and stored in my PDA would be a great help.

Another idea I have been playing with is to pull and convert RSS feeds for mobile browser access and use. This can be readily done with PHP. It seems that MobileRSS already does something like this.

Content, make that information in general, stored and presented in a format that is only usable in one device type or application is very short sighted. Information should be reusable to be more useful. Users copy and paste information into documents, todo lists, calendars, PDAs, e-mail, weblogs, text searchable data stores (databases, XML respositories, etc.), etc. Digital information from the early creation was about reusing the information. Putting text only in a graphic is foolish (AIGA websites need to learn this lesson) as is locking the information in a proprietary application or proprietary format.

The whole of the Personal Information Cloud, the rough cloud of information that the user has chosen to follow them so that it is available when they need that information is only usable if information is in an open format.

iSociety - Mobile Phones and Everyday Life

iSociety Mobile Phones and Everyday Life, is a report looks at the impact of mobile devices as they impact everyday life. Looking at how we work with mobile devices today will help us set a framework for the future.

CompUSA no sale

Need to have an example of not thinking through all the steps when building a Web application? Macwhiz tries to buy a monitor with good money, but bad application does not allow it. Having the credit from CompUSA on a CompUSA card and using to buy from CompUSA does not mean a thing. The buyer wanted it delivered to his office (always a logical option), but had his home address listed on the credit card (another logical option). CompUSA needed him to add his office address to the card (another logical option), but does not offer any mechanism to doing so (somebody will get fired).

When building applications there needs to be processes put into place to handle the needed options. Many times this requires a phone call to people trained in customer service. Not understanding processes before building an application or have ALL parties talking while developing an application will save embarrassment.

You should never start building before drawing a blueprint that takes into account all the options and needs. There is too much experience around to really have this happen with out a conscious decision being made (usually up the food chain) that stopped the options from being developed (if this is not the case they have the wrong developers or not enough time to have the processes worked out). These reasons are very close to why I will never buy from Barnes and Noble on line again. Ever.

Opening an application to the Internet opens the application to real people and real people provide a wide variety of aberrations to the planned uses for any application. Not having the time, resources, or approval to build in processes for easily handling these aberrations or spending time developing the application using user centered design/development skills will sink even the best funded applications. The user is always right and the real users must be a part of the development.

I think a note of clarification is needed regarding the frames comments from the other day. I am a huge fan of the Content Management Bible and have been perusing it for a couple months (or so) now. The use of frames is not all bad, if used in a proper context.

One reason to use frames is using the browser client as an application interface and there are distinct sections with quasi-interrelated functionality. A mapping application (select any one of these elements on the page to see the use of frames - keep in mind there is a heavy use of JavaScript that requires a version 4.5 browser or higher). The application interface often has command elements that are essentially toolbars and definition selection elements that set the metadata layers of the information to be displayed. These toolbars direct the actions of the other frames or provide tools to be used in other frames (a zoom tool, etc.). The functionality in a toolbar is not an element of the map display and it should not be an incorporated element of the map as it has a much different functionality from the map display. Conversely, our users are familiar with navigation being incorporated into the Webpage and that is now a common and preferred construct. But, we are looking at an application being displayed in a Web browser, which requires a different mind set.

Another use of frames is in a controlled environment that has a plethora of distinct content items that are within a contiguous text, such as an extensive table of contents. Here the Metatorial CM Bible is a good example of when to use frames. There table of contents is a helpful information tool to quickly scan through the information to place the reader at distinct point in a larger body of text. The table of contents is a large (long) element of text that could work as an element is one distinct page, but that would require rebuilding those elements of the page with every snippet of information delivered to the browser.

Frames should be used when the distinct content elements require each other. The table of contents and the page display elements should not work with out the other components (if they can we really have to ask ourselves why we are using frames). If we can enter a page in the CM Bible without the table of contents the functionality of the site is broken. The navigation is not available and the assistive information (navigation and/or metadata elements) is not available.

The last item is to ensure that if a frame can stand alone as its own page, please ensure there are the needed navigational elements on the page. In the example that drove my frames rant (largely because the CM folks understand information and its need to be used, but the site breaks information use constructs we know from experience and research to be proper and needed) the thing that was disconcerting was each of the frame elements needed the other to provide complete information for the user. The user needs context. We need to provide the user a means to get to our front page or to other areas within our sites, because if they like our information we should offer them more. If we build a site using framed elements and these elements can be used on their own (no JavaScript sniffers to ensure the other frames are open as a requirement for displaying the content, or other similar technique) the content must have navigation elements (the footer is an unobtrusive placement) and really should have some branding or other statement of ownership.

We know that users of information have varied purposes and methods of using our information. We need to provide the users the tools to help the user provide this information. We are often proud of our information work, but if a user does not know it is us or we do not want to claim our work is decreases credibility.

We need to embrace functional information architecture to ensure proper information use. This bleeds in to user experience design, but understanding how information is used and the information interface is used must be integrated into the IA. Proper functional IA should keep improper use of frames from occurring. Functional IA would walk through a string of questions using a wireframe of a site and ask how the frame sections would interact. We would ask what information is lost if not all the frames function (a surprisingly common occurrence). We would ask if frames maintain context for the information. We would look at methods of insuring the whole of the frames remains so to provide proper navigation, proper context, and proper metadata to help understand the information provided. Not asking these questions is not being responsible to the information, those that collected the metadata and spent time understanding how the information is to be used, and is not responsible to the consumers of the information.