Saturday, June 27, 2009

Mobile & Real-Team Web Innovation Podcast

Joining me on this episode are Val Fox (Director, Innovative Technology Solutions, Ryerson University), Keith Instone (Information Architecture Lead, IBM CIO’s Office, IBM.com), Eliane Tozman (User Interface Designer, IBM Media Design Studio), and our newest member of the panel Jay Trimble (Group Lead for the User Centered Technology Group, NASA Ames Research Center). The panel discusses the Palm Pre and Palm's new WebOS, an update on the Usability Professionals Association (UPA) including an innovative perspective on design called Evil by Design, a summary of the trend toward what has recently called the real-time web including design features of Google Wave and recent experiences regarding Twitter. The interesting website of the month that was discussed is spezify.com and the community news concerned the IxDA organization. The Mozilla Labs design challenge together with IxDA was also discussed.



As always, please use the comment capability of this blog to provide any feedback you may have on this podcast episode.

Thursday, June 18, 2009

Producing a Podcast - Part I

I've been creating podcasts for about a year and a half and during that time have been asked on a regular basis how I go about doing it. I've provided those who asked the details of whatever setup and procedure I used at the time. I've regularly improved upon the equipment, software, and settings. However, I'm pretty well satisfied with the setup that I have now so thought I'd share what I do and what I use here; that way, I simply have to point people here for all the details.

The most important aspect of doing a podcast is the content. The subject of the podcast series should be something that you know well and are passionate about. You'll be spending a lot of time on it and will need to produce episodes on a fairly steady basis so make sure that you choose your subject area carefully. It should also be a subject that others are interested in and that there aren't hundreds of podcasts on already. You can check what podcasts are available on various subjects by doing searches in the iTunes store. You should plan on creating a podcast episode ideally on a weekly basis but every few weeks is usually acceptable too. Listeners start to develop an expectation of receiving your episodes at a particular cadence so you should try to stick to a steady schedule of delivery. There are times when get out of the regular rhythm but then just get back to it when you can. I was ill recently, for example, and then experienced laryngitis for weeks afterward which prevented me from recording episodes (having a voice is rather important in podcasting). I've heard that 30 minutes is the ideal length of a podcast although an hour or longer may be appropriate especially given panel type formats. A microphone is the most important piece of equipment you'll need. I use an Audio-Technica AT2020 microphone. It is what is referred to as a large diaphragm condenser microphone. It has great sound but you need to also use a pop filter with it (to prevent an explosive sound when you say the letters 'p' and 't'). I use an Apex pop filter. I have both attached to a floor mounted microphone stand that doesn't touch any other surface such as the desk to prevent the picking up of any extraneous noise. I record in a room with broadloom and make sure that anything else that can make a noice isn't in the room or within earshot (even a cellphone on vibrate will be picked up by the microphone). I don't use a script but do make notes prior to the recording, the quotes and top 10 lists in the case of my Life Habits podcast and the list of articles and their links in the case of my UXDesignCast podcast).

Given the amount of material to cover, I'll divide this post into a Part I and a Part II. I'll address the actual recording and post-production software, settings, filters, uploading, and posting in Part II. As usual, feel free to contribute any of your own thoughts, experiences, and/or questions using the commenting capability of this blog.

Friday, June 12, 2009

Dynamic Forms, Survey Construction, & Design Inspiration Podcast

Here's episode #26 in my UXDesignCast podcast series. Joining me on this episode are Julie Santilli (IBM Visual Design Community and Tools Lead ), David Schwartz (IBM UI Architecture, Patterns, & Assets Lead), and Bob Jones (IBM User Experience Community & Tools Strategy Lead). The episode provides advice on designing dynamic forms, on constructing effective surveys, and discusses design quotes and recommended reading that provide design insight, advice, and inspiration.


As always, please use the comment capability of this blog to provide any feedback you may have on this podcast episode.

Thursday, June 11, 2009

Influential Books on Design

