CHI day 1

The first day of CHI started with a great opening plenary by Lou Yongqi (check keynotes here and yes, check out WHO is the closing plenary!), which came forward and highlighted the importance of Sustainability in research! Followed by an amazing program of novel technology (think Virtual Reality!), human augmentation (check this totally new way of embodying another person by Prof. Rekimoto), user studies (“Understanding and evaluating User Performance”), and understanding of elder users (“Designing for 55+”) and communities (a great session on Activism in Wikipedia, one on Privacy and one on the “Maker Community”)!

Taken from http://blog.johnrooksby.org/post/116870237912/lou-yongqi-keynote-at-chi2015 Copyright remains with original page.

Also this was the day of the video-showcase, which is a non-academic venue in which authors can submit their videos for further appreciation. It is an amazing opportunity to great a glimpse of CHI by sitting in the theater and watching great research in motion. This year’s winner was the Transform project by the MIT Media Lab (see it here), from which one of the authors is our dear editor Sean Follmer, so congrats to him and his team!

Dear HCI, Thank you. Love, Mechanical Engineering

My entire academic background – BS, MS, PhD –  is in Mechanical Engineering.  However, in addition to conferences hosted by the American Society of Mechanical Engineering, I also attend the suite of ACM’s Human-Computer Interaction (HCI) Conferences. So, why should Mechanical Engineering care about HCI?

First, product design includes interfaces.  ‘Product design’ refers to the blend of mechanical engineering and industrial design. Design is the ‘outward facing’ side of Mechanical Engineering; product designers conceptualize, design, and implement many of the physical products you interact with on a daily basis.  In the cafe that I’m currently writing from, a design engineer was involved in everything from the teacup, the teapot, the table, the chair, and the laptop I’m writing on… and all the packaging that each of those products arrived in.   These traditional products still have interfaces – examples from Don Norman’s infamous “Design of Everyday Things” address how people physically interact with ‘non-smart’ products and devices such as teapots, doorknobs, or rotary telephones.  Today’s product designers are asked to not only design the physical product, but also weigh in on how the user should interact with smart products.

Second, design research in mechanical engineering can learn from findings from interaction design.  Early-stage phases of new product development – particularly user research and concept generation– are agnostic to whether or not the final ‘product’ is a physical product, software, a physical or digital service, or an architectural space.  As a result, many of the same design theory principles coming out of the interaction design community are broadly applicable to other design domains, including product design or new product development, within some level of translation.

Finally, engineers deserve well-designed technology. Engineers are people too – and, while computer scientists frequently design new programming environments for themselves, mechanical engineers and new product developers are not always the subject of thoughtful, human-centered technology design. Taking an HCI perspective to understand how engineers and designers are users of software opens up the possibility for better-designed tools in the future (I’m looking at you, CAD!).

… so why should HCI care about Mechanical Engineering?

It’s sometimes easy to get lost in cognition, perception, algorithms, and pixels.  However, when mechanical engineers check their gut, they see the physical interface between humans and computers.  You’ll see plenty of relevant contributions from Mechanical Engineering in the areas of ergonomics, haptic feedback, or tangible interfaces. But more broadly, mechanical engineers offer the reminder that humans (and computers) still primarily exist in a physical world.