ui archives
“Usability problems usually fall into two categories; either it’s not clear how to do something, or something is too cumbersome to do. The latter is fixed by a better understanding of what the key tasks are, and the former is usually resolved by adding clarity. Often the best way to do this is through the writing of the interface.”
Des Traynor: “Writing an Interface” a post about a presentation he gave at Content Strategy in London (Sep. 5, 2011). If you have 25 minutes I highly recommend watching the presentation.

posted by shane on Monday, Jan 30, 2012

The Power of a UI Framework

I was sitting in a meeting recently with several clients and we were discussing how to create a solution for a business need. You know the scenario. I was trying to extract understanding from the clients so I could design a solution. Have you ever started squirming when one of them goes up to the whiteboard and starts drawing little boxes and circles to create a user interface? Do you get that feeling in your gut that this person is trying to do your job and prescribe what you should create? We designers tend to get testy about that sort of thing. We want to ensure we maintain control of the design so that we can enforce quality. It’s a good desire, but the push and pull of client interaction can be distressing at times.

But for me, this meeting was a breeze. There was a tense discussion between the clients, and the complexity of the business rules they were discussing would make the IRS cower. The paint-like smell of whiteboard markers filled the room and there were scribbles of UI layouts strewn across six whiteboards. Me? I wanted to put my feet on the conference table. Everything was going quite well.

The designer-client interaction was working for me because our project team had established a strong UI framework for our app. As the clients were drawing visual constructs of functionality, they were using our widgets, patterns, and themes. They were comfortable enough with the UI framework that they could rely on it to represent their ideas—it made designing the solution much simpler. It was easier for me to decipher what they were attempting to explain because they were designing with the designers’ paintbrushes.

Trust me on this one. If your app is anything bigger than tiny, take the time to create a framework. Here are some pointers.

Create a separate page in your app that showcases constructs and patterns.

Here is part of ours that describes data table models (filled with dummy data, of course). Imagine that the title for each table was something like “Tables that Need X Functionality” and each would have example data to reinforce its intended use.

Hold your peeps to it.

If you’re collaborating with other designers, it’s critical for everyone to own and honor the frameworks. If you need to create an exception or an entirely new construct, run it by the team and do your best to reduce visual deviation. If you’re a small team, consider a weekly design review. If your team is larger, a daily design scrum may be necessary.

Share the framework with your client.

In time, the app you are building will help your clients recognize your design standards. But putting them all in one place gives them (and you) a library of possibilities. For us, our clients began to appreciate the consistency in the application, and became our allies in enforcing it. They began to crave uniformity in app-wide user interactions.

Just try it. Gosh.

This may just sound like more work and an extra chunk of code to manage, but rest assured that it will serve you well. The bigger your project gets, the more critical a framework is. This will reduce the subjectivity of your design discussions and give you something to hold to when a client wants to get crazy with a particular piece of functionality. This has served us well and I’ll continue to put my trust in UI frameworks.

posted by clifton on Thursday, Feb 04, 2010

case study

UIs that lie & the users who believe them

Interfaces are one of the principal sources from which a person learns about his or her work. That understanding gets turned into diagrams, charts, and maps that, whether accurate or not, come to define the work that person does each day.

My initial meetings with Michael were a bit intimidating. It’s not that he himself was overbearing or anything, it’s just that our conversations eventually filled me with a bit of apprehension – a feeling of “woah, this project could totally kick me around”. See, Michael was a new client who needed a piece of software to help his office do their daily work, and he sat down with me several times to make it clear that their process was insanely complex. Gulp.

Now, I’m a designer, which means I’m supposed to be overly confident about my ability to solve a client’s problems. And at the beginning I was, but as Michael reiterated time and time again how difficult his daily work was, I couldn’t help but believe him, at least in part, and that belief haunted me. With every iteration of the project, as we introduced new functionality and explored additional requirements, I winced inwardly, thinking “here comes the tough part.”

This would be a great time for me to introduce a horrific challenge and then brag about how I beat it to a pulp, but unfortunately that won’t be the case today. It turns out Michael’s project actually turned out to be really straightforward. The logic behind his office’s business process was pretty simple, and as we worked together on a software solution, that simplicity came forward – to our surprise – and made both our lives easier. At first, Michael expressed a bit of concern that we’d overlooked something essential. This seemed too easy. But as he and his staff used the application over time, they became convinced that it was all there. Their work really was that simple.

That got me thinking – why was Michael’s simple process hidden behind so much perceived complexity? How was that confusing layer of muck put in place, and when?

