UX and Agile

UX Profession - Research Project

I know some of you have heard me talk about this mythic UX research project….and well – TA DA! Here it is!

I'm looking to collect minimally 500 responses from UX professionals, product managers, business analysts and developers to better understand the perception people have of UX-ers. From being a UX professional, I've witnessed some pretty interesting things, and from talking to other UX professionals, I've heard similar stories. I came up with this idea because I believe that because UX is such a new field, people working in it have a hard time determining how to fit into the team structures. Boundaries are often fuzzy – even within a creative team – and we just don't really talk about them.

With that said, I've included the links to the various survey types below. Please feel free to forward along. I'll be forwarding these to other groups and such as well. 

UX Professional Survey: https://www.surveymonkey.com/s/ux_professionals

Developers: https://www.surveymonkey.com/s/ux_developers

Product Managers, etc.: https://www.surveymonkey.com/s/ux_business

 

A special thanks to Cameron Craig and Jennifer Loring for helping me with the wording and structure. I appreciate it!

Thanks in advance for your help! And feel free to pass it along!

Tuesday, November 27, 2012 | Permalink | Comments (0)

Is Navigation and what we consider usable intuitive or learned? Part 1

I've been wondering for a while if navigation on a site is naturally intuitive or learned. In usability tests we like to think that we are collecting user feedback to create intuitive systems. And we are in some ways - we are collecting feedback to make a system better. However, are we REALLY creating intuitive systems or are we creating systems that require previous knowledge (cultural or otherwise) to use?

At times we take our life for granted. We wake up in the morning, have a coffee and toast, read the paper, go to work, and so on. However, how did our life today really evolve to how we live now? What made this the pattern of life? We don't realize how defined our life and culture is. We deeply believe that we make decisions. But do we?

So let's think about a light switch for a second. We believe that it is intuitive to use. Now for our culture, it is. But is it truly intuitive? Meaning, if you have never seen a light switch before, would you know what to do with it? We see a light switch from birth onwards and learn how to use it by watching others flip it on and off. When we can reach one - we have an idea of what to do with it and repeat actions we have seen others do. So - is a light switch really an intuitive device? Would someone who has never seen it before understand it?

Another example is a steering wheel. If a child is in a car from early childhood, he or she learns how to steer a car by watching the parent. However, let's say someone NEVER experienced what it is like to be in a car and was presented with a steering wheel. Would that be intuitive to use? I'm not entirely sure.

Now if we think about an iPad or touch devices. We watch TV shows like Star Trek or movies like Minority Report where there are touch screens. Isn't that like watching a manual to learn how to use an object? Is that truly intuitive or are we, in some ways, being trained to think that this is how we use futuristic devices?

Voice control is probably the most intuitive way to use something - we just order it around. But again, is that trained behavior? You can order around a robot - but you can't order a rock to move and you can't verbally order an animal to surrender to be hunted. 

This blog entry is the first of a series, and explores what I believe it means for something to be intuitive behavior versus what is learned behavior based on language and culture. I believe most of what we see today in usability is based on learned behaviors. If we were not socialized to be as we are today - I believe all of our devices would be useless. As an aside, this also raises the question regarding past cultures - do we judge how to use ancient tools based on our modern culture and understanding? If a device is intuitive based on cultural constructs - and ancient cultures were different from ours today - doesn't it logically follow that their devices would be as intuitive to us as an iPhone would be to someone from a remote village in the Amazonian jungle? 

In each section, I consider what we consider to be innate behavior and intuitive - and question if it is truly intuitive. These are purely examples of how we are conditioned to understand the world and use objects. If anything, I'm hoping that you will join me in this thought experiment and maybe adjust how you see what is intuitive as well.

 

Chimps and Gorillas - what is innate behavior?

Many researchers spend hours watching chimps and gorillas use things and figure out how they work. They ponder how a chimp understands an exercise that a 2 year old can do. However, are we asking the chimp to do something learned or intuitive for a chimp, or is it from the chimp's perspective, just a ridiculous behavior being executed to get a banana? (If someone has the answer to this let me know. I'm not a researcher - just pondering this as a casual observer. I may be completely off-base here and would like to get more information on this first hand.) Based on my understanding of what is being observed, the chimps are "learning" what we value as intelligence as trade for a banana. So for that banana, they do things our way.

