Category: General Stuff

I recently attended the monthly  BayCHI event held at PARC, featuring a couple of talks around “the future of user interfaces”. I was only able to see the first one, done by Nathan Shedroff, currently chair of CCA dMBA strategy program and acclaimed author of Experience Design, amongst other titles. A wonderful presenter and all-around great guy, Nathan previewed his upcoming book “Make It So“, which looks at science fiction films & TV shows as inspirations for user interfaces and their enabling technologies. Very fun, inspiring talk and definitely a book I’d recommend picking up to add to your design inspiration arsenal. Below are some of the key themes Nathan emphasized…

– Mixed modalities & multiple paradigms can shape one’s perception of how interfaces fit within one’s lives, taking on humanized and cultural qualities suitable (or not) for interaction (touch + voice, device vs surroundings, visual or tactile, avatar vs tool vs activity, etc.)

– Sci-fi stories have shaped popular conceptions and more importantly, expectations, for what technology can offer us, enabling a “better life”. We all expected jetpacks and flying cars. But the force of real cultural, technical, and human factor constraints have led us to experience that which is appropriate (ex: flying cars would be a massive nightmare to deal with! or jetpacks burning people, awkward social conventions like flying away, etc.) Budgets and laws are a good constraining factor for tech advancement in some ways!

– Specific references:

— Motorola StarTAC was almost literal embodiment of Star Trek communicator device, even the name hints at its inspirational source. Physical truth to the notion that it takes about 50 years for sci-fi tech to become real and popular.

— in 1987 PADD, used by Starfleet within the Stark Trek universe…just like iPad! Sort of.

— Tablet PCs were largely driven by movie fantasies with the slate form factor and stylus interaction. Even some featured without pen but just touch-based.

— The “Knowledge Navigator” concept video by Apple in 1987 was ultimate fantasy sci-fi tech film, anticipated much of what we have now, like smartphones, wireless, Siri, etc. Inspiring and useful tool for looking backwards, reverse reflection of current and future possibilities.

–Personality within devices and tech, makes for anthropomorphic approach to tech, suitable for human interaction. Truly and literally social interaction, not just social media. For example, R2-D2 with minimal cues (just sounds and slight movements) felt very “human” and real. We empathized despite R2-D2 not having a literal face, arms, in typical quadruped fashion. Also Knight Rider with the voice and automotive behavior.

— Nathan suggested that even the infamous Amazon “one-click” is an example of anthropomorphic design: like a concierge with recommendations and also super easy, simple, trusting, with confidence of the results. Hmm!

— The Pixar short “Lifted” shows the madness of complex interfaces, afflicting the hapless alien junior pilot undergoing some training exam. Too many buttons without any labels! So films can be a satirical reference for criticism of our current situation.

— Finally, a great example of how holography in Star Wars conveys social hierarchy. Notice when Palpatine or Yoda and others are projected large versus small in different contexts. Consider the implication for remote web conferencing with video, or telepresence or chat. Hmm!

Some fun examples and interesting ways to re-consider existing and future user interfaces per sci-fi. As Nathan concluded, as designers we create fictions, and we are telling stories that enable our cultural expectations and imaginations. Science fiction is just one great resource to tap into!

 

 

I recently attended a guest lecture at Citrix by renowned Stanford Professor Bob Sutton. Very quickly paced, insightful and thought-provoking, filled with nice stories and anecdotes to help qualify the broader principles Sutton advocated in support of “scaling excellence”. Below are my notes and key takeaways…

Scaling excellence refers to spreading “superior ideas from the few to the many” in some organizational context (a team, a department, an entire company, etc.), based upon promoting a “mindset” which Sutton defined as “a set of beliefs centered on the why (motivations, drivers), that guide behaviors”. He smartly pointed out that you should pave forward a “mindset”, not just leave behind a “footprint” that’s easily forgotten.

On Facebook…

In particular, Sutton referenced the Facebook ethos and their model for cultivating a “Facebook” mindset and scaling that across the organization sans dilution and dispersion as more people join the company. He pointed to Facebook Product VP Chris Cox as a literal embodiment of the Facebook ethos, and grand promoter of it internally, via his “sweet, genuine” personality that is highly admired within the company. This ethos is reflected in certain key phrases uttered by Cox:
– “understand the whole codebase”
– ” move fast and break things”
– “touch the metal”
– “any job you have is temporary”