I've been interested for some time in getting other people's perspectives on a number of topics but most recently on the topic of the most influential books on design. So, I asked the followers of my @ibmdesign and @karelvredenburg Twitter accounts the question, "What's the most influential book you've read on design that you'd recommend to others?" I received a number of really good responses so thought I'd share them here. I've decided to include the additional words people used in describing their books. It is interesting to note that five people mentioned books by Donald Norman with the first four recommending "The Design of Everyday Things" and the fifth recommending his more recent "Emotional Design". The rest of the list includes some pretty interesting books some of which I know I haven't read but now will.

  • Donald Norman's "The Design of Everyday Things".
  • "The Design of Everyday Things" by Donald Norman, perhaps the best and most foundational design book.
  • I think Don Norman's "Design of Everyday Things" is a must-read for anyone who designs anything!
  • "Design of Everyday Things"
  • Most influential book: "Emotional Design" by Donald Norman
  • "Set Phasers on Stun" has great case studies of design gone awry.
  • "Dreaming in code" is an interesting guide to software development.
  • The most influential book on design that I have read is "Goodnight Moon" by Margaret Wise Brown. The audience is enormous.
  • "Computers and democracy: a scandinavian challenge" (1987) - first major participatory design publication in english
  • "Dont make me think" is the best design book. At least for me. Principals discussed applied any where.
  • "Now You See It: Simple Visualization Techniques for Quantitative Analysis" by Stephen Few
  • Jeff Johnson's "GUI Bloopers" is the most practical useable desktop reference for companies that don't have standards or UX staff.
  • "The Illusion of Life"; "Design is multidisciplinary", so I don't think we've only 1 most influential book
  • "Sketching User Experiences"
  • "Reflective Practitioner"
  • "A primer of visual literacy"
If you have any books to add to the list or have any comments on the books already listed, please leave a comment below.

Monday, June 01, 2009

Innovation & Design Balance Podcast

Here's episode #25 in my UXDesignCast podcast series. I use a number of different formats in the series including interviews with design leaders of companies across the industry, education sessions, interviews with IBM design teams, and panel discussions. The latest session is a panel format and included panelists Val Fox (Director, Innovative Technology Solutions, Ryerson University), Keith Instone (Information Architecture Lead, IBM CIO's Office, IBM.com), and Eliane Tozman (User Interface Designer, IBM Media Design Studio). In this episode, the panel discusses the Sixth Sense research project, the future of internet search, data-driven design, and what's messing up our UIs (see previous post on this blog).



I recorded this podcast some weeks ago but we had so many technical difficulties with the recording (one panelist didn't have the regular microphone, one didn't have mute working yielding huge echoes, another had a phone ring, and other interruptions) that it took until now to provide an edited version of it. I'd appreciate any comments you may have on it using the regular commenting mechanism.

Thursday, May 07, 2009

Twitter Insights


Who would have thought that an application that provided users the ability to input 140 characters of text, have others see it, and be able to see what others write would have become such a success. I've pointed out previously in this blog that I attribute the success of Twitter to the ability to connect with other human beings very efficiently with a minimum of technology in between.

There is a lot we can learn from this phenomenon if we collect and analyze relevant information. I did that via my two Twitter accounts (@ibmdesign and @karelvredenburg) and a polling tool. I've summarized below some of the key findings.

Twitter Use:
A total of 68% of followers have Twitter visible to them most of the day. That's a lot of people keeping track of what is on Twitter for a good portion of the day. Interestingly, Twitterers are not the same as Facebookers. Followers reported using Twitter 80% of the time and Facebook 20% but when I polled my Facebook friends the opposite was true.

Electronic Communication:
Followers responded that 65.7% of the time they interact with others during a typical day is via electronic means. Of course, this isn't just Twitter but is still astounding that two out of every three interactions people have during a typical day are via electronic means and only one out of the three is face-to-face in person communication.

Percent of Tweets Read:
You wonder what percentage of tweets people actually read on Twitter. I asked that too. Followers reported reading 47% of tweets on average but there was a low group which read 5% and high group which read 90%. The low group typically followed a lot of people making it difficult to read a significant proportion of the tweets coming through.

Website or Clients:
On average, users reported accessing the twitter.com site only 7.6% of the time they use Twitter. The vast majority use desktop or mobile Twitter clients. The percentage is interesting because the only statistics that are ever provided for the total number of Twitter users are those of the number of people who use the Twitter.com site. If the 7.6% is at all in the ball-park, this suggests that the total number of users of Twitter exceeds that of Facebook. It would seem possible to accurately count the total number of users since the source client information is included in each tweet but nobody to my knowledge has reported those numbers.