Of course, there are tons of variables involved here, and to say that a single factor was wholly responsible for this counterfeit complexity would be a joke. Even so, as I searched for answers about the origin of a lot of business process misunderstandings, I kept slamming into the office’s previous software and its confusing user interface.

The most dangerous thing I saw in the old UI was a knack for misrepresenting information relationships. Due to confidentiality restraints, I won’t be able to share the actual information that was being turned upside down, but let me give you an example:

Alright, alright, this is an obvious one. The figure misrepresents the relationship between “colors” and the rest of the words. Now, because everyone knows about colors (duh!), the mistake is easy to detect and resolve.

It’s easy for us, a bunch of fully-grown, well-trained professionals, to tell that blue, green, red, and yellow all fit within the category of “colors”. Congratulations. However, what would happen if I taught my newborn about color using the first figure? How do you think that would go? Is there a chance some confusion would ensue?

The UI that Michael’s office was using every day to do their work was teaching them the wrong info relationships over and over again. They’d been using it for over five years, and during that time, they had hired and trained several new employees. Their training had been centered around learning to use the old application. Consequently, they had learned their new job inaccurately in essential ways. Their UI was lying to them, and they were eating it up.

You see, as designers we understand one facet of the knowledge-UI relationship quite well. We depend on our clients’ brains to produce the kinds of info diagrams that can teach us about the design problem at hand, and we hope that this understanding becomes solidified and is eventually projected onto our final UI. That’s how we make software.

However, it had never occurred to me that this relationship could also be reversed until I saw it with my own eyes in Michael’s office. For years he and his staff had looked at their old UI, learned from it, formed elaborate diagrams based on what they learned, and then stored them in their brains forevermore. That’s how we capture concepts.

So there it is. User interfaces are one of the principal sources from which a person learns about his or her work. That understanding gets turned into diagrams, charts, and maps that, whether accurate or not, come to define the work that person does each day.

This brings a new dimension of responsibility to our table as interaction designers. Not only do we need to worry about our interfaces being simple, or elegant, or usable, or accessible; we also have to make sure they’re honest. Do they accurately portray our clients’ processes? Do they faithfully represent the relationships between different bodies of information? Do they tell the truth, or do they lie? Ultimately, whatever they say is going to define how our users think of their work, how they understand it, and how they do it.

posted by davidlindes on Monday, Feb 01, 2010

Nathan Borror shares a technique for interface consistency.

posted by jason on Monday, Nov 02, 2009

BumpTop releases for Windows.

posted by john on Thursday, Apr 09, 2009

When I first started reading this review of the Blackberry Bold, the home screen UI looked promising. But the further you scroll down and the deeper you dive into the OS, it starts feeling too much like File System Land.

It’s almost as if the designers only had time to make a good-looking home screen so that the phone would sell well (and meet the obligatory marketing requirement of looking iPhone-ish). The rest of the phone’s OS ungracefully degrades the further you explore.
(via Jared).

posted by clifton on Friday, Aug 15, 2008

I love the new paper-clipped note that has been added to Backpack from 37signals. What a great way to bring the real world into the virtual world in a subtle yet appropriate way.

posted by aaron on Wednesday, Feb 13, 2008

Adobe.com launches redesign, and fails

Visit adobe.com today and receive a shocking surprise of a look that resembles more of a junk pile of web trends, then the website of an industry leader in digital design products. The purpose behind the redesign was to put more emphasis on the content rather than the UI, and work better on wider screens. Unfortunately, I believe the UI is so disgracefully designed it hinders the readability and usefulness of the content and becomes the primary focus.

Flash video headers engulf most of my 15” screen and I can’t see the content. On a 7 Mbps connection, the site slows down so much that the drop down menus are useless, until the center flash video has completely loaded and played. When I hover over the dropdown menus, I interact — unintentionally — with the flash content beneath the dropdown menu. I have such a hard time getting past the navigation, I can barely get to the content and I find myself closing the window rather than surfing any farther.

Coming back later, with the navigation cached, I get to the community pages for designers. My eyes are continually drawn to the empty gray space on the right and top. I have a hard time focusing on the article summaries squished to the left in a 783 pixel wide box, further confined into three columns, each 150 pixels wide. How in the world does this work better for wider screens? I can’t take the claustrophobia any longer and close the window again.

For a site that should be showcasing the best use of its own products, it fails miserably. Content can only emerge when the user interface is so well designed, it works silently without intruding rough edges or poorly aligned spaces into the experience.

posted by emmy on Friday, Dec 07, 2007

A blog about SharePoint UI design? It’s Christmas in November!

posted by jason on Saturday, Nov 04, 2006

Do you know about Yahoo UI Grids yet? More on these later, but dude, sweetness.

posted by jason on Friday, Sep 08, 2006