Designed in California, Built in Hell

FIlm Still from Cocteau's Orpheus

 

Inhuman working conditions within Apple’s manufacturing supply chain stand in stark contrast to the superlative usability of Apple designs. It should give ui designers and software design engineers pause—especially those of us that talk about user-centered design.

“As our society becomes increasingly focused on accessing and manipulating information and on communicating digitally, it’s very easy to lose site of the physical reality right around us, let alone on the other side of the planet.”

Right here in New York we use our iphones amid crumbling infrastructure while the best design and engineering talent is applied to the next generation of handhelds and software.

Now we learn that the sleek Apple products we’ve come to love and depend on are produced in factories with exploitative policies and dangerous working conditions, routinely exposing workers to toxins, dangerous machinery and numbingly long shifts that exceed reason.

The fact that these conditions are an integral part of Apple’s pricing structure—and, thus, their profitability—has been widely commented upon. What has not been discussed is how this implicates the design community.

Q: What does it mean to talk user-centered design philosophy and then ignore the manufacturing and supply side of the process?

A: It implies an inherent bigotry embedded in the assumptions. It would seem that we believe that users of the products are entitled to the best possible user experience while those involved in manufacturing the product are not entitled to any consideration whatsoever.

And it points out the extent to which user experience design has become obsessed with the interaction between some humans and computers at the expense of other humans and the physical world.

Public knowledge of working conditions may build and exert pressure on the industry to clean up its manufacturing act.

Physicists and basic technologists are on the path to developing ever-smaller transistors, and progress in nano-tube transistor technology is moving ahead as I write this. It is predicted that one day soon processors will be small enough and cheap enough to embed in everyday objects, allowing us—perhaps—to truly realize an intelligent world.

“Perhaps this will enable us to reconnect the world of pure information with our physical infrastructure.”

And perhaps the brilliant designers who are now working on yet another redundant mobile app will turn their focus to making our physical world more humane.

 

Share this article

Proliferate, Aggregate, Repeat: Why App Aggregation will be the Next Big Thing

Archimboldo, The Librarian, 1566

Looking at the path the internet has taken over the last ten years, a repeating pattern is emerging. The pattern starts with the establishment of a new asset or application class. It proliferates throughout the web. Then the aggregators come along and start skimming the cream off the top and presenting the best in single package. This pattern began with pages, moved on to shopping, news, reviews and downloads.

Today, with the proliferation of stand-alone applications, the environment is ripe for the next level of aggregation.

A Glimpse

An early entry into this space is If This Then That (ifttt.com).  ifttt is a meta application that allows users to build custom programs that uses separate apps as triggers and components.

How It Works

Using ifttt, you can create a task (or recipe) that automates a process that you used to do manually. For example, take a Facebook status update as a trigger to create a tweet, a new blog entry and update a photo automatically. Or, it might use a weather report or new information on an RSS feed to trigger a series of actions across personal sites, social networking pages, email or micro-blogging. While it is still rudimentary today, don’t shrug it off as just a novelty item.

Going Beyond the Individual

Consider instead how an application like this could integrate with Google’s social graph. The potential to trigger actions that are rules based, broadly social and widespread are staggering (and potentially virus-like).

While we shouldn’t underplay the concerns about security and the stultifying effect that automated messaging can have on human-based social interaction, the promise of this next phase of aggregation is beginning to come into focus.

Image: The Librarian, oil on canvas, Archimboldo, ~1566

Share this article

Social Listening Needs Standards

Robert Egert, 1992, Pinocchio, 72" x 72", oil on canvas, collection of Mary Ziegler

In the last two years smart brands have turned themselves inside out to focus on what customers are saying about them instead of focusing on their own marketing messages. This has begun a slow but steady sea change, shifting marketing focus from creative ideas to smart analytics.

Agencies (both traditional and media) are challenged to step-up to the plate and deliver insights based on social listening. Media agencies are often in a good position to take advantage of this opportunity since they have an infrastructure already in place around analytics—extending that to include social listening is a lot less challenging than establishing a new service.

