Today's computer science seminar is the last one of the academic year before we take
a summer break and we are finishing with a very distinguished speaker. Professor Ben
Shnedierman is a pioneering researcher in HCI and his talk will focus on a subject that
seems very pertinent to our new school: how to carry out research that blends science,
engineering and design.
Location: AG08
Date: Tuesday 8 July, 2014
Time: 12:30 - 14:00
Speaker: Professor Ben Shneiderman, University of Maryland
Title: High-Impact Research: Blending Science, Engineering, and Design
Summary:
High-Impact Research strategies could help large and small projects to deepen human
understanding of the natural and made worlds, so as to promote sustainable use of natural
resources and improve quality of life for individuals, organizations, communities, and
nations. The raised expectations are that by addressing basic and applied research goals
from the start, projects will yield higher quality basic and applied results.
The High-Impact Research strategies are not for everyone, but I claim that researchers are
more likely to achieve high impact, if they follow these strategies:
- Choose actionable problems that address civic, business & global priorities
- Blend science, engineering, and design knowledge & research methods
- Seek interdisciplinary collaborations with diverse individuals & organizations
- Build on generalizable theories, principles & guidelines
- Develop prototypes that are tested with ever more realistic interventions
- Use quantitative big data & qualitative case study research methods
- Promote adoption & measure impact
There are many ways to apply these strategies, and there may be other strategies that
would be helpful, but the number of individuals, teams, and organizations that are
already demonstrating their value is growing. My hope is to accelerate their adoption
and provoke discussion of these and creative alternatives.
Speaker Bio:
Ben Shneiderman (http://www.cs.umd.edu/~ben) is a Distinguished University Professor in
the Department of Computer Science, Founding Director (1983-2000) of the Human-Computer
Interaction Laboratory (http://www.cs.umd.edu/hcil/), and a Member of the UM Institute
for Advanced Computer Studies (UMIACS) at the University of Maryland. He is a Fellow of
the AAAS, ACM, and IEEE, and a Member of the National Academy of Engineering, in
recognition of his pioneering contributions to human-computer interaction and information
visualization. His contributions include the direct manipulation concept, clickable
highlighted web-links, touchscreen keyboards, dynamic query sliders for Spotfire,
development of treemaps, novel network visualizations for NodeXL, and temporal event
sequence analysis for electronic health records.
Ben is the co-author with Catherine Plaisant of Designing the User Interface: Strategies
for Effective Human-Computer Interaction (5th ed., 2010) http://www.awl.com/DTUI/. With
Stu Card and Jock Mackinlay, he co-authored Readings in Information Visualization:
Using Vision to Think (1999). His book Leonardo’s Laptop appeared in October 2002
(MIT Press) and won the IEEE book award for Distinguished Literary Contribution. His
latest book, with Derek Hansen and Marc Smith, is Analyzing Social Media Networks with
NodeXL (www.codeplex.com/nodexl, 2010).
















Saroj Shrestha
September 3rd, 2013 1:48 pmMartinspire
September 3rd, 2013 2:14 pmDieter Mueller
September 3rd, 2013 2:36 pmBefore the Pseudo-3D Style was made so simple even Pixel Monkeys could do it with Shadows and Light Effects – everything was “flat”.
Wrong Argument #1: Flat Design reduced Information Overload.
Any UX-Designer or IA will tell you that the Interfaces hold the same Amount of Information – just the visual Representation is less ornamental.
———-
Wrong Argument #2: Flat Design is “simple” or brings Simplicity.
Not it isn’t. It is made to look simple. It a Question of Perception, not Reduction or Simplification of the Interface and it’s Elements.
The Author confuses Simplicity with Reduction. For example GMails new Compose Windows looks simpler, because it has reduced the Number of Elements – but it also means that the User has to make more conceptual Leaps to get his Tasks done. To open the Formatting Option you now require an additional Click just to open that Toolbar – which means the User has to remember the Interface and even understand the conceptional Leap that a certain Icon represents the Formatting Option.
Once again it’s about Perception: the Interface is not simpler and nor is it a Simplification of the actual Functionality and Workflow – but Eye Candy and hiding perfectly useful Function for the Sake or being cool and trendy.
So Simplification often causes unnecessary conceptional and cognitive Leaps by the User – hardly an Achievement in Terms of good Usability and actual Simplicity.
———-
Wrong Argument #3: Obviousness of Controls
No, not everyone immediately gets every Interface, even when they have worked for Decades with Gadgets and Computers.
Why shouldn’t Controls be obvious, clearly identified and labelled?
Because Designers are bored of doing their Homework? Or because Buttons spoil their pretty Photoshop Designs?
Unless you customizable Interfaces or a Pro and Beginner Version any Interface should be as comprehendable and clear as possible.
Even so called digital Natives are often not as sophisticated as they think and any Interface requires a learning Curve as well as conceptional Leaps.
The Designer should provide a solid Interface and possible a Choice for the User to customize his/her Experience – Empowering the User doesn’t mean hiding Stuff, just because we ASSSUME the User has it all figured out.
Especially Google has that terrible Habit of making their Offerings “Auto-Awesome”, which doesn’t empower the User, but make him/her a Bystander in the Workflow. This takes away the Chance of actually learning a Tool and some Skills as well as Choices with the Workflow / Creative Process.
This dumbs down the Users – it doesn’t empower them. Power comes from Knowledge and Knowledge comes from Learning. Take away the Chance of Learning and you get a Pavlovian Button-Presser.
———
Contrast is King? The Author illustrates his Points by using many Screenshots that have miserable Typography and Colour Choices that have hardly any Contrast at all.
This is currently very prevalent in Flat Design: dark Grey Typo on medium Grey Background – no Contrast at all (this also applies to the Example of White Type of Yellow Background). Often they also use very delicate / thin Fonts that offer also no Contrast, especially on mobile Devices in Sunlight.
J Gallaher
September 3rd, 2013 2:57 pmIt’s actually really confusing and things are misplaced. Example, signing out and settings are in two different areas that are hidden away.
David G.
September 3rd, 2013 3:40 pmCan you also give some design advice in addition to your (constructive?) criticism? Like what do you consider good typography or contrast color schemes? And how would you make interactions obvious?
Libbie
September 3rd, 2013 3:10 pmNowadays, people innately know how to use a smartphone/tablet so the interface is allowed to become less obvious, more stripped back, and that kind of paves the way for a ‘simpler’ design.
Sean
September 3rd, 2013 3:46 pmAdrian Taylor
September 3rd, 2013 4:11 pmArgument #1: Flat Design reduced Information Overload.
I agree that there is the same about of media (text, image, video, etc.) in a flat design as in a more dimensional design however I would argue that every item in a design requires effort by the user to decode. Less elements often means less work. Now this is not to say that you can’t make a dimensional design easy to parse, just an example of a possible benefit.
Argument #2: Flat Design is “simple” or brings Simplicity.
I agree with you here and don’t believe that I ever made that argument that flat inherently creates simplicity. In fact, I would suggest that a reduced use of dimensionally in your design often makes it more difficult to create an obvious / intuitive interface. Good usability and aesthetic style are separate concerns. I do feel that when designs attempt to work with a reduced visual pallet it can help to focus their efforts on usability rather than decoration, but not always. I think we both agree that simplicity is hard to do right.
Argument #3: Obviousness of Controls
I think we are actually aligned on this point. Flat does not make things more obvious, it often makes them less so. When designing flat you must work even harder to make things intuitive. A big shinny button with a drop shadow is almost always going to be more obvious then a thin white arrow on a flat background. Before working flat designs must consider whether it is the right style for their audience and then word diligently to ensure usability.
Thanks again for your thoughts!