Landing on Planet Drupal (or trying to)
By Micha | May 13, 2008
It’s been just almost a year since I focused my professional attention onto usability for web applications and launched this web site. I’ve known for about eleven-and-a-half months that, as a hybrid between a blog and a business web site, this site has significant issues. My goal was to see if I could mix my personal perspectives with a professional profile. The experiment is over and I’m not afraid to say it’s a problematic mix and change is required.
Looking at it from a writer’s (i.e. end user’s) point of view, the problem all along has been deciding which ‘voice’ to use – the one that likes to push TUAG’s services or the one that is just passionate about usability issues? The logical decision is to let this site function as a soap box for user advocacy. So that means I need another web site.
And a new site I shall have. Eventually.
I’ve chosen to use the Drupal content management system as the basis for my new business web site. I’ve been orbiting around Drupal for as long as this blog has existed. But on my first approach to it I bounced right out of its dense atmosphere and decided to create my first major web app with my own custom made content management system.
Lately I’ve been taking another look at Drupal, coming at it slowly and more directly with an intent to get my head seriously around it. For the last couple of months I’ve been studying it closely, mostly from the code level, and getting some insight into its strengths, and weaknesses. Progress has been very slow and I would have to honestly say it’s to a large extent because the Drupal administrative user interface has significant issues.
Drupal is an open source framework for building dynamic web sites that has been built by dedicated engineers from all over the planet. It has a brilliant core architecture that, among other things, provides tremendous flexibility in the site presentation – i.e. what it looks like.
But shaping a given web site in Drupal is not an easy matter for the novice. Surrounding the Drupal core is its administrative user interface, a veritable asteroid belt of usability hazards. Much of this outer ring is functional debris emanating from the many moons, or ‘modules’, that orbit the main body. Here, nothing is simple because nothing is connected. Interface components float randomly everywhere, ready to tear through one’s productivity as if it were wet tissue.
Not surprisingly, beyond the asteroid belt there is a calm zone where countless Drupal web sites exist in a state of near identical placidity. In this zone one can hear the whispers of end users and clients asking their web developers “But can you make it look less … Drupally?”
Drupal’s difficulties are not unlike those found in so many other software development projects. In both the web and desktop worlds, software development frequently begins with functionality first, thus leaving the user interface design until much later – typically when screams are heard from the far outreaches of the end user domain.
Having spent 20 years or so working on both sides of the usability/engineering divide I could talk a lot about this phenomenon. For now I’ll just say that functionality created in a vacuum of usability requirements always produces a problematic mix of values. The potential for a confusion through the collision of multiple perspectives is indeed serious. It’s not a question of anyone being at fault - it’s just a state of evolution that can be surmounted with intelligence and good planning.
The discussions happening at Drupal.org seem to demonstrate that there is a growing awareness of this within the Drupal community. That is what impresses me. As a newcomer to the open source universe, I’m pleasantly surprised by the intelligence, civility and democracy in play here. It is certainly motivating me to roll up my own sleeves and pitch in.
I’ll leave other points for subsequent posts. Now that I’m officially booting out the ‘professional profile’ requirement from this site, it’s finally free to become a plain old blog and speak directly from the user advocate’s corner. In the meantime when that other site is launched, you’ll be the first to know.
Topics: user interface design, blogging, usability, connectedness, community, systems, user experience, functional design, design simplicity, Drupal, open source | 3 Comments »
Getting It Real and Really Getting It
By Micha | April 21, 2008
I recently jumped ship on a project that seemed destined to hit the rocky shores of missed deadlines and then sink in the swirling eddies of communication breakdown. I wasn’t on board for long - about a week and a half really - but during that time I spent far too many days trying to obtain critical information about the project’s code structure and database from the engineers who had developed it.
The problem seemed to stem from the fact that there was no provision made to pay the engineers for the time it would take them to conduct a proper knowledge transfer to me. As independent business people like me, I would certainly not expect them to do this for free.
But the young manager at the helm of this project, seemingly on her maiden voyage, had very little idea about how to connect the crew of geographically dispersed contractors. Sadly, she exhibited an unrealistic faith in the value of the ‘Chat Tool’ (complte w. obscr abrev.s and speling mistwaks) for bearing the brunt of the knowledge transfer process. So much for context and clarity.
What was clear was that my need to communicate with the team through phone calls rather than emoticons proved to be an indulgence that lay far beyond the reach of this project’s budget. With no course corrections forthcoming I felt I had no choice but to jump into the nearest lifeboat.
I’m not used to backing away from a challenge and to be frank, this left me with a thirst for some sort of confirmation that bridging the gap between end users and engineers requires not only knowledge, experience and insight but also a solid channel of effective communication in both directions.
It so happened that last week, I was on a panel* for the Ottawa Software Executive Forum (OSEF) that discussed the topic of “Effective Techniques for Defining and Designing Product Features”. To my delight, our discussion gravitated towards the very issue of how to bridge the gap between end users and engineers. What a great opportunity to air out some ideas and validate my ‘obsession’ for high bandwidth communication.
As a panel of agreeable usability specialists we initially risked boring our audience of software executives with our collective head nodding. However there was an individual in the audience who had more than a little to say on every aspect of our discussion.
At first I misread his energy, thinking that this was going to one of those gruelling sessions where one overly-eager individual would dominate the proceedings and steer them into a deep ditch of irrelevant ideas. However the fact was this particular guy was talking sense – a lot of sense.
And by ‘sense’ I mean he was one of those rare software executives who seemed to ‘get it’ when it comes to recognizing some of the real issues behind getting engineering processes to be both user oriented and productive.
He understood the value of guiding engineers, designers, and product managers into a common mindspace that focuses on solving tangible real world problems for real world end users. Focusing on a common goal such as this, along with using the proper collaborative tools, greatly improves the chances of working more effectively together.
He repeatedly spoke about the benefits of ‘agile development methodologies’ which, among other things, stresses the key importance of high bandwidth, face-to-face communication between engineers and business experts.
My thirst was quenched. But it got better than that - it turned out that this man was none other than Dave Thomas who has an impressive track record as a thought leader in the world of innovative software development practices. Widely known for founding Object Technology International (now IBM OTI labs) he is a pioneer in Agile Product Development and one of the founding directors of the Agile Alliance . Confirmation from such an experienced source was indeed like coming home to a safe port.
In conversation after the session, Dave shared a revealing anecdote about an individual who no doubt contributed to his awareness of the need for proper production practices. He spoke about an uncle who had worked his way up to a very high position at AT&T. Technologies change rapidly and, over time, this wise uncle became concerned about the growing knowledge gap between himself as a senior executive and the ranks of engineering staff under his management. One day, to the horror of his peers and the surprise of his staff, he resigned his executive position and jumped back down to the level of engineer in order to re-immerse himself in the realities of the current technologies.
Throughout our panel discussion Dave had stressed, from his seat in the audience no less, the importance of software executives ‘walking the floor’ and staying vitally in touch with the realities of the day. He declared that far too many of today’s software executives approach their job purely from a theoretical ‘bottom line’ point of view and lack the critical knowledge required to steer the development ship away from dangerous waters.
I couldn’t agree more.
Footnotes
*The panel members were Scott MacEwen of Cognos/IBM , Lorraine Chapman of Macadamian Usability, Tom Hoferek, Corel Corp, and myself M Baynger of The User Advocate Group. The moderator was Marc Graveline of Cognos/IBM)
(back to story)
Topics: usability, customer relations, user relations, user experience, coding, ineffective communication, understanding technology, effective communication | No Comments »
Demand More
By Micha | March 29, 2008
What is a software application?
When we think of a software application, most of us will conjure up the image of some sort of user interface splashed across a computer screen. As far as most of us are concerned, whatever is on the screen is the software. Period.
Engineers will tend to look at it a little differently. They are of course very aware of what goes on ‘behind the screen’ that makes all this stuff appear as it does and do all the things it does.
As a user interface systems designer I look at the screen as bit of a battleground. Two decades of working in the industrial software biz makes me intensely aware of the people behind a given application and sometimes I can almost hear the arguments and debates that must have taken place in the process of its creation.
In that sense I see a software application as an attempt by a small group of people (behind the screen) to communicate with a large group of people (in front of the screen). Typically, the purpose of this communication is so focused on some functionality that we usually see the software application as a thing unto itself rather than as a meeting point between engineers and users or vendors and customers.
What I mean is, we treat a software application as a distinct objective entity rather than as a measure of a complex relationship between two distinct groups of people.
From the point of view of a usability specialist, and standing just slightly behind the screen, I see a software application as an attempt to anticipate something significant about who you are as a user and what tasks you are trying to accomplish. It’s a sort of disembodied sketch of you and aspects of your life.
Your ease of use for a given application is directly related to the accuracy of the image that the software’s creators have of you. If the producers of the application never bothered to put themselves in your shoes as a user, then your experience of that software will probably be somewhat uncomfortable if not outright frustrating. Perhaps you can recall such an experience. Perhaps you can recall many.
On the other hand it is not always easy to do that envisioning work, especially if the application is a new invention or a venture into new territory. Unless the application designers have their feet on the ground and are truly able to see things from the users’ point of view, their efforts may be wasted.
And worse yet for the vendor’s business plan, the entire R&D and marketing efforts may be at risk because if a better alternative comes along, customers may well flee at the first opportunity.
I saw something the other day that illustrates this situation quite nicely.
This billboard serves as a wonderful analogy for the type of software application that misses the point. In this case, the ‘functionality’ is not distracting, in fact there may be no functionality at all beyond the intent to entertain pedestrians at a busy street corner.
I think it’s safe to say that the entertainment value comes from the mysterious trick that our eyes seem to be playing on us. The point being that the dot is objectively half way down the triangle but when we look at it, it seems to be closer to the top.
But in this particular deployment, if the Passerby User thinks to herself “but the dot really does look closer to the top” she would be perfectly correct. Look at the metrics up close.
This ‘Billboard Application’ was deployed on the roof of a building and, from the user’s perspective, the dot is closer to the top because of the non-linearity of the optics. However slight it may be, the subjective experience is in fact more accurate than the creators had perhaps anticipated and arguably the entire point of the application is lost.
So there is a similar kind of disconnect here between the intent of the application creators and the experience of the application users.
As a User Advocate my point is this: like a gigantic billboard towering over a streetscape, a computer software application may carry a certain air of objective authority. We, as individual users, are often made to feel very small and are forced to adjust to its way of doing things.
So often we have no choice, no matter how frustrating the user experience may be. We often don’t question the way an application behaves because we are too busy trying to use it. We’re trying to book a plane ticket or print out an invoice or find a bus route or whatever the task is at hand. We are usually so focused on trying to achieve that particular goal that we can’t step back far enough to see how this application could be made better - beyond wishing it would just place the right button at the right time in the middle of the flippin’ screen.
So, fellow users, if you can take away one thing from all this (listen up fellow designers and engineers) I would hope it is a strengthened sense that your experience is what really counts. It’s worth remembering that, from your perspective, the software is the tool and not an end unto itself. If you find yourself feeling confused or frustrated by the way an application behaves, you are entitled to absolve yourself of blame and see the problem as lying on the other side of the computer screen. Demand more.
Topics: user interface design, subject oriented design, artificial intelligence, usability, graphical user interfaces, systems, customer relations, user relations, user experience, functional design, ineffective communication, understanding technology, effective communication, target users, target markets | No Comments »
Turning New Pages
By Micha | February 28, 2008
As a software artist who is focused on ‘bridging the gap between end users and engineers’ I have always found it necessary and worthwhile to explore the ‘materials’ that I work with. In doing so I can better control the emotional impact of an application on the user: the more I know about how the technology ticks, the more I can coax an application into being a pleasurable experience for a user.
With that in mind I set off on a project last year to learn about and work with web technology across the full spectrum - from front end design to back end programming. I had a unique opportunity to do this when I was asked to create a new web site for Pages Books and Magazines, a cool, indie bookstore that has been a long standing fixture in the hub of Toronto’s cultural center on Queen Street West. I began by interviewing at length the proprietor, Marc Glassman, his site editor Shaun Smith, and the Pages’ staff about what they required in the new web site. After coming up with a design concept, I then began a long trek across a new technological landscape and learning a lot about such fascinating areas as PHP, MySQL, AJAX, CSS, Templating Engines, and Javascript. Thus I gathered the materials and knowledge required to actually build the site.
My client’s key aesthetic requirement was that they wanted something ‘light and quirky’. This, combined with the use of the shop’s fabulous signage art, was my guiding principle for the emotional experience of the web site. The artwork, done by Toronto artist Michael Cho, perfectly reflects the character of this smart and hip alternative book store.
It turned out that building the front end (the part that you see) was a relatively easy task. Where the real challenge came was in building the back end content management system and the accompanying administrative interface. In striving to make the content creation process just as easy and pleasurable to for the Pages’ staff users as the site is for end users I chose to put some extra effort into making the interaction as clear and productive as I could and avoiding many of the usability pitfalls that many administrative Web UIs seem to possess because they are not seen as ‘important’.
The resulting web site (www.pagesbooks.ca) was launched a week ago. I approached the task of guiding users around the site with a number of methods including an ‘active home page’ where inner content can be surfaced to the level of one-click availability, and colour cues that gently inform users of the context for the information they are looking at.
I’m happy to be back from this journey and eager to apply the new knowledge to future projects. But I also want to take a moment to thank others who helped me along the way and got me out of a few scrapes. First of all, thanks to my associate Tom Kamil who collaborated with me to, among other things, help interpret the meaning of ‘light and quirky’. Thanks also to Adrian Karmel who got me pointed in the right direction to tackle the MySQL stuff. And to Gavin, Peter and Daniel of the Ottawa PHP meetup group and Brett and Steve of 76 Design who inspired me with their own projects and aspirations as well as graciously sharing their knowledge when I got lost in some dark technological valleys. And a big thanks to Tyler Brown who made a significant impact on the success of this project by providing important insights and expertise on a variety of topics across the technological spectrum. And last but not least, a big smooch to my partner Conchita Flores and a warm hug to the rest of my family, who put up with me being a total geek for so many months.
More and more I hear about the gap between ‘design and development’ in the arena of web site creation and the many ways that web sites just don’t meet the needs of the business owner and their customers. And as businesses require ever more sophisticated web applications, the challenge to keep them usable and productive for their customers grows exponentially. As a User Advocate and user interface designer with a detailed knowledge of the technology behind dynamic web sites, I can better serve my clients by truly bridging the gap between end users and engineers.
Topics: user interface design, subject oriented design, usability, art, user experience, Geekness, coding, understanding technology, target users | 1 Comment »
The Meaning of Art, The Purpose of Technology
By Micha | January 2, 2008
As a software artist I am a beast with two heads. I am an artist by compulsion and I am a software designer/engineer both by choice and sheer determination to understand technology. Most people tend to address one head or the other, depending upon whether they meet me first as an artist or as an engineer. Some colleagues grasp the nature of my hybrid approach and they are a pleasure to work with. Some never grasp it at all.
As a child I had often wondered if I would be an artist or a scientist when I grew up. Digital technology, particularly computer graphics, came along as a perfect middle ground where I could exercise both my visual imagination and my need to work through problems methodically.
Although I began my career as an artist and art gallery administrator I was drawn to working with software design and eventually committed to it full time. This was perhaps inevitable because of my precise but wide open definition of the meaning of art. While still in art school I formulated a practical definition of art based on investigations into information theory. I had become enamoured with the way scientists spoke of information as a combination of variety and redundancy and described the ways that signals could be transmitted through the mechanism of carrier waves.
As an artist I pictured various ways in which communication signals carry not just information but also meaning across the great voids that separate all human beings. It was this aspect of my studies that caused me to realize that I had become interested in art not necessarily to make drawings or paintings but because it was a system of communication. In that regard I understood immediately that the concepts of carrier waves and signals as described by scientists corresponded directly to the concepts of form and content that is studied by art historians.
My direct experience as a practicing artist led me to define art as nothing more or less than Minimal Redundancy.
The meaning behind Art=Minimal Redundancy is not really new and has been said using other terms by many who have thought about it.
Occam’s razor is not equivalent to the idea that “perfection is simplicity”. Albert Einstein probably had this in mind when he wrote in 1933 that “The supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience” often paraphrased as “Theories should be as simple as possible, but no simpler.” It often happens that the best explanation is much more complicated than the simplest possible explanation because its postulations amount to less of an improbability. Thus the popular rephrasing of the razor - that “the simplest explanation is the best one” - fails to capture the gist of the reason behind it, in that it conflates a rigorous notion of simplicity and ease of human comprehension. The two are obviously correlated, but hardly equivalent.
From wikipedia.org/wiki/Occam’s_Razor
Art=Minimal Redundancy speaks of the idea that something special and meaningful occurs in communicative expressions that neither lack anything nor contain any superfluous parts. It is a perfect balance of form and content. It does not discount redundancy but regards it as the formal component of communication. Neither does it allow for unnecessary redundancy because that implies an unintended content component and hence a statement of lesser meaning. If you compare a masterwork to an amateur’s painting you may be able to see that the master is able to convey information about a subject with fewer extra bits and pieces than one who lacks that degree of vision, passion and control.
But you could arguably also say the same thing about tennis players or truck drivers although the specific outputs of such practitioners may not have the same impact on the hearts and minds of a wider public. In other words there is surely an art to volleying a tennis ball or backing a transport trailer even though the appreciation and valuation of such ‘art forms’ may not exist as such in our society today.
If you are grasping what I am saying here you may also see that defining art as minimal redundancy frees one completely from looking at it through particular forms or even disciplines. Suddenly the world itself becomes our studio. Anyone can potentially create ‘art’ in any context. Art and Life are indeed inseparable.
My working definition of art was conceived in a context of scientific and technological language. It was therefore perfect for helping me make the transition into a technology focused career. As a conceptual tool, this practical benchmark for creativity has helped me produce new and original inventions as well as provide a platform for critical analysis of technology itself.
And this perspective has naturally led me into the arena of user interface design – where user interface systems can be regarded as primarily human to human relations, mediated by significant technological components, and NOT as human-computer relations, as is implied by the term “human-computer interface design”.
Like “artificial intelligence”, the term “human-computer interface” is unsatisfactory for me because it implies a creative or responsible role for the machine component rather than regarding it as just a communication vehicle. As a blog writer I can talk to you through a ‘pipe’ that has a computer on each end – like tin cans on a string. As a software designer I can also talk to you through that same mechanism but the message, and user experience, will have a different quality.
Art forms such as painting, stained glass and architecture were the multimedia communication vehicles of the past. Cathedrals were the pinnacle of technological advancement in the middle ages and, like the computer today, were the economic drivers and focal point of many social communities. The purpose of this technological marvel was to uplift the human spirit and even today any visitors to the site of a medieval cathedral will still be able to see that it continues to function in this way.
The computer is the cathedral of today. Google is a ‘technological edifice’ that towers over much of our daily virtual landscape. Where medieval peasants may have entered cathedrals to search for meaning, we routinely come to Google to search for links. We stare into the brilliant colours of our computer screens and marvel at what see.
I think it is a relevant question to ask what is the effect of modern technology on the human spirit?
It may or may not be worth pointing out that, despite all appearances, even the most sophisticated computer algorithm possesses no more, or less, consciousness than a blob of paint. Philosophically I am deeply opposed to the idea that computers should be regarded as ‘conscious’ or ‘intelligent’ in some creative fashion that even remotely resembles human consciousness.
Furthermore I am very much opposed to human beings relinquishing their creative potentials to the straitjacket of bad software design. To varying degrees, this inverted relationship with machine, where we see ourselves as unable to control it, has the effect of quashing the human spirit.
As a software artist I am committed to finding ways of preserving and even stimulating creative activity on the part of end users. And the guiding principle I use for achieving this goal is to create designs with Minimal Redundancy.
Topics: user interface design, artificial intelligence, usability, art, community, graphical user interfaces, meaning, user experience, framing, functional design, Humanity, ineffective communication, understanding technology, design simplicity, effective communication, minimal redundancy | 2 Comments »
The (In) Convenience Factor
By Micha | November 27, 2007
The motto and the objective of The User Advocate Group is to:
“Bridge the Gap Between End Users and Engineers”
Why is there such a gap? Well, there are many reasons such as: “language” differences (”geek-speak” vs. “human-speak”); lack of effective communication channels; economics; priorities (technology-centric vs. user-centric); etc.
But here’s one that came to mind recently as I was making my daughter’s lunch. I call it the (in)convenience factor. (How you pronounce it depends, I suppose, on your perspective – a half full / half empty kind of thing.)
You might ask: What’s making a sandwich got to do with using a software application? Well for a start both can involve tasks that should be simple. Using a well designed software application should be basically effortless - or at least rewarding and pain-free. It should be as easy to do as say… making a sandwich.
I’ve made my daughter’s lunch countless times with no significant experience of effort – until this one occasion. I encountered one of those bread bags that was sealed with a bit of sticky tape rather than the familiar and easy-to-use plastic clip. My response was to utter:
“#@#$(*@$??!!!”
And by that I meant “Why is this unnecessary obstacle preventing easy access to my loaf of bread???!!!”
And that’s precisely the kind of user experience any good designer should seek to avoid. Sadly, the world of software applications is full of bits of ‘sticky tape’ that prevent us from getting our work done efficiently and stress-free.
Later I reflected on why these bits of tape even exist. The answer I came to is the (in)convenience factor. My guess is that it was deemed convenient for the manufacturer to use sticky tape rather than the standard plastic tags clips. But what was convenient for the production process in this case was highly inconvenient for this end user.
Perhaps the rationale was profit rather than ‘convenience’ but I, for one, will never intentionally buy a loaf of bread sealed with a piece of sticky tape again. If others happen to agree with me then this could become a costly inconvenience for the manufacturer.
This is precisely what flashed through my mind a couple of weeks ago as I was implementing a navigation feature for a web site. I found myself tempted to lean towards convenience in code production rather than building an interface that would be convenient for the end user. Shame on me!
It doesn’t really matter what the specifics were – the point is that I had two options: get it done fast and grab an early lunch or get it done right - maybe after lunch. As ‘inconvenient’ as it was to my personal agenda at the time, I chose to do it right.
These kinds of twists and turns are the daily reality of software engineers. The risk is that always choosing the convenient-for-production route may ultimately result in serious defects in the product and in the ability to reach customers.
Of course at the same time the profitability of the production process has to be taken into account. In a larger sense, the convenience of production should really come from having a good strategy to meet the needs of both the customer and the business. It’s very inconvenient to not sell yor product and it’s also pretty inconvenient to rewrite it after you find out users are fleeing to the competition.
Great code doesn’t necessarily need endless labour – just a clear and meaningful plan based on an accurate view of user requirements and a realistic assessment of R&D capabilities. Such a plan is in fact the bridge between the end user and the engineer. And building that bridge is what we do at The User Advocate Group.
Topics: Uncategorized, user interface design, usability, graphical user interfaces, customer relations, user relations, customer service, user experience, Geekness, coding, ineffective communication, design simplicity, effective communication | No Comments »
The Occasional Frequent User
By Micha | November 8, 2007
Last weekend we set the clocks back for the winter. It’s always nice to have an ‘extra hour’ and to perhaps do something a little special: lay in bed, go for a leisurely breakfast, take a long walk in the park. It’s one of the perks of living on a tilted globe.
For me, this time of year also means that I get to be an Occasional User for certain technology interfaces such as the button riddled panel on my car stereo and the monstrous web tool for managing expiring domain names.
In the past I’ve been completely stumped by the task of adjusting the little car stereo clock and for many years I just let the thing be off an hour throughout the winter months. Having of course lost the manual I was not able to get beyond the point where clicking the ‘Clock’ button would simply toggle the LEDs between clock time and CD song time.
One year I had a brilliant insight – or was it an accident? – and I held the ‘Clock’ button down for long enough to set the LEDs flashing in a promising fashion. Then all I had to do was figure out which of the many other buttons would actually adjust the time. Eventually, after enough stop lights, I was able to accomplish the task.
The problem is that I would forget all of this in the following six months. As an Occasional User I was perpetually untrained, at least for a number of years. It’s not so much a learning process as a forgetting-and-relearning-process. This year however I was very pleased with myself for getting the whole operation done in the space of a single stop light.
But then there’s that domain name problem. I decided, for convenience sake, to transfer all my expiring domain names to my newer registrar, GoDaddy. It turns out that GoDaddy uses the ubiquitous “Domain Control Center” for domain name management. The Domain Control Center is found on many registrar sites including, ironically enough, the site I am choosing to leave. I don’t know much about the mysterious world of domain name registrars but it appears that either one corporate entity controls a good number of disparate brands or many registrars license The Domain Control Center engine. Considering that www.domaincontrolcenter.com takes us straight to GoDaddy.com one might draw the conclusion that it’s GoDaddy’s baby.
That in itself is not a problem. Where the whole thing comes to a grinding halt for me is that this DCC is essentially unusable for anyone who has more than a tiny handful of domains to manage. I had about a dozen in this batch and after an arduous 2 hour struggle, several of my domain names had still not made it across the transfer chasm. Perhaps I’ll try again someday but in the meantime I have better things to do with my time.
So what exactly was the problem? Well largely it comes from two factors:
• The plethora of cryptic links on the interface
• The dogged insistence on doing everything piecemeal
These two conditions actually spell out a core usability problem. Each is a distinct design paradigm and each points in a different direction: the first towards a more Frequent User who has managed over time to learn the meanings of the links; the second seems to cater to an Occasional User who has only one or two items to manage and needs the task broken into a linear sequence of steps. I fell into a third, unsupported category as one who is an Occasional User who would like to be efficient in managing a significant number of items - in bulk.*
To make matters rather more stressful is the fact that the proper authorization codes and IDs must be reconciled for obvious security reasons. This is done through emails coming from both the old and the new registrar. One takes the information supplied in each registrar’s email and enters it into the process at the other’s site. Although this may sound complicated in words, the user who has a single domain name to manage may not notice a problem. But in my case I found my inboxes for my two respective email accounts (old registrar and new registrar) became populated with the likes of this:
Now what this means is that not only is one forced to deal with the numerous changes one at a time, but without domain name information in the subject line one must also play a rather silly lottery to guess which emails contain the info for the particular name that is being transferred. The option of true bulk management seems to not exist - or at least it is not apparent to the Occasional User.
So let me describe the user experience in terms of an analogy. Let’s say you’re cooking an omelette. This is typically not a complex task because you simply pull all the ingredients out of the fridge and get them ready on the counter. Then you crack a few eggs and place them in the bowl, mix ‘em up and cook. Very simple.
Now let’s do the same thing in a Domain Control Center style of working. You walk into the kitchen after entering your password (if you can still remember it from last year). You open the fridge and realize the ingredients you want are not there - you will need to transfer them from the grocery store. Your fridge gives you secret information that will enable you to acquire the eggs from the security conscious grocery store. You go to the store and at the front door you give them your other password (if you can remember that one). You want to get a dozen eggs but are told that you can only buy one at a time. You make numerous trips to the dairy section and return to the check out with a single egg. Naturally, you’d like to pack up the eggs in your shopping bag but are told that they will be delivered – for security reasons of course – to your home.
Back in your kitchen, you are told that the eggs (when they arrive) cannot be all put in one bowl. Instead, each egg must be scrambled in its properly assigned bowl, each of which you must select before bringing the egg into the kitchen. The eggs arrive in the back of a truck in individual, unmarked brown paper bags. You go to your front door and ask the delivery guy to give you a bag. He brings you one but in the kitchen you find it’s not the right egg for the currently active bowl. You head back to the front door and ask for another. You spend an hour or so trying to match eggs with their respective bowls, endeavouring to ignore the shouts of your kids who are due to expire from hunger at any moment. You begin to wish that there was such thing as a fast food restaurant in this strangely twisted world.
There are many instances in which our world is so strangely twisted and our time so amply wasted by systems that are poorly designed. On a happier note, today happens to be World Usability Day. I applaud the higher profile that this international event gives to the efforts of usability professionals who work hard to remedy some of these unnecessary and avoidable stresses. But they can only do that if software producers take the step to hire them. If you are creating a software application, do your customers a favour and hire a proper usability expert to help ensure your product caters to such factors as these significantly different types of users: the Frequent User and the Occasional User and, yes, the Occasional Frequent User. It can make a world of difference.
Footnotes
* To be fair, there is a ‘bulk transfer’ feature in the Domain Control Center. However it seems to be inconsistent and after entering multiple names at the start I found myself having to deal with individual items again. It could well be that I missed something in the interface - but then that’s my point about being a perpetually untrained Occasional Frequent User. (back to story)
Topics: Uncategorized, user interface design, subject oriented design, usability, graphical user interfaces, customer relations, user relations, customer service, user experience, ineffective communication, design simplicity, target users, target markets, web monsters | 1 Comment »
Facing Your Web Monsters
By Micha | October 30, 2007
Hallowe’en is here – is there a monster lurking in your web site?
Hang on, you don’t believe in monsters? Then let me offer this very practical definition that I once heard and you can think again…
“A ‘monster’ is an aggregation of disparate parts.”
Simple enough and bang on, I think.
Now about your web site. Is it a portal or a torture chamber? Is it a useful tool or a Time-Consuming-Beast? Does is make your customers happy or send them shrieking into streets? You want to find out? Who ya gonna call?
Usability Testers would be a good start. A well formed usability test can sniff out those demonic disparities and diabolical dead end links. It can cast a bright light into the shadows of broken work flows - although, to be honest, you may not like what you see in there.
But don’t be afraid, there are more Forces of Good at your disposal – Information Architects can clean out the muddy data structures (where Time-Wasters love to breed) and an experienced User Interface Designer can turn those stifled work flows into breaths of fresh air.
But before you dial for help with your graphical user interface design problems, don’t assume a Graphic Artist is the same as a User Interface Designer. Graphic Artists have an important role to play but their toolsets typically aren’t intended to cut through the usability blockages that form in the dusty cavities of the World Wide Cob-Web.
And if you want to ensure a long and happy life for your web portal, a Templated User Interface System can protect your users from the sharp claws of the Exposed-Code-Beast. Your typical user is probably not a systems analyst, so don’t make them think like one – a template system can keep the Code-Beast in the back end where it belongs and let the front end be populated exclusively by Good Usability Spirits.
So if your web site has become a Little-On-Line-Shop-Of-Horrors remember there is help out there. But if you care about whether you get a Trick or a Treat be careful about whose door you knock on.
Happy Hallowe’en!
Topics: user interface design, usability, graphical user interfaces, customer relations, user relations, user experience, information architecture, Smarty, web monsters | 1 Comment »
Road Blocks and Code Blocks
By Micha | September 19, 2007
A couple of weeks ago I alluded to my journey of discovery into server side web programming as being like an expedition over perilous, rocky terrain. Certainly the learning curve has been steep in places but I really enjoy the view from the top – when the answers to previously daunting questions can be finally seen with alleviating clarity.
So just for fun I thought I’d share with you one of the obstacles that I ran into recently. Like some boulder on the trail this one stopped me in my tracks for quite a while until I finally saw the answer.
Take a look below and see if you can solve the problem. You don’t even have to be a software engineer as long as you can stomach the bizarre appearance of SQL code – it will give you a glimpse of what software developers face everyday as they stare into their screens. If you ever wondered why engineers give you that glazed look when you ask them a simple question, it’s because they have a head full of stuff like this. So go easy on ‘em.
Really, it’s just a pattern matching exercise and to solve the problem you just have to spot the difference between the two chunks of code. The first snippet does not work and the second one does work. And naturally, the problem becomes increasingly hard to solve as a deadline approaches.
Here it is:
DOES NOT WORK:
SELECT a.title, a.teaser, a.contentItemId, a.typeId, s.sectionName AS secName
FROM contentItem a, section s
WHERE a.typeId > 200
AND a.deleted = 'N'
DOES WORK:
SELECT a.title, a.teaser, a.contentItemId, a.typeId, s.sectionName AS secName
FROM contentitem a, section s
WHERE a.typeId > 200
AND a.deleted = 'N'
Did you find it? Well it took me a while – first to narrow the problem down to these two cases and then to see the difference between them. Have fun with it!
And just to make it more interesting I’ll even send this stylish-all-purpose-indoor-outdoor-official-User-Advocate-Group-baseball-cap to the first person who sends me the right answer in the comment section.
Now that’s really worth racking your brains for, huh?
Update:
So we have a winner. Dan was first to get his correct answer in. Thanks Dan, I owe you a hat! Thanks also to Pierre for adding his comment and to the folks who checked it out and sent me replies ‘offline’.
Update 2:
So I traveled all the way to Kanata, Ontario for the presentation of the Grand Prize to Dan (and also for a nice lunch with the gang).
Topics: Geekness, coding, understanding technology | 5 Comments »
The K.I.S.S. of Death for User Interface Design
By Micha | September 10, 2007
Probably everyone involved with user interface design has heard the K.I.S.S. maxim.
“Keep It Simple Stupid”
It always struck me as a bit rude to tack that last word on the end. But I suppose the acronym K.I.S. just doesn’t have the same impact. Nevertheless, the word seems to stick out like some loose barb, ready to slash at anyone who might disagree with those who sagely utter the phrase.
But I don’t actually find it a helpful phrase. Aside from its cliché usage, it doesn’t promote good communication amongst stakeholders. And, by masking assumptions, it allows widely diverse opinions to remain concealed beneath that one, almost useless, word – s i m p l e.
Motherhood. Apple Pie. Simple User Interfaces.
It’s a sad fact that I’ve sat through many meetings where otherwise intelligent executives will show an appalling lack of understanding of what is really required for an application to be successful from a usability standpoint. In my opinion, that always boils down to having clear answers to two key questions:
1. Who Is The User?
2. What Should They Be Able To Do With This Application?
Quite often these seemingly simple questions can be very difficult to answer. Why? Well I have my own quaint maxim to shed light on this. It goes like this:
The K.I.S.S. of Death for User Interface Design
Imagine people at a fairgound arcade all shooting for their respective bullseyes. All of them are doing precisely the same thing - staring dead ahead and focusing on the bullseye. But none of them are shooting for the same target. They are competing against each other. This is the last thing a software company needs on its own production team. It is extremely important to establish and articulate the common goal.
So when account executives, product managers and so on utter the K.I.S.S. phrase in my presence, I encourage them to worry less about designs not being ‘simple’ and to think more about identifying who their target users are. This forces them to really think about, and articulate, what market problems they are trying to address. This helps ensure that we are all shooting for the same thing.
If you can identify a target user group you stand a much better chance of making your application simple – for that group of users. Or put it the other way – if you have no concept of a target user, you will never produce a simple application.
It is a real joy to hear a senior executive or product management team speak precisely about who they are targeting as their prime users for a new product initiative. I know that a great design is just around the corner.
Topics: user interface design, design simplicity, effective communication, target users, target markets | No Comments »