Thoughts on successfully implementing UI/UX standards

Developing brand compatible UX/UI standards is relatively simple. Successfully implementing them is not.

First, it is important to distinguish between UI and UX. UI consists of the visual elements of an interface. Colors, shapes, icons, fonts, etc. Creating standards for the UI from brand standards is trivial.

Thoughtful UX design has two tiers of complexity. The easy tier is very similar to UI, and consists of reusable interaction metaphors. Things like the navigation and the styling of widgets like select/drop downs, tabs, accordion panels, tables, pagination, etc., elements generally found in widget libraries like JQuery or Bootstrap.

This level of UX and UI can be easily distilled into a set of design standards and patterns so that product teams have a visual reference for updating current products and guiding development of new products.  At the very least the end user will not have a disruptive and jarring experience when going from product to product. There are challenges here - the design standards will need to offer compromises based on limitations of legacy products. For example, while products today are built to be “responsive,” so they adapt to difference screen sizes, older products may have fixed width tables that cannot be easily made responsive, or may be native applications with completely fixed layouts. So the goal should be to have standards that allow for compromise, accept mediocrity when one must (but document, track and prioritize fixes), while painting a vision for the future.

The more challenging tier of UX is how the system guides the user through a variable flow and produces the desired outcome, in a way that causes the least distress to the end user (and perhaps even “delights" them, but that is a rare occurrence and mostly lives in the minds of sales executives) and provides the desired value to the enterprise. The solution here is implementing a robust design methodology that requires a full and detailed comprehension of the problem being solved by the software system. This is not so much a standard as a practice, and often requires cultural change.

Which leads to the challenge of implementing UX standards and practices. When product teams are distributed, they tend to develop distinct sensibilities and characteristics, a result of things like remote management style, local management style, employee longevity/turnover, team competency, end user understanding/access, hardware and software skills required/preferred, the overall organizational culture and the local culture.

For example, some product teams can be insular and highly defensive of their product. Developers can be reluctant to implement even the simplest of javascript widgets if they have not done so before, and they will push back with excuses. Strong leadership (and technical knowledge) is required to prod these folks to execute to the standards. On the other hand, there are many hidden gems in product teams whose creativity is dormant and who yearn to implement techniques and designs they see being created by online peers or that they encounter everyday in mobile apps and want to do the same. Of course, many product teams are highly collaborative and will embrace anything that makes their product better — which creates another problem in that you have to manage the constant refactoring.

And that is just UX/UI design standards. A UX design methodology is much harder to operationalize, and needs to be driven top down to be successful. Since the methodology should require full understanding of the problem being solved, the processes captured and modeled need to come from facilitation with and direct observation of actual end users (anecdotal and third party observations can be woefully inaccurate, and even direct feedback may not be truthful based on the perceived seniority of the questioner).  So now you need to not only engage with the product teams, but customer support and sales as well, which adds greater risk, particularly depending on the nature and state of customer relationships. Often in enterprise software, the folks who approve the acquisition of technology for a particular purpose may use very little of the system themselves, or not at all. And frequent users who had little or no say in a system that has been imposed on them must suffer the burden of using something that perhaps was not the optimal solution it was sold as. Meaning, sales and customer service often hear very different kinds of feedback on UX and UI issues, and direct observation/questioning is the best way to understand how to refine and improve functionality and experience.

Bottom line, developing UX/UI standards are easy. Assess the products, incorporate brand elements, done. The hard part? Assessing and understanding the unique culture of each product team then developing an implementation strategy/plan (Inspire? Incent? Replace? Cajole?) to get them on board. And the key to success? Strong, strong, management support.

All purpose business graphic

Free clip art!  Download the SVG file of this image here and you can have fun all day building Powerpoint decks. Just add labels!

Visualization for prioritizing product development

A suggested approach for mobile tooltips

Perfect autosave

One of the challenges in mobile design is informing the user something has happened -- a form has been submitted or field update saved. The boring and accepted way to do this is a popup window that says "You just did something!" And if your developers are over thirty, they probably will insist on putting a confirmation button to dismiss the window. Under 30, they probably have the window fade after a second or two, or when you tap out of it. Without this, the change might be subtle enough that you are unsure what if anything just happened, and depending on connectivity, the ubiquitous loading animation may flash too quickly to do little more than add to the confusion. And don't forget by adding text to a confirmation window you are creating another language/data element to worry about when you decide its time to go multi-lingual.

So I would like to give this to the world, the perfect autosave image.

Take it, use it, enjoy it.  Me? I use it when a user updates via select/dropdown, or clicks into a field, makes a change, then clicks out -- the image fades in then out a second later. And as a bonus, I add this sound effect which reinforces that something has indeed occurred.

Enjoy!

Finally found my blog password!

Yeah, so it's been a few years since I posted anything. This does not mean I have not had any opinions or thoughts worth sharing, only that I kept trying to cram them into 140 characters (or less) --  with questionable results.

Anyway, been doing a lot of thinking about UX and mobile in particular, have been working in Angular.js, Node.js, Sass and vector images, and done some things and thought of some things that may be useful to others.

Stay tuned!

The age of brand functionality?

The web should have been the death of the brand.

The web was measurable and rich with meaning, meaning that could be extracted and associated with tangible goods and services (Planting a garden? Buy a shovel now!).  Things that are less tangible, whose only unique differentiator is brand identity itself, should have faded away.  It should have been the rebirth of advertising, providing information on differentiators and attributes so consumers could make informed decisions on the product or service that was just right for them.

But brand advertisers were tenacious, and were used to aggressively spending without measurable results. They tried their best to exploit the web.  They created sites with games, sites that entertained, and while they and their ad agencies won many awards,  ultimately a brown fizzy liquid is just a brown fizzy liquid. And really, there's just not much more to say about it. While one can create a perception of value in more traditional, less data-oriented media, it is much, much harder in an information-rich environment.

Then social networks came along and saved the brand.  Like chugging a fizzy brown liquid, social media is, at its best, immediate and fleeting. While it rarely provides value in revisiting (and more often than not embarrassing in retrospect, though the facebook timeline feature may prove me wrong -- or right), there is a persistent, nagging longing for more.  Thus the challenge for brand advertisers is that they must maintain a constant presence in and around these networks, ready to exploit those brief, fleeting moments when they are #mentioned.

There is another way. What if brands built and delivered web-based functionality that made their customers' lives easier, better and more efficient? Functionality that reinforced brand expertise and unique selling propositions? For example, what if realtors, who expend enormous amounts of effort and money to endear themselves to neighborhoods and communities, instead built a website to support community interactions (calendar, bulletin board, directory, etc.) and gave it away free?

The challenge, of course, is when trying to make people's lives easier, intrusions (er, advertising) can greatly diminish the offering and experience.  Sure, the real estate company's name would be omnipresent but it would have to be non-aggressive and of less visual weight than the functions that attracted folks to the site in the first place. Of course, tasteful and subtle are not necessarily popular notions in branding, but in the long run, delivering functionality that improves your customers' lives will pay far greater returns and be a much better investment than spending on social media buys.

Google PageRank - innovation, albatross or just plain evil?

One issue not addressed in the recent New York Times article on Google SEO woes is whether or not PageRank is simply no longer credible or useful. Sure, when it was first introduced it provided an additional dimension to refine search results beyond keyword density, but back then sites only linked to other sites because they had meaningful or relevant information.

There was simply no other reason for linking.

PageRank provided that reason -- and single-handedly created the SEO industry (though the abundance of marketing folks that popped up during the bubble had to find something to do for a living, at least until Facebook and Twitter came along), resulting in the never ending game of one-upmanship between Google geniuses and SEO hacks.

So here's the really interesting question -- if PageRank went away, would search results become better or worse? Would diminishing the impact of the massive quantity of link and content farms allow for organic, useful content to percolate to the top like the good old days?

I think the answer is yes, particularly if the holy grail of search, the search box, were improved to help searchers write better queries.  No matter how smart search algorithms may be, the better the query, the better and fewer the results.

Another issue, beyond whether or not PageRank is still useful in improving search results, is whether or not it is actually becoming dangerous and detrimental to intellectual discourse and society as a whole. PageRank encourages the promotion of new and frequently linked content regardless of how credible the source may be (such as the non-existent link between autism and vaccines) so it will continually rank high, while older, more credible content on the same subject (but less linked to by blogs, media, etc.) gets pushed down far enough to where no one will ever bother to find it.

The result? The self-perpetuation of ignorance. That's sure evil in my book.

Are social networks driving the rebirth of the handwritten note?

I think social networks have begun to influence the offline, er, real world.

How?  Well, it may be highly anecdotal, but I have noticed a dramatic increase in notes on car windshields. One could suggest it is the holiday season what with people sharing good tidings and all, but the notes I have seen are not of the particularly friendly sort.  Here's my thinking -- as more and more people feel empowered that their opinion actually matters and must be shared, that swelling of conviction can no longer be contained within the boundaries of the Twitter or the Facebook. So wherever a social injustice may occur (or one simply has an opinion on something) people now feel they have the right -- nay the obligation -- to express their outrage. Perhaps someone could come up with a line of notepads that express generic observations, and all the user (er, person) will have to do is fill in a blank or two to contribute their thoughts and feelings.  Now that's the offline equivalent of Facebook...

And by the way, to the person who left a note on my car claiming I blocked them in, next time don't pull thru and park your SUV in front of a pile of debris, leaving a legit parking space behind you. If I only had a notepad and a time machine...

Must a user experience be "positive?"

User experience is an important dimension of software development, but it is not the entire thing. 

Sure, a "positive" user experience can increase adoption, but if the business requires things to occur in a precise way at a precise time, then the software has to enforce that, even if it means incorporating unpleasant and unnatural methods to ensure it happens exactly the way it must. 

Accomplishing this means you need to be agile in your thinking, able to see connections and intersections in new and different ways, and not be constrained by conventional thinking.

Understanding business process can create a better user experience

Software consumes, transforms and presents information. It is utterly about communication. And consumption, or capture of information, depending on the business activity supported, may be of far greater importance than how the information is represented. This is particularly true if unstructured data is feeding into the system.

As I discussed in my previous post, information simply does not have the physical or conceptual limitations of a cup holder or door knob. Thus, information design is not just about the presentation or graphical layer, but the structure as well -- data modeling, information architecture and perhaps, most important (in my experience, anyway), business process modeling, so that you have a detailed and granular understanding of the processes the user must go thru in performing a set of tasks that intersect with the software system. Process modeling helps better design the interactions and hand-offs with touch points within and outside of the system. It also helps understand the information types required, the actors involved, the constraints required by the system and the organization, additional systems or tools that are necessary, and the inputs and outputs that drive the user through to completion. 

Bottom line, the better you can understand the business and its requirements, the better and more meaningful experience you can create.

What defines a user experience practitioner?

There has been an ongoing LinkedIn thread in the User Experience (UX) group regarding just what defines a user experience practitioner. This is something that I have noodled as well as I have tried to determine what my last decade as a software entrepreneur has turned me into (professionally, at least). Of the many hats I have worn, ideation, prototyping, interaction and interface design and user testing has been the most interesting and personally satisfying, but does that make me a UX expert?  The LinkedIn thread leads me to believe there are two distinct groups, the traditional practitioners who come from industrial design, architecture, etc., and digital practitioners, who are more visually inclined. Certainly I am more of the latter, tho with a strong foundation in marketing fundamentals and keen knowledge of business process methods, both of which I think are additional strengths for effective digital UX design.

Anyway, I thought I'd share my recent contribution to the conversation as it describes a key notion of mine regarding software design and user interaction, which is the ability to achieve greater clarity of purpose by freeing yourself from constraints and rules:

"I have been following this conversation for some time, and I think a key distinction between these two UX camps is that one is governed by immutable rules, and the other is not.  User experience in the real world, as defined by architects, industrial designers, etc., is constrained by reality -- things like gravity, friction, mass, and so on.  The digital user experience is constrained by none of these things. In fact I would make the case that the more the real world intrudes on the digital experience, the more it is potentially diminished. Just because a physical object is known for a specific purpose does not necessarily make it the best metaphor to represent a vaguely similar action.

And as much as I respect the deep training UX demands in the real world, perhaps that same training, when applied to a primarily visual experience, is detrimental when it comes with so much psychological and creative baggage. Artists, on the other hand, excel at imagining possibilities without constraint. The beauty of the web and web toolsets are that they provide an easy way for artists to realize their ideas without making too many compromises. This is not to say anything should go, but it is always easier to scale back big ideas than to take a small idea and make it more than it is.

Certainly a balance of both skill sets would be optimal, but moving quickly and being good enough for the medium is going to win most of the time."

The era of the perpetual job seeker?

Over the last several decades, the level of trust between employee and employer has corroded.  While there are many causes for this decline, the bottom line is most employers no longer hesitate to slash employees, and most employees do not hesitate to jump ship for better opportunities. And each party is fully aware of the other's intent.

So what does this mean for average Joes like you and me?

It means that your employer is going to continually look for new and exciting ways to squeeze productivity out of you (more on this to come soon).

And it means you are going to have to change from the traditional passive model of "job hunting when necessity strikes" to being ever vigilant and alert for new opportunities.

First, the easy part -- get your personal "brand" polished and ready to go at a moment's notice. At the moment, LinkedIn seems the be the primary mechanism to do this, tho other social media matter as well.  Whether you use Facebook or Twitter or some other site, these social media outlets need to collectively communicate your strengths, and hopefully few of your weaknesses.

Second, you need to find ways to always be on the lookout for that next gig. This is the real challenge -- traditional job posting web sites like Monster or Careerbuilder are tiresome to wade thru, as is Craigslist (which seems to be on the wane from its glory days as a job site) and newspaper sites. LinkedIn appears to have the lead here, but other than using your network to suggest connections, technologically it is not particularly interesting.

Jobfox is little more interesting in their approach. Sure, they have job postings as well, but you use your resume to build a profile on which the site performs an automated categorization of your skills.  This enables Jobfox to recommend jobs that you might not find on your own as the title, keywords, or details may be different from the kind of job you would normally search for. Of course, when you automate categorization it is rarely 100% (for example, my profile came back with Linux, which was not on my resume, as a skill -- and while I can fat finger my way around VI, I am by no means proficient).

A way to make the categorization more effective is by applying semantic technology. Being able to eliminate options that are in the wrong context increases the overall quality of the associations.  And the ability to mine for non-obvious associations provides insight into opportunities that would have remained hidden.

Bottom line, whatever the technology, being able to have relevant, quality, networked opportunities delivered to you as they occur will certain help you prosper in the era of the perpetual job seeker.

Twitter, the first ten days.

I tried to stay away. Really, I swear I simply am not that keen on sharing 140 character thoughts, notions and witticisms...but frankly, for better or worse, it appears that one is increasingly considered out of touch technologically if one is not tweeting, blogging and doing whatever the hell it is you do on Facebook. Particularly if you are in marketing, which certainly is part of what I do. So I got a Twitter account recently, and have been gently dipping my toes in the swirling chaos of millions of little thoughts.

A few observations:

At first I was puzzled why so many tweets were in initial caps. What was it about writing a tweet that inspired tweet authors to write like journalists of old with screaming headlines? Um, nothing, it turns out. The truth came to me when I decided to comment on an article from the New York Times -- most sites "prompt" you to tweet by offering the headline as tweet.  How thoughtful -- should I not care to craft a witty insight of my own I can just use what they provide. Easy!

Second, I was fascinated by the number of folks who always appeared to looking off the side (generally the viewer's right, so as to look as tho they are gazing lovingly at their tweet). This particularly seemed to be the case for what appeared to be professional, or business folk. This in fact inspired one of my early tweets, which I will repeat here (which is the point, isn't it?):

"New study shows 3 out of 4 twitter users unable to stare directly at camera."

Still makes me giggle.

Now, here's the thing I still don't really get -- most tweeting is simply retransmitting what smarter, more informed people have already written elsewhere. And generally, as noted above, with little added insight, other than reinforcing whatever beliefs that person already has.  Which is fine, I guess, but certainly makes much noise to filter thru, especially if you follow people with similar interests, as they are all tweeting and retweeting the same damn thing. 

What Twitter has motivated me to do is seek out people who are amply capable of making witty and clever statements worth reading. So far I have found Sarah Silverman to be worth reading, as well as The Onion (whose use of initial caps is perfectly acceptable).  Admittedly, I have not sought out too many others yet, but I am saddened (but respect them even more) by those who have chosen not to tweet, like John Waters (just the film maker from Baltimore, please) -- but I bet if he did they'd be particularly clever.

On a final note, it appears the dead are prolific tweeters.  Kurt Vonnegut has been active lately (and kudos to him, he only chooses to "follow" one single person -- Mark Twain), and you know what, when his writing is broken down into snippets and doled out one at a time -- it really works, but only because he was such a damn good writer in the first place.

When business process, semantics and search collide

As more and more server and desktop applications migrate to the cloud, there is great opportunity to take old, worn metaphors and functionality and re-invent them in lighter, faster, more usable ways.  A few search vendors are already preparing for this evolution by offering architectures and tool sets to build these applications -- Exalead offers a smart take on what they call search-based applications, or SBAs, and Google just announced a business version of their App Engine. And I am sure that others will soon follow.

But something important is missing:

A business process is usually baked, or hard coded, into the application that supports it (with a slight amount of configuration tolerated), so the challenge has always been how to tie disparate applications together into a unique, business-required flow. For example, a process may flow from the SFA app to a pricing spreadsheet to a CRM app, but there is no common connector other than the process or expertise.

Sure, BPM and workflow software can sometimes do this, but it is expensive, complex, time consuming to implement and ultimately only works for processes and flows that are precise and reoccurring. They do little to support "knowledge" or ad hoc processes. And certainly traditional BPM/workflow systems do not offer the kind of flexibility and usability that can fully leverage the benefits of the cloud.

So who can effectively bring a business process sensibility to the cloud and search-based apps? It's a good question, as process folks are too rigid to accept the ad hoc nature of search, and search folks will not like the structure and rules that process requires to be successful. But whoever figures it out will have a killer platform.

The key to this convergence, by the way, will be semantic technology. Think of it this way --  business process, at its essence, is simply a set of rules around how around how words are displayed and connected. The purpose, of course, is so that individuals within a group can come to agreement as to what it is they do, should do or want to do, and agreement to the methods they will use.

I'd like to walk through a example that may provide some insight on how process could be effectively incorporated into search applications.

Let's begin with a simple, traditional process model. What this says, basically, is since a birthday is occurring (the input), there is a need to bake a cake (the activity).  A baker (or actor) will follow a recipe (a guideline or rule), using available ingredients (material) and an oven (a tool or system) to produce a cake (output). This process could be decomposed into its parts, or sub-activities, such as "Select Recipe," "Purchase Needed Ingredients," "Make Batter," and so on.

Traditionally, this representation would be used for reference (here's how we prefer to do it), or it could be automated into a workflow (you cannot bake a cake unless you have a birthday occurring within the next two days).  But try looking at it like this:

Each component of the process is really just a part of a larger entity or repository of common types, that in the case of baking a cake, happen to fit together like this. Certainly each component can play many different roles at different times. This notion of a distributed process environment is exactly what will work in the cloud. Process definitions become metadata and fuel for rich semantic queries that can tap multiple repositories when needed, retrieving and assembling components on demand into an interface that is meaningful to a user at a precise point in time.

What's cool about this is a business process can be enabled from many places -- from a document, from an email, from a user profile on a social network.  Since any component of any process is aware of its role across many processes, users are able to engage in typical ad hoc behavior but will always be a click away from greater process rigor should they want it or the business require it.

This also means that the ability to "model" or define a process needs to fast, easy and human, something most BPM and workflow tools most definitely are not.

Mediocrity of the crowds

Everyone may have a fundamental right to an opinion, but that doesn't mean they know what the heck they are talking about. And put enough of these people together, and well, welcome to the internet, 2010. Loud, anonymous and opinionated with little substance. Credibility and expertise be damned.

While the touted benefits of the hive mind help rationalize this embracing of mediocrity, it in fact makes it even harder to discover information of substance and value as the outliers, both superior and inferior, get clumped together as they are not of the "norm."

Practically speaking, this makes it harder to know what new books to read, what new music may be of interest, or if a movie or play is worth seeing. Not to mention the utter lack of meaningful serendipity. It is not for lack of opinions, but for lack of quality, substantive opinions. While the internet has made it exceptionally easy to solicit and contribute feedback or post one's grandest or most heart-felt insights to a blog (ouch), there is absolutely no guarantee the thoughts shared are of any value whatsoever. And even if there are postings of substance you may simply never find them, having to first wade thru dozens or hundreds of rants and ramblings.

A real problem with this clumping together of outliers is that it also makes it much more challenging to discover things that may be loosely but not directly of interest. Sure Amazon and Google can tell you what has occurred in the past (people who liked this bought that...), but they are lousy at predicting the future because it's, well, unpredictable.

The answer? Well, for as long as they are around, the best resources are still the traditional media, where people are directly compensated to articulate critical thoughts. Skilled writers and reviewers with years of expertise in specific domains. While one may not always agree with their opinions, there is at least respect for the wisdom applied. And by being trusted sources, they enable readers to make discoveries and connections that software simply cannot know to make.

The best advice I can give a first time entrepreneur

You will not get venture funding. Stop wasting your time. If you can't come up with an idea that leads directly to paying customers, go get a job. Do not max out your credit cards, do not borrow from friends and family.

The truth is, if this is your first venture, and you have never raised capital before, you will not get funding. While it is especially true today, it was mostly true since the bubble burst. Now, VCs will not tell you this as they like to stay relevant and informed and will indeed take meetings to learn about you. And of course, they are happy to offer all kinds of advice. But do not let them give you hope – they will not ever consider investing in you, at least not until you have more than proven yourself (and no, not one or two customers, but many, and much revenue).

Now ask yourself, do you have the resources to build your product, get someone to buy it the first time (and by buy, I mean pay enough to sustain you, not a token fee for a “pilot”), and stay afloat long enough until that next sale comes along? No? Then forget enterprise software. You'd probably fail anyway, big businesses tend to be risk adverse and rely on trusted relationships. So unless you have a partnership with IBM, Microsoft, Accenture, etc., you'll never close a deal (tho they will waste much of your time as they too are curious about new technology – they just won't buy it from you).

So what's left? How about software as a service? If you're a geek with a good idea (like solving a problem small businesses may have but they cannot afford to hire an FTE to manage), then building a cloud/subscription based service could give you a way to bootstrap. Tho if you are a geek you may not be particularly savvy at sales and marketing. But hell, you can figure out that stuff by reading a book. Watch out for small business marketing consultants and specialists. If they were any good at what they did they would be charging top dollar working for big businesses. Actually, that advice applies anyone who wants to “help” you, particularly if it involves retainers. They can be expensive and distracting, and rarely produce.

So, to summarize – if you really feel you have to start your own venture, save up, aim small, and expect to fail, tho you will learn much along the way. Good luck!

The possible business benefits of social networks

I have to admit I have been slow to find value in social networks and social media, particularly in a business context. Sure, I've tried Facebook, but I closed the account after I decided I simply did not care enough about the comings and goings, minute-by-minute activities and phone-enabled orgy of idiotic imagery (for example, the image here shows a foul baseball that landed just under the front passenger side of my car, hit by my 11 year old last night at the little league playoffs (they won, BTW) -- without my iPhone, this magical memory would be lost forever) of people I had not seen in person in years, and frankly have little in common with anymore.

Same for Twitter -- I have enough frequent, brief thoughts of my own to organize and evaluate I don't need them crowded out by the pithy musings of others, nor am I needy enough to really believe I am doing a disservice to humanity at large and hindering the advancement of intellectual discourse by not instantly sharing my every thought. That's what blogs are for, which are only slightly better in that they allow for the all-too-often unused capability to produce multiple drafts.

Now, LinkedIn I do use frequently, but less for interaction with others and more for research. And the more features they add, the less interesting it becomes to me as it just creates more visual noise.

Which leads me to the enterprise.  While many people are keen on the benefits of social media within business, I have been much less so.  Businesses exist to produce goods and services for less than the market will bear.  Social networks are distracting, and combined with other distracting technologies like email and phones, it seems to be more counter productive than not.

But here's the thing, whether I like it of not. Social media and networks can be fun and engaging. And if people engage, they contribute.

This has been the classic challenge in knowledge management. Just because you install software to enable a "Community of Practice" does not mean people will contribute. And those who do may not be the ones you really need, as the people who are really good at their jobs are generally busy doing their jobs, and have little time for anything else.

Another approach has been to hide rewards within a system to encourage users to explore it, but that tends to encourage the people who like to find things and get rewarded, and have the time on their hands to do so.  Which, again, are most likely not the people who excel at revenue producing activities.

Social media may be different.

Social media, if woven into the work flow and processes, could bridge the gap so that knowledge capture is thorough, useful and painless. But it will need to be guided and managed to truly be successful.

The big lie in search

The biggest lie in search is also its most touted benefit -- that it is intuitive and easy to use.

Perhaps, as much as a blank piece of paper is intuitive, so too can be a single, empty text box partnered with a single submit button.

But the search results page? Easy and intuitive, it never has been, and it is getting worse and worse as search companies keep adding more options, suggestions, clusters, facets and widgets to try and help you make sense of the endless pages of results. Even the Google with its once pristine layout recently felt compelled to add more clutter to the interface, an explicit acknowledgement that the results they serve up simply are not good enough.

So how could the search experience be improved?

One way is to make the results better by asking just a little more of the searcher up front. If you are able to ask the right questions, you can infer much. For example, if, instead of a single submit button, suppose there were three; "animal," "vegetable," and "mineral." By forcing the user to select, huge amounts of ambiguous results could be eliminated. Of course, this approach impacts the simple, intuitive search box and button combo myth, but if the experience and results are better, does it really matter?

Another approach is to build applications and interfaces that integrate rules to constrain search queries to a specific business purpose or process. To quote from a patent currently pending (um, mine):

"This invention relates generally to software-based search technology, and particularly to rules-based (rules being any standardized set of principles or methods for organizing and structuring information (e.g. The AP Style Manual; IDEF, a business process language; the Marquess of Queensberry rules for boxing) searching via a constrained or guided query structure."

 You can read the full patent here should you be interested.

Bottom line -- attributing the property of "intuitive" to a text box forces a free-for-all environment that must cast too far and too wide, and demands far too much processing on the backend in the attempt to guess at user intent.  Constraining the queries, either by empowering the user or by integrating them into the user experience, can more easily deliver better, more relevant information.

Fun and games with disambiguation

One of the coolest things I have learned in the last few years is the notion of disambiguation, a linguist's term for determining the right meaning of a word within a specific context. My current favorite example to illustrate this is:

This is important, as not knowing which meaning of “manhattan" is being referenced, whether in a search query or in piece of content, can really impact how well algorithms can leverage words. While my interests are currently focused on automated query building, certainly there are many, many interesting things that can be done when proper word definitions are known. Here's an example from our experimental search engine, howdoya.com on how to mix a manhattan. Note all the useful words on the left you can use to refine your query -- disambiguation! Now, if you want to see something really interesting, click on the x-ray glasses next to each search result -- again, disambiguation! A world of possibilities.