The marketplace is overflowing with analytics tools that range from high-priced industrial strength products to free, web-based products that are open to anyone and new entrants are emerging ongoing. The products vary in quality and some have a deeper feature set, more expansive options or inclusion of third party research data that adds to the depth of the insights and comparisons that can be made as well as contextualize insights against demographics as well as media saturation and spend.

As this market expands and enters the big league what is really missing are industry standards. Conduct a sentiment analysis of the same terms in two or more different platforms and you can expect to get wildly varying results. The reason is partially inherent in the subjectivity of language. (What is social listening if it isn’t linguistic analysis?) But at every step along the way: rules that govern how data is collected, sample size and finally the analytics engine itself vary from platform to platform.

In the race to develop the best product we run the risk of undermining the value of the service if we don’t address the need for standards.

Image: Robert Egert, 1992, Pinocchio, 72″ x 72″, oil on canvas, collection of Mary Ziegler

Share this article

Invention, Reinvention and the Wheel

Working with my team today on a new interface that uses a horizontal transition between pages. The entire site is designed using just HTML5 and JQuery so there’s no Flash to worry about.

It’s another example of how interaction design can largely abandon the concept of pages in favor of a more responsive interface. But how did we get here?

When I was first educating myself on software design, one of the first concepts that I cam across was the idea of control systems. This generally refers to hierarchical relationships between key parts of a logical system that govern which parts of the system give out orders and which parts respond to those orders.

This is what prevents a malicious website from taking control of your computer. It works because in the hierarchy, the operating system is above the browser, and in turn, the browser software is above the website. The OS can’t be controlled by the browser but the browser can be controlled through the OS. (You launch or quit and application via the OS, not the other way around.)

From an end-user perspective, these relationships are somewhat intuitive through common convention, however from a ux designer’s perspective these hierarchies are what delineate the possible from the impossible in design.

The recent history of interaction design can, in large part, be described as the blurring of these hierarchies.

The two key factors at work in this process are asynchronous web programming and app culture. The first eradicated the concept of the web as a series of pages in favor of a dynamic display that can be continually refreshed based on user actions (vs. hyperlinks), and the second changed the act of downloading and installing new software into a casual act from what was previously a considered purchase.

Illustration: Dominance hierarchy of a single population of elephant seal males during the mating season, from From Marianne Riedman, The Pinnipeds, page 206.

Share this article

Usability is a Contemporary Mythology

Milan Kunk: How we adapt to machines and compuers is anything BUT intuitive despite the a=obsession with the term usability

How we adapt to machines and computers is anything but intuitive despite our obsession with the term usability

Recently I have spent quite a bit of my personal time helping people look for jobs. Call it my contribution to the failing economy or just the fact that I hate to see single moms on the street. At any rate, as you might guess, my first point is to help friends negotiate professional networking sites and to generally make their profiles visible to the companies and recruiters that are seeking to hire people with their skills.

For those of us in information technology, advertising and other digitally aware industries, this is a no-brainer and generally understood. However it is not the case for many people who work in other fields such as education, healthcare delivery, and social services.

It is a constant source of surprise to me how many people have no clue how to use social networking sites to their professional advantage despite the fact that most of them are regular users of facebook. After spending time walking them through steps such as taking and uploading photographs, adding biographical and resume entries and creating keyword sets a single observation has emerged: It’s all about how you handle frustration.

We are all confronted with new interfaces that are challenging and disorienting. It is part of the process of UI evolution that new patterns and paradigms are introduced and before they can feel intuitive they must be learned.

There is nothing intuitive about interacting with a computer. It is all learned behavior. Systems can feel intuitive, but that’s because their conventions conform to a pattern that has been previously learned.

In fact, we are all learning and relearning how to interact with machines all the time. We are constantly updating our knowledge, expectations and sense of normalcy. Once a new pattern is introduced it must be learned before it can become internalized: similar to muscle memory that is experienced by a violinist who intuitively knows where to depress a string to get the right tonality.

