INTRO: UCD CHARRETTE

(Above: Sticky notes on the board as group brainstormed about types of users)

-A CHALLENGE PRESENTED-

We started the class off by listing several types of scenarios and people involving cars, and we were assigned a group to design for. The challenge presented for this first sprint was to create a vehicle's user-interface for a particular group of users that have certain goals and needs. 

I had the assignment of designing for somebody who was on the road for many hours at a time (such as a truck driver) who needs a way to stay awake on the road. My group thought of a car that senses when the driver is falling asleep (by the tension on the wheel) and wakes them up using an alarm or by music. 

(Below: My group partner and I present what our interface would look like)

Designing for this type of user got me thinking about why designers would choose one interface over the other when there are so many types of people to be addressed. You can't create a design that appeals to every single subgroup of people, but what do they use to determine which subgroups take priority? It was difficult to think of an interface that could apply to any car or truck without having to add all the bells and whistles of an actual alarm. Incorporating this design into an already existing interface (to suit every vehicle's need) was the hardest part.

Overall, this project was enjoyable; I do not have a lot of opportunities to work with a team to come up with brand new ideas in my typical classes, so it pleased me to see how many concepts and ideas my small team of three could come up with. The amount of time that we were able to accomplish this was also surprising, as we created a flow chart and some concept art for our idea, along with a brief presentation to the class. 

-THE PROCESS-

The main takeaway of this assignment for me was that I had to open my eyes to all the different potential users of a product, so the charrette process could be useful when I'm trying to find a wide range of ideas to suit, for example, a wide range of people. App designs or interface layouts need this amount of thought and consideration per idea. 

This process is quite handy when it comes to getting a large number of ideas posted and outlined for brainstorming, but it's not as appropriate when there's one clear solution to a problem (as you don't need such a large number of ideas). Why brainstorm together when there's only one path to solve this? But otherwise, this is a good way to collaborate.