If you are living in a cage eating pellets, going along with this game isn't a bad idea. But is this type of activity really demonstrating intelligence overall? Shouldn't we be defining intelligence beyond how we define intelligence in our modern human society (through activities, interactions, etc.)? Are we observing behavior that is really innate? Or is this behavior really innate if you have lived in a modern human community (observed at such an early age, it is part of our "programming" for lack of a better word, and we don't even realize it)? And it becomes "innate" or learned by another species because the animal is being rewarded?

We teach gorillas sign language to communicate with us and express their thoughts. However, if you think about it - we are giving them words and concepts to use that are based in our modern human experience. How do we know if gorillas communicate different concepts with each other in a different way, because their way is truly beyond our own experience and society? How do we know if these human concepts are structuring their world and beliefs into something we can understand, and we are losing out on their experience because they have no tools to communicate their experience to us? They are expressing their thoughts according how we define the world thru language. But is this the true gorilla experience? Do they have a different world view that we will never fully be aware of because they don't have a spoken language that we can discern? Do they have ways to express concepts that are outside human experience? Are we being arrogant to assume that their experience is less than one of that of a modern human?

This gets me to wonder - why don't we work to try to understand them in their "culture"? Why do we need to use our culture as the center to judge all other "cultures"? Is what we consider to be usable and tests of intelligence really applicable to humans only? Don't we miss something with this? Aren't we conditioning these animals to do what we want?

 

Language and how we see society

France has a council to regulate the French language called Académie française. Actually, most countries today have a committee to regulate and define the language. These organizations don't just keep the language "pure." Language and culture are closely tied in general. How members of a society express their thoughts and values is dependent on a language to unify their experiences. If you think about it, by defining the language, these organizations are also shaping the culture of those various countries. Language influences how and what we think.

Language also influences how we view concepts. We have a single word for love; other cultures have dozens. C.S. Lewis wrote The Four Loves, which outlines the 4 types of love in Greek.

  • Storge – affection
  • Philia – friendship
  • Eros – romance
  • Agape – unconditional love

In the US, we obsess about Eros. This may partially explain why Americans are obsessed with romantic relationships and sex and overlook other types of relationships. Love is Valentine's Day, candlelit dinners, 'til death do us part. We rarely think that love is about friendship, affection or unconditional family love. Women typically dump their friends in favor of a boyfriend (which works until a man dumps them). Men have friends, but search for that one woman that rules their world - and does the same thing to their friends. In modern American society, we believe that it is ok to cancel an outing with friends in favor of a date. Generally, we forget that love can be a warm family dinner, spending time with a grandparent, cuddling a child. This oversight may be attributed to how we define the word "love." We have a single word, and we have attributed at least 4 types of love to it - talk about oversimplifying a concept and at the same time making it more complicated! This is just one example of how words truly shape how we view the world because it reflects (and also drives) our culture, ethics, values.

The US doesn't have a group to regulate and define English. That also speaks to our culture not being defined. And it is a mixture and free for all. I'm not implying this is a bad thing - if anything, it allows for creativity and an openness to live as you want, which is a cornerstone of the US based on the Constitution. By allowing creativity in language, we are enabling a more creative society that is fluid and changeable. However, this idea of freedom also influences how we view the world - how we use objects around us and how we expect them to work. We believe in personal freedom and expect the ability to have experiences defined so that we can customize them. That is fairly consistent to our experience daily - we want it our way and we feel we can define our future because we define our own language.

Language influences how we view the world, and in some ways, it influences what we view as intuitive. How a society perceives the value of language also influences what we consider to be intuitive and what we value.

 

Culture and Religion

Beyond language, we are programmed through culture, religion, the media. We are defined by social conventions. And we take this for granted - we don't even realize how deep this all goes. From my own experience, I grew up deeply Catholic - church every week, Catholic high school, constantly going on retreats. A crucifix to a Catholic is obviously a symbol representing Jesus's death and considered holy, revered, and respected. However, to someone who is not familiar with Christianity, the image of a crucifix is truly horrifying. Similarly, so is the crown of thorns. When I was 7 and not really exposed to Catholicism yet, I saw a very graphic picture of Jesus wearing the crown of thorns in a religious shop. Upon seeing it, I was immediately terrified, screamed and had nightmares about it for weeks. I wasn't yet programmed to accept the crown of thorns image as holy - it was outside of my experience. And I didn't yet learn that I shouldn't respond that way.

Today in US culture, we are ashamed of going the bathroom (we have stalls separating us in a restroom). Going to the bathroom is a private moment. It is apparent from archaeological sites that in ancient cultures, people weren't ashamed of it - they would socialize when they were there! In ancient Roman baths, there was a communal bathroom, with dozens of place to go the bathroom around the edge of the wall. Apparently, the Romans in the baths may have been immersed in a great conversation that would continue to the bathroom. Going the bathroom was like eating a meal or changing. So what happened where we see going to the bathroom as a private act?  In some ways, we could say that our hatred of our bodies influence this view. What happened to make us ashamed? Unbridled Christianity during the Middle Ages is a factor. But are there others? What would make us define the bathrooms in the Roman baths unusable, and they would probably see our bathrooms as unusual (why potty alone?).

Another example is doorknobs vs latches. When I was a little girl my uncle used to tell me that the difference between Europe and the US was latches and shallow toilet bowls (which alone lended itself to a lot of literal potty humor). I got further confirmation recently about the latches/doorknob AND toilet bowl issues from a friend from Germany. She told me a story about how when she was in the US as an exchange student, she didn't understand how to lock a doorknob. With latches you can see if a door is locked or not; with a doorknob - well - she didn't get it. It wasn't usable. Someone had to show her. The deep toilet bowl story isn't too appropriate to repeat here, but to sum it up - the deep toilet bowls in the US are great. Honestly, there is no better or worse approach to either issue (well, honestly our deep toilet bowls are better for many reasons I won't get into here). In the end, it's the same functionality but a different approach for having someone open a door (no puns intended for both). And you get used to using what's available to you - it is more intuitive to live that way; living another way is a foreign concept.

 

Devices and manuals

When we buy an electronic device, we typically get a manual that we need to read to understand all the available features. We study the manual or reference it when we have a question - and most times we consider a device to be intuitive if we rarely reference a manual to achieve our goals.

Intuition is defined by Merriam Webster as "quick and ready insight 2a: immediate apprehension or cognition"

To sum it up, if you must touch a manual to use an object, it's not intuitive.

We consider the iPhone to be intuitive; same as the iPod. The first time I held an iPod, I couldn't figure it out. I'm not a stupid person (at least, I like to think so). I didn't understand the buttons, touch dial, or display. I needed to be shown how to use the device by an Apple employee. The employee praised Apple for creating an intuitive device. I just had a blank stare - because in a way, I was being told that I was so stupid, I couldn't figure out something intuitive and so well designed.

This was also true for the iPhone. I needed a training session to use the touch screen, swiping, the whole thing. I have personally witnessed people watching me use my iPhone, seeing me use a feature that I was shown, and ask me to do that again so they could learn what that feature was. I frequently call people to learn how to do things on my phone. If you can't figure something out on your own, having an "ah-ha!" moment, by definition - that means it is not intuitive. Apple may be defining new conventions - which is great - but honestly, by definition, it's not creating intuitive devices. 

 

Needing training and demonstration to use a device means that it's not intuitive. 

We are being socially conditioned to use products. Apple designs beautiful products - no doubt. However, because the products are cool, we get attracted to the shiny object, and we are being socially conditioned to use these products. If you know how to use them, you are then in the "in crowd." If you do not use the products you are considered to be a laggard. And we think that because we use these products we are so far ahead of the curve, when in some respects we are being trained how to use technology and just look at the laggard as the poor thing who can't keep up (when in fact, the laggard may be thinking these technologies aren't intuitive to use - and they aren't!). 

Now we look at navigation on a Web site. For the past 15-20 years, we have been trained to use Windows. Microsoft Windows is everywhere - work, home, school. I remember being at MIT using Project Athena. I had to use UNIX and always got out of that environment to XWindows for a better interface. Essentially I wanted to use Microsoft Windows because I perceived it as being easier to use. I think it was only because I didn't need to understand command language. Programming scared the life out of me - not only because I was a lousy programmer, but because I was afraid of my classmates who already knew how to program like an ace and saw me as an idiot for being at MIT without this previous knowledge (this brings up a debate about why go to school and take a class if you already have the knowledge - but I digress). With XWindows and Emacs, I could just type and see results. Was this necessarily me thinking this was easier? No. I was avoiding machine language because it was more difficult and took what was presented as an "easier" option. Honestly, it wasn't that intuitive to use. I needed more technical friends around to help me all the time. I found it intuitive because I was less afraid and intimidated of using XWindows than Unix command line language.

Using Microsoft Windows is difficult. Try watching an older person use Windows. It's sad and entertaining at the same time. They try so hard to make the computer work - but they can't because you need previous knowledge to use the computer! We don't realize how we have been trained to use menus - bars at the top of the screen, bars at the bottom of the screen. This isn't intuitive; if it were, people wouldn't take computer classes. We make people think they are stupid not to understand how to do things on the computer - of course they can't - it's simply not intuitive. It's learned behavior.

Let's talk about Windows 8. Windows 8 is a departure from the standard Windows menu-based navigation. It's scary to use because it's a brand new paradigm. 

Here is a review:  http://blog.laptopmag.com/usability-expert-windows-8-on-pcs-is-confusing-a-cognitive-burden

I personally haven't used Microsoft 8. However, based on everything I have heard and seen, I'd like to use it to see how Microsoft has changed its paradigms. Is this change really better or worse - no. It's just different. We may consider it not usable because it's a different paradigm. But is it a worse paradigm? Not sure. I think the jury is out on that because we have been so programmed to use the older approach of Windows - and a new approach may be more usable, but not immediately seen as intuitive because of all of the training we have received. 

Human minds really don't multi-task. Humans focus on one thing at a time. Original computer interfaces (specifically, the Cannon CAT) allowed a user to work on one document at a time. Windows even followed that model in the early days of computing. Over time, culturally, we were told that we needed to multi-task to do our jobs. I'm not sure how someone can successfully focus to create presentation and a document and spreadsheet at the same time, but we were encouraged to do this - and the MIcrosoft interface supported this concept. It also encouraged us to have multiple windows open simultaneously. Were any of us actively working on these documents? NO! Most likely documents are open for reference - or for later work. All this does is make a messy desktop and sloppy use of system resources. Is it usable? Again - it doesn't really map to how our brain works; it maps to how our culture WANTS us to work. 

So is Windows as it stands intuitive? I'm guessing no. It's learned.

 

Propaganda by Edwad Bernays

Propaganda is a book that is required reading for anyone who works in advertising, marketing, or any other product creation company or role. Essentially, the book is about how choice is made for us by an "inside government." In some ways, this is true.

The movie "The Devil Wears Prada" alludes to this:

Miranda Priestly: [Miranda and some assistants are deciding between two similar belts for an outfit. Andy sniggers because she thinks they look exactly the same] Something funny? 

Andy Sachs: No, no, nothing. Y'know, it's just that both those belts look exactly the same to me. Y'know, I'm still learning about all this stuff. 

Miranda Priestly: This... 'stuff'? Oh... ok. I see, you think this has nothing to do with you. You go to your closet and you select out, oh I don't know, that lumpy blue sweater, for instance, because you're trying to tell the world that you take yourself too seriously to care about what you put on your back. But what you don't know is that that sweater is not just blue, it's not turquoise, it's not lapis, it's actually cerulean. You're also blithely unaware of the fact that in 2002, Oscar De La Renta did a collection of cerulean gowns. And then I think it was Yves St Laurent, wasn't it, who showed cerulean military jackets? I think we need a jacket here. And then cerulean quickly showed up in the collections of 8 different designers. Then it filtered down through the department stores and then trickled on down into some tragic casual corner where you, no doubt, fished it out of some clearance bin. However, that blue represents millions of dollars and countless jobs and so it's sort of comical how you think that you've made a choice that exempts you from the fashion industry when, in fact, you're wearing the sweater that was selected for you by the people in this room. From a pile of stuff.

And this is so true. As much as we believe we have choice in society, do we? Are the decisions that we make that define us really decisions that are defined FOR us to make? We believe we are choosing a blue sweater, when in fact, someone else is offering a blue sweater to sell to us and we make a decision only between red and blue - not the sweater style or color offerings.

So does this mean that our culture is defined by someone else?

I had a hard time selecting quotes from Propaganda to prove this, and frankly, I just recommend you read the book. But here are some quotes to give you an idea of his point:

"We are governed, our minds molded, our tastes formed, our ideas suggested, largely by men we have never heard of."

"Vast numbers of human beings must cooperate in this manner if they are to live together as a smoothly functioning society."

 "It is not usually realized how necessary thse invisible governors are to the orderly functioning of our group life."

 "We have volunteraily agreed to let an invisible government sift the data and high-spot the outstanding issue so that our field of choise shall be narrowed to practical proportions."

"In theory, everybody buys the best and cheapest commodities offered him on the market. In practice, if everyone one went around pricing, and chemically tasting before purchasing, the dozens of soaps or fabrics or brands of bread which are for sale, economic life would be hopelessly jammed. To avoid such confusion, society consents to have its choice narrowed to ideas and objects broiugt to it attention through propaganda of all kinds. There is consequently  vast and continuious effort going on to capture our minds in the interest of some policy or commodity or idea."

"It might be better to have, instead of propaganda and special pleading, committees of wise men who would whoose our rules, dictate our conduct, private and public, and decide upon the best types of clothes for us to wear and the best kinds of food for us to east. But we have chosen the opposite method, that of open competition. We must find a way to make free competition function with reasonable smoothness. To achieve this socity has consented to permit free competition to be organized by leadership and propaganda." 

"Some of the phenonen of this process are criticized -  the manipulation of news, the inflation of personality, and the general ballyhoo by which politicians and commercial products and social ideas are briught to the consciousness of the masses. The instruments by which public opinion is organized and focused may be misued. But such organizations and focusing are necessary to orderly life."

It is all around us that we are given choices to choose from and if we didn't have this - we would be overwhelmed and unable to make a decision. This approach does assume the public is stupid, I won't deny that, but it confirms what I am saying here - our lives have been more or less decided for us by others (magazines, etc.). A cultural code has been established for us and we have the illusion of choice - as earlier confirmed by Miranda Priestly in The Devil Wears Prada. 

This cultural code is in the press, politics - everywhere. A few decide how we should perceive the world. We are presented with options where we choose which is best for us given our current society.

And this defined society provides the basis for us to consider items to be intuitive. 

 

Usability Research 

When people participate in research, they don't create new products themselves. The researchers are looking for problems that they observe (or they perceive and define as problems) and think - why is this person doing this workaround? Is there something this person could be doing to make this easier? People are doing work in the way they know how. And designers and engineers create a solution based on their experience and what they believe will work. They leverage design conventions used in other products in a different way - rarely is something truly new created. We think it is new through marketing and messaging. A phone is a phone, or phone with TV, or phone with Internet. It is cool - but is it a true breakthrough as a concept? Combined devices started long ago - what were the furniture hi-fis of the 50s with a built in turntable and radio? We may change the combinations, we may add new technology, but the general concept is the same - multi-use devices.

We look to make a product intuitive or usable in the context of modern human society. We don't always consider cultural factors unique to an area - designers tend to work with more generalities. A good example of this is the iPhone (apologies that I keep picking on that device). It was designed in Cupertino, where the weather is fairly pleasing all year round - it is rarely below 40F.

Shortly after buying a phone, I went to Boston at Christmas to visit my parents. I remember it being cold and snowing - typical weather for the Boston area. I was all bundled up in gloves and coat, and needed to call my parents while I was walking to the MBTA station to go home. I desperately tried to unlock my phone so I could call them while wearing gloves but I failed. All I thought was - are you kidding me? I can't use the phone in the cold? I have to have numb fingers to use it? 

After I figured out that I could get the phone to work without gloves (and I had numb fingers), I immediately called my friend who works at Apple to understand if my experience was in fact designed. He said yes - the touch screen requires human finger heat for it to work. I asked him if the designers ever considered someone using the phone outside in a cold climate? Having some type of attachment? I mean, 50% of the world is in a cold climate. And with my Palm I could type wearing gloves (clumsily, but nevertheless, I could type).

Silence.

 

Real usabiity and intuitive use

This is a very long blog entry that may grow to something else in the future and I plan to publish parts over time (obviously, I have a lot to say about this). However, I'd just like to sum up everything I was saying and leave you this thought. If we went to a village where there has been zero exposure to technology or devices and usability tested our modern sites and devices, would they be considered to be intuitive or would they require training? Would they understand our technology? Would they need to have some of our modern human culture behind them to "get it"? Is a technical item being technical itself a reason to make is unusable? In my profession, we make devices work for anyone - so that is not a reason. Anyway, it was something to think about.

Thursday, November 15, 2012 | Permalink | Comments (0)

UX Design Doesn't Just Make Things "Pretty"

The design field is changing. A couple of years ago, I was at a design conference and one of the speakers clearly told us that design heros no longer existed. He said that designers had to move towards being a leader to create a solution. It's true. We aren't creating art. We aren't making a pretty picture. We are creating solutions to business problems.

To create a solution, that means we, as designers, need to:

  1. Have a defined problem to solve - and sometimes that means we need to help define the problem
  2. Understand the problem we are solving - all aspects
  3. Faciilitate discussions with all team members to get to the solution

In some ways, designers are being called to take on some of the role and knowledge of an engineer. Or are we assuming the role of our first cousins, the Industrial Designer? Or are we more like an Architect for software rather than a building? Or something different? Which role makes more sense?

There are a number of jokes on the Internet about how engineers see designers and designers see engineers. This is probably the best one ever (See the site, Into the Painted Grey for the original. This has been passed around the Internet many times over so it is impossible to know who the real creator is.).

 

I think this image is hilarious - and in some ways, not too far from the truth (which is probably why it is so funny!). But more and more, the role of the designer is drifting away from being the "painter," making things look pretty to become a solution creator and a type of engineer. 

 

What is engineering?

One perspective - Preparing for the next step

Making a product is about preparing for the next step, always moving towards production. This preparation for that next step is where documentation and engineering happens. Most projects follow the process and phases: exploration, requirements, design, execution/production, testing, distribution. Engineers usually do their work in the exploration, requirements and design phases; construction and manufacturing works in execution and production. This is true of all industries except software - where execution and product is performed by software engineers, developers and programmers. 

Designers typically work lock-step with engineers in the process, preparing documents for manufacturing or development. Using this model - designers and engineers are part of the same group, defining what the product should be. 

 

A formal definition

According to Wikipedia:

An engineer is a professional practitioner of engineering, concerned with applying scientific knowledge, mathematics and ingenuity to develop solutions for technical, social and economic problems. Engineers design materials, structures and systems while considering the limitations imposed by practicality, safety and cost.[1][2] The word engineer is derived from the Latin roots ingeniare ("to contrive, devise") and ingenium ("cleverness").[3][4]

Engineers use science and research to create a solution. Most engineers don't necessarilly do the actual building of a product (some know how and are able to do that, but usually they are able to leverage science to create a solution thru plans and drawings) - they create the plans to make it happen. Software is an exception, where engineers work more directly, writing code (plans) to optimize data flow. 

Traditionally, engineers think in terms of optimizing; designers think in terms of attractiveness. However, in today's world, the market doesn't support a clear separation between the two - consumers want well-built, good looking products with optimized efficiency. An engineer has to have some design-sense, and a designer needs to have some engineering sense. Apple could be considered a trailblazer with this concept - creating something that works well and is well designed. Martha Stewart also strengthened this concept, along with Ikea making something well-designed and fairly well-built, affordable.

This is where a customer's or user's experience becomes so important. Here is the definition of user experience (from Wikipedia): 

ISO 9241-210[1] defines user experience as "a person's perceptions and responses that result from the use or anticipated use of a product, system or service". According to the ISO definition user experience includes all the users' emotions, beliefs, preferences, perceptions, physical and psychological responses, behaviors and accomplishments that occur before, during and after use. The ISO also list three factors that influence user experience: system, user and the context of use.

A UX designer is solving social problems - the core problem of how a user interacts with a system. To sum it up, he is designing a system. Given the earlier definition of an engineer - I think on this alone, we could safely say UX is less about design and more about engineering, but let's look at some other examples.

 

Separating design from engineering 

This is a lively debate in all fields. There is an article at MCA Cafe that outlines the difference between the design and engineering disciplines so that people who are hiring a designer or engineer know what they are getting (summary: engineer makes it work; designer dresses it up). There are a number of forums as well that continue this debate.

To sum up the findings:

The engineer makes sure that the product can be manufactured; the designer makes sure that it not just looks good, but it's ergonomic, usable, marketable, sellable, etc. 

This puts ergonomics and usability into the field of design; however, if we explore the definition of ergonomics:

At its simplest definition ergonomics literally means the science of work. So ergonomists, i.e. the practitioners of ergonomics, study work, how work is done and how to work better.

And usability is:

ISO defines usability as "The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use." 

With these statements and the definition of engineering, one has to ask: are ergonomics, human factors, and usability indeed engineering? Isn't it beyond design and "dressing things up"? 

However, is separating design and engineering really all that easy? Making something marketable means that you need to understand the market and have a handle on its sociology. Many "designers" I know have a deep knowledge of psychology, sociology, and social research methodologies. Engineers, by definition, work with materials, but they also work with the "softer," people sciences (creating workflows, optimizing how companies operate). This makes the successful design of workflow and interfaces a form of engineering.

 

Product Design and UX Cousins - Industrial Designer/Design Engineering

UX Design is a close first cousin of Industrial Design - it could be considered Industrial Design of the Web/Mobile/Software. Industrial designers work with engineers to create new products. 

However, industrial designers must have an understanding of the technology when designing. They need to understand what materials can do - how much they can bend, how compact a chip can be to achieve better usabiiity and ergonomics and aesthetics. They need to understand the psychology of people who will use a product and what the product will be used for. By working closely with an engineer, the designer learns more and more about materials and capabilities, giving a broader understanding of what's possible. But sometimes the engineer needs to determine how the form of an object could change - smaller, rotate, etc. - to make a better design. There may be something about the material or object that only the engineer will know. This makes the designer/engineer working relationship really a partnership.

Maybe this relationship should be redefined with the Industrial Designer being the "people engineer" and the Design Engineer being the "materials engineer." For optimizing the process - the traditional "Designer" may suggest that the process flow one way to make it better for users based on what they need, and the traditional "engineer" would figure out how to get the chip or information to do that in a optimal way.

Considering this, both are engineers - just different focus. 

 

Architecture and Construction - similar yet different

An architect creates a vision for a building or structure. He understands about materials and design and how they can work together. He develops an initial sketch and various architects and engineers at a firm complete the work. They consult with construction teams to learn what's feasible. In some ways, the process is similar to product design - there is a team working on a project with different areas of focus. Where it is different is that the architect, in some ways, is a hybrid of the traditional engineer and a designer. He needs to understand who will be using his structure, why, and how he will interact with it. He needs to understand materials - not in detail (that's a structural engineer) - but enough to create a sketch of something that can be built. 

Is the architect an engineer? Well, architecture is offered in many engineering and design schools. The architect needs to understand science and art and people. The architect also has to understand psychology and sociology in order to desgin a great building. 

The UX designer is very similar to the architect - they could be considered cousins as well (not first cousins, but cousins). Both need to understand technology, design, art, sociology and psychology. The difference is that architects create a vision and lead a project team to bring this vision to completion; UX designers rarely own or lead a vision to completion (typically that role goes to the business in the form of a product manager). 

This is why UX is closer to engineering than architecture. Architects oversee a vision; UX is part of a team creating a product responsible for the how the user's will interact with a system.

 

Conclusion

If UX Designers didn't have rquirements to follow and literally just made interfaces look pretty - then I'd be happy to agree to and acccept being just a designer. However, UX designers:

  • Work with requirements
  • Understand technical aspects of how systems work
  • Create workflows
  • Ensure that a proposed design can be "manufactured" or developed
  • Ensure a product is usable
  • Research user trends and actions
  • Understand the users to the point of being a user advocate
  • Ensure that a product will appeal to a market

Given all of the definitions above, that defines an engineer that's focused on people using an optimized system. It goes well beyond design and making things "pretty."

I guess based on this, the discipline of User Experience Design is a type of engineering. 

I'm curioius to hear your perspective. Please share in the comments. 

 

Friday, October 26, 2012 | Permalink | Comments (1)

Follow the money - UX Independence

When we want to learn someone's true agenda, especially in politics, we follow the money.

  • Who is paying the Senator or Representative?
  • What is the donor getting from Congress?
  • How does that relationship work?
  • Who does that Senator REALLY work for?

In American culture, money is exchanged for goods or services; we work in a system of trade. For products, the exchange is for "what you see, is what you get." There's not really any customization available, unless the person or company selling the product is offering it. However, in the case of services, whomever pays the money is getting something back that benefits them based on their specifications. So if you own a house, and you pay an architect to add a porch or a greenhouse or whatnot, the architect won't be doing exactly what he likes - he'll be designing and creating a porch that will meet your expectations and needs, with his design flair added.

This makes you wonder if the same assumptions apply to UX professionals. Who are they working for? And does this person influence the team's work?

I think it does. If UX teams within a company were independent teams responsible for contributing to the bottom line and had metrics to measure success, users would have a better experience, spend more money, and generally, revenue would increase for any product. Otherwise, if the UX team is part of another group (business or technology), they are "managed" by them and aren't able to make all of their own decisions. 

 

We all do commissioned work

In a company, all employees are doing commissioned work; they are being paid to do work for someone else based on specifications. They aren't working completely on their personal goals; they are completing work to help an organization achieve its goals. Sure, employees meet some of their personal goals, but the goals are mainly driven by whom they work for.

Artists will sometimes do commissioned work as well, and they are basically selling a custom service.

To begin with, working on commission, creating a work of art on spec from scratch for someone other than yourself, is totally different than selling a finished piece at a show, at a gallery, or out of your studio. Selling a completed work of art is an event; producing a work of art on commission for another party is a relationship. Never confuse the two. - ArtBusiness.com

In the Middle Ages and Renaissance, royalty and nobles would commission artists to paint their families. Some of these paintings romanticized individuals and made the subjects notably more attractive. I mean, why would you make someone paying your way ugly? It's probably not a good idea if you like the nice meals and living in the castle or manor home.

Scientists (all types) can also be commissioned to do research work. Needless to say, one has to wonder about the integrity of this work because someone is being paid to prove a theory, idea, or concept or the results could be interpreted with a "spin." Most scientists will get a government or foundation grant to continue their research to remove outside interest, but getting commissioned to do research by a company means that the scientist is technically working for that company, and potentially it's interest. Altimeter makes it clear on their site that there is a high potential for a conflict of research for commissioned research.

Branding: Altimeter prefers that the research be branded to the company and not to Altimeter so that it is not confused with Altimeter’s own branded research. The less the commissioned research reflects the Altimeter’s brand, the less the conflict. - Altimeter - Commissioned Research Policy

The concern for conflict of interest for commissioned work goes across industries - from art to science and design. It's a fairly consistent - and valid - concern.

 

Internal UX Teams as Consultants

If a UX professional works in the product management/business team, then he is collaborating with them to make their vision a reality. UX provides insight into what will provide an effective user experience; the business provides direction as to what the product should do. Sure, we all work together, but the business team is defining the problem the team needs to solve.

I want to be clear that I'm addressing UX employees rather than consultants. Consultants have a very different relationship for whom they work. They are being paid for their expertise, but also getting paid to help get a project done. What's different about a consultant and employee is ownership - a consultant doesn't really "own" what he is working on; the consultant is a resource who raises issues, but he doesn't necessarily have responsibility to increase the bottom line (there is always a final decision maker/owner for that) or have insight into all aspects of a product as would an employee who works on a project every day, all day. Employees often assume that they are contributing to the bottom line and "own" a project/product to a certain level (meaning they have input into the project/product's direction). 

If the business team (product management team) funds the UX budget, then UX works for the business and needs to do what they want. If the business has a requirement, then the UX team will include it in their designs. In more democratic teams UX can give feedback, but at the end of the day, it is the decision of the business as to what is included/excluded for a release. 

As an example, I worked on a product where we were designing a My Account page. I was a UX person (employee) on the product management team. I gave some suggestions as to how we could display data and handle some of the functionality. However, the product manager had already made a number of decisions with engineering that were driven more by what made sense for engineering rather than what was best for the user. I was not included in any of the discussions. I continued making recommendations to make the experience a little smoother for the user, but I was told that the approach the business decided to take was the final decision - even though I had valid feedback. I voiced my concerns and risks, but the business made the decision. If you think about it, I worked as a consultant, providing advice, guidance, and benefits/challenges of a decision. 

The leader of this group later told me that I didn't own anything - that the business was responsible for revenue and metrics so it was their decision. That's understandable, however, why be an employee in a situation like this? I might as well have been an independent, outside consultant providing advice that may or may not be used. For UX to be a contributing member of any team, UX needs to be able to contribute to the team as an equal and have a degree of ownership.

Are all teams like this? Definitely not. I've had clients who are partners, respect my position and bring me in to give advice as to what to do. However, I've also been an employee where I was treated like an outside consultant. This is why at times UX professionals prefer being consultants - at least his role is well defined.

It is also the decision of the business to allow the UX team to include users in the development process because they are funding the work and it needs to be approved. I have been refused funding many times for user research activities. I consider research to be very important, but if the business doesn't want to include it - what can I really say? I can only advocate as much as I am an equal. 

Similarly, if a UX person is part of the technology team, and the technology team is paying for him, then he is working for the technologists. The technologists may be more open to user research and including their recommendations, but the bottom line is that UX is working for their interests. 

Product management and technology are usually separate teams so that they don't have a conflict of interest - they both represent their own needs and they are treated as more or less equals. They are both employed by the customer payments (revenue). The business may dictate the priorities, but technology decides how the project will be implemented. If IT owns a project completely, it will be too technology driven (most early IT/computer applications); if the business owns a project, the interests of the technology may be overshadowed. However, if UX is part of either of these teams, and represents the voice of the users as part of either team, the business is at risk for losing opportunities and revenue and better understanding its audience because UX is not an equal voice to the other teams.

 

The Irony - Customers are the one who are paying for you 

The irony of this situation is that it's the customers who pay for the services (or it's the investment bankers who fund the project - and want it to get customers and succeed - meaning extreme profits). It's the voice of the customer - or the actions of the customer and where their money goes that proves the success of the product. So if the UX team does some research and has a recommendation that the business doesn't listen to, the business is damaging the product. If you really want to hear your customer, you need to make UX an independently funded team in the organization, treated as an equal to the other teams and interests. It can't provide only services to a project. It can't be a filtered voice. UX needs to be equal to the business and technology teams and work directly for the customer and be funded by what the customer directly pays. 

 

Independence for UX

This is why the UX team needs to have full fiscal responsibility for its work. If UX had responsibility for the results, then there would be more input from users, the UX team would be have more invested ownership - not be just a consultant, and most likely, customers would have a more successful experience. The UX team would actually own the experience and be responsible for its success, have a set of metrics to meet, and there could be real research, rather than opinions, guiding the work.

Discussions about features would have a broader perspective where the UX team represents the needs of the users, the technologists provide cost-effective approaches to problems, and the business represents the bottom-line needs and is able to prioritize what will bring in the most revenue. Increased revenue comes from hearing the needs of the user - and you need UX to independently represent that voice - from both quantitative and qualitative perspectives.

Metrics could include drop off rates in purchase paths, shared responsibility for adoption (and work with the business to define what that means - which team is responsible for what), general site satisfaction, return user rate, and a number of other metrics that are more thorough than revenue - and could prove that the user experience is contributing to the bottom line. There could also be metrics from usability studies, showing that users like what they are using. There could also be discussions with users where they express their opinion or share stories to tell what they like or don't like about a product. The dashboard you create has endless possibilities depending on your business and what makes sense to track. But in all cases, it allows the user to have an equal voice with other interests.

If you want to get more money from your customer, you have to find out what they really want. UX does this best. That's why the money should be used to directly fund UX work, not allocations to other teams as the middlemen. UX Independence!

Sunday, August 26, 2012 | Permalink | Comments (2)

The embarassment of the dreaded typo

I was thinking about this the other day when I submitted an update for a typo that had to be done quickly. Some development teams prioritize fixing a typo or content mishaps as a level 4 bug - it's very low on the priority list. Realistically, typos don't impact functionality, and most users understand what is meant by the transposed characters - so typos are not showstoppers, just annoyances. This made me wonder why the discovery of a typo is always a fire drill.

My answer: it's the embarrassment factor.

Typos are symptoms of less than perfect character traits - sloppiness, carelessness, being in a rush, not paying attention to detail, focusing on getting something done rather than getting something done well, not learning how to spell and proofread what you type. Nothing is more embarrassing to a copywriter than the typo, because, at least to him or her, the typo shows either the copywriter didn't care enough to get it right the first time, he or she didn't do that one last review or run spell check, or he or she doesn't know how to spell. A typo can be perceived as being worse than a grammatical error - at least a grammatical error proves that a team of people don't write English properly (and looking at most of today's adults, not many native English speakers really do use proper grammar). With all of the spell check tools out there and the number of people reviewing content - a typo proves that no one got into the details. Not even a machine.

But a copywriter should not be the only one embarrassed by a typo. Most corporate sites have an extensive team involved in writing and managing site content. There could be between 2 and 50+ people on a team to create site content. Yes, that's right - potentially 50+ people work on a site's content. That's over 100 eyes. 

Let's follow the life cycle of a typo, which may give you more insight into how embarrassing it really is for the team for a typo to make it to a live site: 

  • Someone writes copy
  • Copy is reviewed and edited by the team
  • Copy is approved by one or more people for posting to the site or inclusion in a database
  • Developer copy/pastes content and checks to be sure it follows conventions to layout properly on the page 
  • QA people and others review the content on the site 
  • Developer edits any content or functionality as outlined by bugs
  • Site is approved to launch

And there are cases where content is syndicated and it appears on multiple sites. In these cases, content is created, added to a database (Site A), and then pulled into another site as its own content (Site B). Not only should we consider Site A's content creation/review process where up to 50+ people missed a typo, but let's add on another 2 to 50+ people from Site B and their review process. That's a total of 52 to 100+ people (or 104 to 200+ eyes) not catching that there is a typo on the page. 

That's a lot of people missing a typo.

One could also suggest that a typo got introduced to the site during the process. That doesn't change the fact that up to 50 people, yet again, saw it and didn't do anything about it. It's just in this case, people saw that typo maybe once or twice, not up to 10 times, before it got launched. That means there was still time to fix it pre-launch. 

Once a typo launches, even more eyes are on it. And let's face it, users and customers are not so nice about a typo. Some user responses could be:

  • Not notice it and say nothing 
  • Laugh about it and not say anything to you, considering you or your company to be careless
  • Point it out to you through public channels and make fun of you while doing it (if it's that funny of an error)
  • Point it out to their friends and never tell you
  • Point it out to you and be nice about it

And I'm sure that there are more responses that I haven't thought about yet. If you ask me - those aren't great options - except for the last one. Further, most people don't report typos. It's not like a user can't complete a task on your site, or can't read the instructions. It's a minor mistake, but nevertheless, a mistake that is public and in plain sight, and sets a perception about your company. 

Let's say you find the typo and want to fix it RIGHT NOW. Although admirable, what does doing this really achieve? Let's just take a look at some of the numbers. By the time you find a typo to fix on a live site, how many eyes do you think saw that typo? Look at your site logs. That many people saw the typo. With that in mind, in all seriousness, what would happen if another 5 or 1,000 eyes saw it? Exactly. Just 5 or 1,000 more people may perceive you as careless compared to the number of people who already saw it. At that point, what's another few over the course of a day or two? Is it really all that harmful?

A team fixes bugs using a priority list for how important it is for a feature is to work properly. Often, bugs get released to the public because they are in less used features and therefore, are not as visible. Allowing a major feature to be buggy makes a company look careless - and who wants to buy something from a careless company? Also, such bugs can bring embarrassment to the company. With this in mind, one could say that the prioritization of bugs is based on an embarrassment factor.

Keeping in mind that minor bugs are released and launched, it makes you wonder why people claim that fixing a typo is the most important thing. It again goes back to embarrassment. The copywriter is often embarrassed the most because it's his or her job to prevent such silliness from happening. However, the entire team of 50+ - from the QA analyst to the VP responsible to the content - should be embarrassed because they all were slackers and let the little typo live on, never noting it as something to fix, or just not realizing it's a typo (which should get you to wonder about your team). The embarrassment factor of the typo's existence makes it THAT urgent.

Realistically, any typo isn't that urgent to fix; the urgency comes from the embarrassment associated with a typo - how it got there, why it's still there, and why no one sees it until after a site is launched for weeks. Sneaky typos.

Oh - and if you notice a typo in this or any of my blog entries, please let me know. Only one person with 2 eyes work on them.

Wednesday, June 27, 2012 | Permalink | Comments (2)

People are funny

So this is Don Dodge's new post - just came out today. Ironically it includes the information I posted to his site that never made it there. Coincidence?

http://dondodge.typepad.com/the_next_big_thing/2012/03/how-to-name-your-company-and-product.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+TheNextBigThing+%28The+Next+Big+Thing%29

 

 

Tuesday, March 20, 2012 | Permalink | Comments (6)

Response to Don Dodge

I really need to be better about posting here. It's been too long and I have a lot of things to report.

My latest update is that I posted a response to Don Dodge's latest blog post: http://dondodge.typepad.com/the_next_big_thing/2012/03/why-company-names-urls-dont-matter.html#idc-cover  

I posted this morning and didn't see it go live yet (it could be waiting for approval - I'm not sure). I made tweaks to my draft on his site when I submitted, so I don't have the full copy unfortunately (lesson learned - I will cut and paste moving forward), but here is the draft response, edited as much as I remember. 

 

Actually, after doing a bit of research (about 15 minutes on the Web), those names did have some meaning and a story around their creation:

 

  • Alta Vista – Latin – high view or view from the top of something (their original logo was of a mountain – so you are searching as if you were a vista point. This is from memory from long ago.)
  • Napster – based on the haircut of one of the founders. It was catchy and stuck. http://www.techno360.in/origin-of-the-names-of-famous-brands/
  • Cisco – short for San Francisco, where they were founded. http://en.wikipedia.org/wiki/Cisco_Systems#1984.E2.80.931990:_early_years
  • Google – based on the googol – a type of number with many zeros implying the amount of results you can get. Someone did a typo while searching. This is why Google appealed to the techies at first. http://graphics.stanford.edu/~dk/google_name_origin.html
  • Zappos – from zapatos for shoes (this one is obvious and doesn't need a link)
  • Yahoo – it's an acronym made up by the founders - http://docs.yahoo.com/info/misc/history.html
  • Zynga - name of one of the co-founders dogs (why the logo is a dog - originally it was Presidio Media) http://en.wikipedia.org/wiki/Zynga#History
All words - even made up ones - have some type of meaning. This adds emotional value to the company/product and helps bring in prospective customers and users - and it especially helps to get a great logo designed. Names are not just picked out of the blue - a lot of work goes into selecting them - even if someone uses the name of a dog or city. As you can see from the examples, all names have a story behind them. A great logo is only part of the brand - there is the user experience, the name, how the user learns about the product (SEO/SEM/Social Media). Posts like this oversimplify the process and, unfortunately, oversimplify the creative profession. There are companies that focus on naming exclusively (and rightfully so) - it's an art and science. 
Sure, the name and logo needs to be related to the product and service, but at the same time - it helps give creative fuel to the UX/marketing fire if that makes sense.
New customers just know their experience with the brand, how the name feels (fun, interesting, etc.) and extends to the experience, and what the product/service is offering. All of this together creates a memory in the user's mind about the product. Hopefully it's a good memory and the user comes back.  In the end, all of the elements of a brand/experience riff off of each other like a great jazz band. Everything is interconnected.
Such posts typically alarm me when they are not from branding or marketing experts because they leave out a lot of the story about what makes a good user experience. I'm not an expert in creating P&L statements or coding - which makes me not qualified to write about such things. Maybe given this post I should start doing that - I must be missing out.

 

 

As an aside - there has been psychology research completed on how names influence individual personalities. 

http://www.telegraph.co.uk/science/science-news/3294546/Is-your-name-to-blame-for-unhappiness.html

http://news.bbc.co.uk/2/hi/uk_news/magazine/7312412.stm

 

Sunday, March 18, 2012 | Permalink | Comments (2)

Published on UX Magazine's site

Here is the article that I wrote at UX Magazine (published just before the holidays). Enjoy!

http://uxmag.com/articles/usability-testing-includes-users-as-stakeholders

Tuesday, January 03, 2012 | Permalink | Comments (1)

Why Google Health is retiring

http://www.google.com/intl/en_us/health/about/index.html

 

Google Health is shutting down in 2012. I wasn't really surprised to hear that. I didn't think it was a concept that was going to have a high adoption rate to begin with. It's one thing for Google to manage your email, photos, instant messages, contacts, videos and track your behaviors. But for Google to know that you just had an organ removed the week before? I'm not too sure that's the type of information that you would want to share with them.

Then again, I'm biased. Working with health insurance companies for a number of years has made me sensitive to handling personal health information (PHI). At Blue Shield of California, we spent a lot of time thinking about PHI and HIPPA compliance and it's impacts - and acknowledging how much it matters to consumers. We frequently hear about hackers breaking into ecommerce and online banking systems, but generally most people aren't too concerned if an online account is hacked because most credit cards are usually protected from fraud and someone won't lose more than $50. But what if someone hacks into your health information? What if you have a life-threatening illness that you want to keep private? What if an employer learns about an illness (such as mental illness) and uses that information against you?

It can happen.

I took a look at Google's Health privacy policy and it's comparison to HIPPA compliance to get more facts as to what was being offered before I just dismissed Google Health as a generally bad idea. You can read it for yourself here. I found this chart to be a little disturbing overall. And here's why:

 

Google created a specialized privacy policy rather than leveraging existing HIPPA policies enforced by the Department of Health and Human Services

Google created a special privacy policy for Google Health. Most people in the US know what HIPPA compliance means and how it works. There are a lot of safeguards in place to protect people and information sharing of PHI. Sure, HIPPA can be a pain in the butt, but it does prevent the wrong people from getting information if you are unconscious. The benefit of HIPPA is that the Department of Health and Human Services enforces its own privacy protections through civil and criminal penalties; Google privacy policy is covered only under the Federal Trade Commission. Do you believe that a PHI breech will be handled properly if prosecuted through the FTC (the same organization that deals with consumer protection and anti-trust violations)? I didn't think so either. 

 

Information sharing

Below are two points Google lists for sharing PHI that I find challenging:

  • With contractors and vendors operating solely on Google's behalf (subject to security and confidentiality requirements)
  • To protect against imminent harm to the rights, property or safety of Google, its users or the public, or to address fraud or violations of the Terms of Service

What does this mean? Is this marketing information? What if someone has Hepatitis? Does this imply that Google needs to report that? What about reported epidemics? What about other disorders? Will it notify a 3rd party to contact you for more information? Shouldn't this go to a doctor? Where is your doctor in all of this? Reading this doesn't make me feel comfortable about the security of my health information and raises more questions than answers about infomration usage.

 

Who can access the information

A limited number of employees in particular job functions may have access to user information in order to operate and improve Google Health. Users consent to this limited internal use when they sign up for Google Health.

In health industries, employees and contractors go through quite a bit of training to learn how to protect an individual's PHI. I had to take courses and pass tests about PHI every couple of years to validate that i knew the rules. And I would have to go through more training if I actually worked with PHI. Given everything I had to keep in mind with PHI, I didn't want to work on anything related to it - it was all too much responsibility. But reading the above regrding Google, I'm not sure from this description how much training someone in Google gets around PHI or how that works. And even then, PHI is generally shared with organizations and people to get help and more information about an illness or coverage. Usage stats should be used for improving the site - not PHI. I think here, Google missed the point.

 

How Information is Kept Secure

This is the HIPPA security mandate:

HIPAA requires that health care providers and other services maintain a minimum standard of "reasonable and appropriate safeguards to prevent intentional or unintentional use or disclosure of health information".

This is the Google Health security mandate:

Google Health secures information by:

  • Using electronic security measures such as Secure Socket Layer (SSL) encryption, back-up systems, and other cutting-edge information security technology
  • Strongly restricting information access to a limited number of necessary personnel

Companies like Kaiser Permanente and other HMOs will often have networks of information inside a firewall. There is a lot of technology setup to allow PHI to be accessible to doctors inside the network and not to the outside world. Given that SSL is used with ecommerce and online banking - and people can break into this - it doesn't give me a lot of confidence. Sure, SSL is fairly secure, but I'm not sure how I feel about this protecting my health information. I almost feel better keeping my information as hard copy with a doctor and using the fax to transmit it - and this is why that workflow is often used today. There is more at risk with PHI in the wrong hands than your credit card. Again, you can be protected for up to $50 spent through fraud; no one can protect you if someone learns about your health problems and decides to use this against you.

 

Don't get me wrong, Google Health as a concept is a great idea. It would have been a better idea if it was originated from a health organization rather than an organization that leverages user data and tracks behavior for monetary gain. And people do recognize that Google is about the statistics - so it does make one wonder about their motives. With all of these factors, it does explain why Google Health just never was adopted as it potentially could have been.

What are your thoughts?

 

Friday, November 25, 2011 | Permalink | Comments (1)

Interesting post about the iPhone in Shanghai

I have other thoughts about the iPhone as well (e.g., it works great in warmer climates, but in the cold, get ready for your fingers to freeze if you are lost on the winters streets of Boston, New York, Chicago and the like), but this can get you started thinking.

http://blogs.hbr.org/cs/2011/09/why_someone_from_apple_needs_t.html

From various conversations, I've learned that working with the Chinese language is always a challenge because it's not structured the same as a western character based language and honestly, outside of our expeirence. It's true - Western designers need to get a crash course in other languages like Chinese, Japanese and Arabic to better understand how input devices (maybe for those languages it's not a keyboard) could be optimized to reflect how people think when they are communicating in those languages (and how the communication is different than western/latin based languages).

Anyway - happy reading and more later!

Tuesday, September 13, 2011 | Permalink | Comments (3)

« Previous | Next »
My Photo

About

Recent Posts

  • The Dos and Don'ts of Collaboration
  • Interesting perspective on customers who buy copies
  • High-tech Really Is Like High School
  • JP Penney - a case study in customer research, or rather, listening
  • On the theme of data and meaning....
  • How much data is enough? Enough to have a conversation with your users.
  • Some good advice on innovation
  • SXSW Interactive: Why do we go? (A cantankerous opinion)
  • My first Webinar
  • What is up with this new term "evergreen"?
Subscribe to this blog's feed
Blog powered by TypePad

Categories