Clearly it’s a dynamic, iterative model of thinking and working! Gotta be flexible and roll with the punches. This is inculcated within new Facebook engineers from day one as part of a 6 week bootcamp (!), whereby new recruits don’t know what their specific job duty is and are rotated among several projects (like 12-13)…but in the first week they have to do something that they could show their Mom to make her proud. Ha! So that really encourages the engineer to get hands dirty very quickly, a literal “bias towards action” (to borrow a phrase from Stanford d.school). But it’s also very cultural, to get that mindset and habit established early on, from the get go. Sutton mentioned that Cox is very afraid of watering down and losing this core truth to the Facebook culture as more engineers join the company and they become geo-distributed (apparently they just opened a NYC office). Time will tell…

Key Principles

Moving on from Facebook, Sutton ran through a set of broad principles for “scaling excellence”…

** More vs Better tradeoff
— Just like with feature creep, too much info/rules/policies/structures as the org grows is a burden on cognitive load, increases complexity and difficulty, degrading the cultural core.

** Alone vs Cooperative
— Highlighted several companies like P&G, Mozilla, and Pixar which took several approaches to dealing with competition and retaining their core culture (connect & develop vs. open source vs. going alone)

** Catholic vs Buddhist approaches
— Ah, the eternal struggle ;-) Do you declare a cultural value system and force everyone in a Catholic manner with strictness, or create a general value framework that each team/locality adjusts for their needs? Pros/Cons either way.

** Hot Causes need Cool Solutions
— How to get teammates excited and emotional about a dire deep cause that drives the company, and generate cool solutions for customers? Gotta have both to succeed. Hot emotion, and valuable outcomes. Else folks get excited for nothing, a waste.

** Connect and Cascade
— A way to foster connectivity and trickle out the learnings and values across teams, etc.

** When in doubt, cut it out
— Sutton highlighted the Intuit Design For Delight initiative which had tons of complex info and raised lots of doubt initially. After revamping their “pitch” into a pithy triangle diagram, more Intuit employees bought in.

** Little things have big impact
— Things like word choice, moving furniture around, body postures, small recognitions for good behaviors, etc. Small victories! Gotta celebrate them too. Builds confidence and credibility when you ask for the truly big things.

** Don’t put up with destructive attitudes/behaviors
— Obviously if there are die-hard cynics and naysayers, dump them and keep moving forward. Don’t poison the well, be swift and move on.

** Swarming is not Scaling
— Interesting point… “swarming” is when you’ve got a group all super excited but then don’t implement, translate passion into actionable results. To scale, you need to act, connect, demonstrate, do real things that are exemplars.

Ultimately to scale excellence in the org you gotta walk the talk, truly embody the attitudes, beliefs and behaviors in your daily actions, serve as role models / exemplars for others to emulate (implying the inherently leadership nature of scaling excellence…want others to do as you? then you gotta do it first!) People are creatures of habit and sociable, so gotta leverage those small simple truths of human nature when trying to effect massive change in complex org contexts. These ideas and princples from Prof Sutton should help!

Been a little too quiet lately I realize ;-) Drafting some posts based upon the following topics and perspectives for next few weeks…Stay tuned!

* Stylistic trends: An observational piece noting some of the most popular visual UI trends over the past decade, going back to Apple’s Aqua, up to MSFT’s Metro. Not about personal preference, likes/dislikes, but more about the key qualities, taking a bigger macroscopic view…and suggestions for what might be coming next.

* UI “chrome”: Recent interface models & visual styles (esp MSFT Metro) are veering towards “chrome-less” designs, ostensibly supporting a “content-first” attitude. Some thoughts and reactions. Can we defend the value of UI “chrome” against the wave of flatness?

* Design’s supremacy: Many recent articles tweeted around in the design-o-sphere have been celebrating the role of design as founding part of a start-up team, necessary for any software dev success, etc. But haven’t designers been articulating this for, oh I don’t know, decades?? What’s the crucial turning point? Has there been a gradual ramp-up in recognizing design’s positive value to business and technology, beyond “making it pretty”?

* UI standards, patterns, and genres: Some initial thoughts looking beyond the typical set of UI standard guidelines and patterns towards product genres, a typology to inform better applicability of patterns, and grappling with the common, yet complex situation of supporting lots, lots, lots of products (esp for large enterprise software firms ;-) How do “persistence, inheritance, and emergence” factor into designing for UI genres? Hmm.

* Designing: Finally, my book! Or what I hope will emerge as my book ;-)  Assembling various key posts from this blog, along with thoughts on “designing” as a professional, offering a lively, anecdotal POV on the story of designing as a practice, a passion, a pursuit.

 

 

 

 

 

 