What does vary is the way we adapt to new interactive patterns. Here are two examples of adoption and resistance to change:

• Blackberry user has adapted to using an input keyboard that is tactile and refuses to move to a touch screen interface because they have become accustomed to feeling the keys in their finger tips and cannot easily adapt to a visual-only feedback system inherent in the iphone and android model of text input

• Website user is accustomed to finding a particular function interface, such as a button in a particular place. If, as a result of redesign, the button is moved, they become agitated and frustrated when they need to interrupt their task to find the new pattern

These examples point out two distinct classes of user resistance: The first is based on an established pattern of feedback (in this instance it is physical but it could just as easily be visual or audio). And, even though I am no fan or Blackberries, it is completely understandable.

The second example is more interesting. It is about a tolerance for interruption and constant adaptation to new behavioral patterns (vs. physical feedback).

What I am positing here is that how a user responds to the interruption of a task is a good predictor of how well they will be able to adapt to new technology. A user that is able to pause and switch focus from the task they are trying to accomplish to the means by which that task is attained and then back to the task itself will be able to learn the new UI pattern. Other users find the interruption to be intolerable will find it frustrating and may interpret the challenge of having to change focus as a direct threat to their goals.

What this points to is the fact that all of us are constantly adapting to technology. As my tag line says, technology changes what it means to be human. Our reactions, interpretation and behaviors are formed in large part by our expectations of what results from our actions.

I think it fair to say that nothing on a screen is truly intuitive. Particular designs just seem that way because they incorporate patterns that we are accustomed to.

Share this article

Hootsuite Impressions

Hootsuite interface elegantly combines OS conventions with that of web-based browser UI to resul tina new, transitionary state.