Time to Start Tweeting:
A recent report questioned whether people who join Twitter are serious about using it since it appeared that 60% didn't continue tweeting for the first month. I ran a poll on this one and found that 33% started reading and tweeting immediately, 18% took a week to start, 14% took more than a month, 21% took several months, and 11% took more than a year before that started. I'm actually in the several months group myself. It took me a while to figure Twitter out and friends of mine have the same experience. From these data, it would appear that 49% of people do not tweet during the first month that they've signed up for Twitter but they do after a month or much later. This itself is interesting. While the basic concepts behind Twitter is fairly straight-forward, the actual use if it with all of its conventions isn't.

Conventions:
In a previous post on this blog I wrote the Twitter Authoring Guidelines to help people getting started with Twitter. I'd suggest that anyone still unclear about aspects of the Twitterversse to read that post. It is interesting that most of the conventions in Twitter simply involved someone starting to use a particular practice and then others following their lead. After that, the conventions are incorporated into the various Twitter clients. I've been involved with an effort to improve the design of one of the most important elements of Twitter--the retweet. Most people use the standard "RT @name" to retweet content that someone else has written. The assumption is that this format indicates attribution of the source but virtually no change in the content. Another format "via @name" is supposed to be for retweeting with paraphasing or additional content. Everyone is aware of the former format but fewer are aware of the latter one. One of my followers proposed a new much more efficient format "~@name" which takes one in the place of three or four characters of the precious 140. It is also quite simple and elegant. Of course, I ran a poll on this too and the results showed that 69% of preferred to use the "~@name" format in place of at least some of the other formats. A full 37% want to replace both other retweeting formats with the tilde, 17% think that only the RT format should be replaced, and 14% believe that tilde should replace the "via" format. I'm now using "~@name" for all of my retweeting and encourage you to do as well.

I'm quite amazed at the ability to very quickly collect this type of information using Twitter itself. Of course, it is simply self-report and thus doesn't necessarily reflect reality perfectly. However, I believe this information provides interesting insights into key aspects of the Twitterverse. As always, I'd appreciate any thoughts you may have on any of this by using the commenting feature of this blog.

Wednesday, May 06, 2009

Design Mentoring

I've served as a mentor to many people over my career and have also learned a lot from the people who have mentored me. In fact, it was my mentees and mentors who inspired me to start the UXDesignCast and Life Habits podcasts. My experience of late communicating regularly with the more that 3,000 people who follow my two Twitter accounts gave me the idea to collect some mentoring wisdom from this crowd that I could share with everyone. I asked two questions that yielded some great responses.

What's the one thing you didn't learn in design (or other) school that you now believe is key to success?
  • How to play nicely with others -- art of influence versus trying to solo
  • Entrepreneurship, client communication, proper valuation of work
  • On the job there are way more people involved in the iterative process than there were in school; things aren't as flexible
  • Trusting your gut, "liking" the people you hire, and always standing up for what you believe in
  • Working with people across differences in discipline, background, and power - design as a social practice emphasizing diversity
  • How to listen -substantially underestimated
  • Speed is key to iteration. Trial & error trumps genius. Perfect is enemy of the good
  • Soft skills like persuasion, communication to marketing, developers, sales, CEO's, negotiating

What's the most insightful, interesting, or valuable thing anyone ever told you about design?

  • Best advice re design "simplicity, less is more, balance, specialist generalist, implicit communication, realign, define problem, iterate, reflect".
  • That you don't have to be "a designer" to be a designer
  • All Display Is No Display” From newspaper editor on art of balancing headlines (display) art & text.
  • (Industrial) Designers are "Specialists Generalists"; they need to know something about everything in order to do their jobs.
  • Design = implicit communication
  • Realign not redesign
  • Clearly define the problem, iterate often and step away regularly in order to reflect.
  • It was in London, during a lecture, someone told me : "every morning you are a designer" because of clothing.
  • "That is painful to look at."
I'd like to thank all those who provided input on this via Twitter and would like to invite you to contribute any additional thoughts you may have on either of these questions using the commenting capability of this blog.