Finally…in developing digital products, there’s a range of often-forgotten elements that contribute to the total user experience and can negatively impact a user’s first time (or last time) encounter unless taken seriously from the very beginning. Make sure not to forget these vital pieces, so they’re not left at the last second or to some poor overworked engineer to jam on it at 2am before all-too-critical code freeze!

 

The initial “out of the box” experience
What’s the first time flow? What about the “next time” and thereafter? Consider licensing, activation, registration, and even un-install or deactivation as well (the final, end of app experience). How do they all relate? Make sure the login or sign-up process is simple and painless, preferably delightful, with a strong positive brand impression being made.

App preferences & settings
This should be simplified, largely smart-defaulted as much as possible. Never treat your prefs area as a toolshed, throwing a bunch of junk that doesn’t fit elsewhere. It should be well-curated just like a task menu or table list.

User accounts pages
Make sure users have a place to go to modify their accounts, update billing, change passwords, etc. and of course manage their privacy settings in an extremely intuitive, understandable manner that doesn’t require a law degree or IT schematic diagrams!

Error & warning messages
Don’t leave this to the very end or treat as an after-thought. It’s necessary to factor these into the overall design and product development process. Remember to make messages human readable, and meaningful with clear actions, preferably phrased in the affirmative (i.e., avoid double negatives, which confuse folks).

Section 508 compliancy
For physically challenged (sight, hearing, mobility) users. This is critical for government contracts in particular. Various agencies offer specialized consulting for 508 compliancy.

Internationalization
Maybe not a big issue for start-ups as much, but perhaps down the road as you grow and broaden your market reach, it’s good to spend some time considering your plan for supporting different languages and global markets. A good rule of thumb is to factor 30% more spacing for labels in forms.

 

Continuing with the primer series, this part covers some key fundamentals for shaping an effective user interface. Each should be carefully interpreted and absorbed (not just skimmed), to help achieve a solid foundation for good design in your product. Applied diligently (and repeatedly), they form the basis for a sound design practice and habit that will carry forth in subsequent revisions and related products/service offerings (i.e., mobile, web, etc.).

* Layout, structure, hierarchy, clutter, emphasis, fonts, colors, language…Yep it ALL MATTERS to good UI design. Below are some basic UI design principles to help:

* Having a good mental model (organization of elements) is critical. Should be simple, intuitive to understand. 

* If your user asks “how do I get back?” or “where is that page?”, just generally lost/confused, that’s a sign you have a poor mental model. 

* Structure is vital: navigational structure (taskflow), informational structure (menus and tabs), visual structure (layout of elements). 

* Grids provide the order, regularity, hierarchy, and stability for understanding a product UI layout. Respect and persist the grid! Don’t just randomly put stuff in places that “look nice”. Be sensible and logical.

* Use contrast and whitespace to create visual emphasis. There should always be a single clear emphasis of what’s most important. Limit the number of emphasized elements otherwise everything is shouting.

* Cluttering a screen with every possible piece of data only creates confusion, hurting the priority of content and overall legibility.

* When it comes to fonts, start simple: Start with just 3 fonts and limit the overall number. A font is any variation of weight, style, color, typeface. 

* Ditto for colors, start simple: Pick a color system that serves the need of the product at a functional level. Start with a base color, up to 3 compliments, 1 highlight color and black and white (yes, white is a color too! it’s not “nothing”)

* Reduce complexity: Remove all extraneous lines and ornamentation. Check for repeated words and symbols that can be consolidated. Pick a primary way to perform an action and do it well. Do you really need all those buttons, dropdowns and sliders? 

* Language is vital: Avoid marketing labels in the UI. Just call things what they are to the user in their language. Always use industry standard language when possible for specific domains, like bio-tech or financials. Be consistent with terminology! Especially across platforms and devices. 

*All UI actions require visual feedback. Make sure there are visual cues as to what is draggable, clickable, etc. If the UI lags in response to a user’s action, it will be perceived poorly by the user. Performance matters to good design!

* Being consistent for the sake of consistency is unwise. Cohesiveness and being sensitive to the context, purpose, goal of user’s task…that’s far more important.

* After doing all this…seek out moments of delight, something fun, positive, surprising to make your product more desirable. Clever uses of animation, sounds, graphics, casual language are all examples. 

* Ultimately you want to be sure your product instills a sense of trust (confidence and reliability), desire (emotional bonding), and integrity (authentic, cohesive, fully formed all the way).