I just started using Hootsuite as an indivdual user. It does an impressive job of providing an extensible platform to aggregate social network activity across channels for individuals and presumably for smaller more agile marketing and PR organizations. The web-based ui design is among the newer crop that straddles browser-based aesthetics with client app standards. (If this sounds like jibberish, just think of Panic Software’s application Coda, which, like Hootsuite mixes user interface conventions from both operating systems and browsers. The result is a new transitionary state that, like mobile apps, mixes web and application standards to produce a result that feels as responsive as a resident app while pulling data from the cloud in real time.

OK now the downside. The application is still way beta with bugs galore. This is excusable except for the security issues it brings up and the fact that it is extremely powerful in terms of its ability to ramify your message footprint. One false move (intentional or no can wreck havoc).

Share this article

Why Not Balsamic (Not a Question)

Balsamic is a cool applicaiton but that doesn't stop me from hating it for all the standardization it imposes on the UI design process. Plus the fact that people who have no imagination or understanding of UI design can create acceptable UI designs that often do more harm than good to the process.

Turn back the hands of time, way back to the early days of the dot com boom. Web design in those days was devoid of templates real and imaginary. End users had no expectations and web interfaces ran the gamut from the audacious to the beautiful to the idiotic. Any new project was a chance to establish a new paradigm. And all bets were off.

Keep in mind that in the early days, web browsers were advancing and leap-frogging each other with a rapidity that made any design essentially obsolete within six months to a year. And even if it didn’t become obsolete, innovative new UI features, such as mouse-over effects, expanding menus, etc. were strong motivations for web sponsors to invest in redesign efforts.

I still remember vividly the ABC News site of the late nineties that featured the navigation on the right side of the browser. Eureka! More people are right handed, therefore this is a more convenient design. (They’d designed it to remain in sight regardless of the size of the browser window.) I was busy sharing the interface with my clients and team-members until one day soon after its release they flopped it back the left side, just like every other website.

It was a milestone day, like the day your favorite corner store closed and was replaced by gap or a starbucks. The day that conformity kicked in and a reign of standardization began.

Which leads me to my complaint about applications like Balsamic (For those of you who aren’t familiar, Balsamic is a template-based tool that allows people with no discernible visual skill to create UI mock-ups by arranging pre-made elements such as buttons, navigation tabs, form elements, etc.)

Balsamic has, depending on your point of view, opened up UI design to anyone with an interest, empowered sponsors to get hands on in the UI development process, or rendered the skilled UI/UX designers’ role irrelevant.

Perhaps it does all three of these things. But from my perspective, the larger issue is that it reinforces a standardized approach to UI design that will stifle UI innovation and further limit the kinds of interactions that we can invent or imagine.

Creativity is an essential component of innovation. And in order to remain relevant, designers must prove their worth by demonstrating true innovation, elegance and usability in the interfaces they envision.

Share this article

Bifurcate Me (again)

Rats in the works, here pictured, the front end developers and creative staff working like the Dickens to complete twice the work as befoer in the same amount of time! Technology is supposed to make things easier for us--not more difficult and time-consuming, right? But expanding coverage to mobile, tablet and for God's sake now the Kindle Fire is going to make the creative and user experience teams jump into a lake. That is, of course, if they aren't put out to pasture by lesser-paid equals in other continents.

Disappointed once again by the false promise of responsive design, CSS and syntactic design.

Our current project is nothing but a content-driven website–not an app or form-driven experience. So I wonder, why is it so difficult to create a mobile instance? Why is it that we need to create an entirely separate instance of the site? My goal was to implement the site using responsive design best practices; using device detection in combination with separate style sheets. But alas nothing is really quite so simple.

The developer team tells me that the time required to make a single set of files display correctly across devices will be so much greater than just creating a second set optimized for mobile.

But I know that doesn’t take into account the time and coordination required to maintain two separate sites down the road: when there’s a copy change, a new graphical revision, personnel changes, press releases, etc. Every one of them is going to require that each change be made twice and then edited and proofed. Everything times two. There’s got to be a better way.

I’m told the reason has to do with the fact that our site integrates JQuery and that means that once we start implementing across devices it’s going to get very buggy. I believe that too. But I just wonder, when’s the efficiency on cross-platform compatibility going to kick in on this?

Share this article

Code and Fix My Waterfall

Today I gave an informal talk on development process models. I started by explaining and contrasting waterfall method in contrast to the code and fix approach. Most of the people in the room had never heard of either of these terms which was surprising considering that they are either in project management roles or part of an interactive creative team.

What became apparent through the discussion was how we use a defacto code and fix approach for all of our internal projects and a pretty sequential waterfall for all our client work.

The real question is, how much of this has to do with formal reviews and how could that change?

Share this article

Pharma: Head in the Clouds

Thinking today about cloud computing and how the successful marketing of the concept has impacted my clients’ beliefs and expectations.

Software as a service and cloud computing is on everyone’s lips but it is surprising how much confusion there is about what it is. This is surprising considering how much good information is available on the topic. Perhaps it’s part of the downside of the successful marketing campaign around the cloud: non-technical clients seem to think it’s something new despite the fact that its been around for a long time.

Meanwhile in the healthcare industry, cloud computing represents a major challenge to the existing infrastructure that’s used to house and manage patient data. Pharma has gone to great lengths to ensure security, hygiene and compliance around this sort of personally identifiable information and it will take more than a marketing campaign to change existing relationships between database vendors and IT departments.

From a design and production perspective the implications of cloud computing are huge: especially for those of us involved in one-to-one marketing and dynamic health applications. Whether we design our applications for a web services/cloud model or for a traditional model will significantly impact design. Today that means applications that require data storage such as tracking tools and health diaries that will benefit from seamless access to data across disconnected wireless devices.

Share this article

Design Challenges with Agile Prototyping

I love these mobile app stencils not only because they work so well but also because they remind me of the stencil kits we used in shop class eons ago

In the rush to release mobile apps and the proven success of rapid prototyping its no surprise that design has had to adjust to an agile methodology. This also means that the project sponsors are far more involved in design decisions than ever before.  It is in the nature of mobile design to rely on the OS far more than in browser-based application design. This implies (and demands) full integration of interaction design with software development in a way that hasn’t really been popular since before the emergence of the web.

Not a bad thing if you ask me.

Share this article