Design

Ten Things You Need to Know About Design

by Joey deVilla on July 4, 2010

10 things about design

What you see above is a slide from Jason Putorti’s slide deck titled 10 Things CEOs Need to Know About Design. Don’t let the title throw you off: everything in the presentation is even more important for developers because we actually make the things our customers use.

If you decide to commit only one of these ten things to memory, commit this one: Design is more than pretty pictures. It’s about combining different aspects of intelligence – rationality, creativity and empathy – to meet your users’ needs and drive business success. It’s about crafting the user experience, which is how the thing you’re designing works in the real world and how your users feel about it.

I’ve included the slide deck below…enjoy!

This article also appears in Canadian Developer Connection.

{ 2 comments }

“I’m Comic Sans, Asshole!”

by Joey deVilla on June 15, 2010

"I'm Comic Sans, Asshole" -- John Marston from Red Dead Redemption pointing a gun

That most hated of typefaces, Comic Sans, gets anthropomorphized and bad-assified in Mike Lacher’s piece for McSweeney’s titled, (in)appropriately enough, I’m Comic Sans, Asshole.

This article also appears in The Adventures of Accordion Guy in the 21st Century.

{ 1 comment }

So You Need a Typeface…

by Joey deVilla on April 26, 2010

so you need a typeface flowchart

Got a project and can’t decide on a typeface? This chart is by no means complete, but it might help steer you in the right direction. Click it to see it at full size.

This article also appears in Canadian Developer Connection.

{ 1 comment }

Replica Spanish galleon on fire

Sometimes, you have to do more than just start from scratch. Sometimes, you have to burn the boats.

“Burning the boats” is an expression that comes from a story – some say legend — about Cortes, the Spanish Conquistador (and yes, the subject of Neil Young’s Cortez the Killer). Wishing to guarantee that his men would stay in Veracruz (which he’d just taken over from the Governor of Cuba) and only move forward into terra incognita without retreat, he ordered them to burn the ships that brought them to the New World. It was an extreme measure, but without the distraction of a way home, they committed themselves completely to business of exploring and conquering.

The Original Mac: No Arrow Keys

Bruce “Tog” Tognazzini, former user interface guy at Apple and the company formerly known as Sun, and now member of the Nielsen/Norman Group, wrote about how Apple burned the boats back when they released the original Macintosh in his 1992 book Tog on Interface and more recently in an article on his blog, AskTog.

Original IBM PC and Apple // computers

In 1984, the Macintosh represented a break from the dominant paradigm at the time: the command-line interface. Back then, you’d issue commands to a program these ways:

  • Typing them in
  • Using control-key combinations
  • Using function keys
  • Using the arrow keys to navigate

Software developers at the time had little experience developing for GUIs, which meant that there would be great temptation for them to simply develop apps for the Mac the way they did for other platforms. The software they’d end up writing would be a command-line app that just happened to run on the Mac.

Steve Jobs and Apple’s Macintosh team, an unconventional bunch who were said to have nary a classical computer science degree among them, thought that existing software sucked. I was 16 at the time, and I’d have to agree. In order to prevent straight ports of existing software to the Mac, they decided to “burn the boats” and make it difficult for developers to “go home” and simply rely on the UI techniques from the Old World. The first Mac keyboards didn’t just omit the function keys, they also left out the arrow keys:

Original 128K Macintosh. "See? No arrow, function or control keys."

Tog writes:

That was a big deal. Almost every application then in existence depended on the arrow keys (then called cursor keys) for navigation. With that one stroke, Steve reduced the number of apps that could be easily ported to the Mac from tens of thousands to zero, ensuring that this new computer would have a long and painful childhood.

It’s counterintuitive to want to have your creation go through a long and painful childhood, but there was a method to their madness. In “burning the boats” by getting rid of the function and arrow keys on which developers relied and taking away their “way home”, they forced developers to redesign and rewrite their applications to fit a mouse-driven graphical interface rather than a keyboard-driven command-line interface.

They eventually brought back the arrow keys about a year and a half later. By that point, developers had grown used to developing GUI apps that took advantage of the UI controls and mouse that we’ve come to know and love. The return of the arrow keys at that point would now be a welcome addition and convenience, rather than a dangerous temptation to return to “the old ways”.

It was a bold move, but when you’re making radical changes to the way things are done, bold moves are often required.

Windows Phone 7: No Copy and Paste

Copy and Paste icons

There’s been some talk about Windows Phone 7’s lack of copy and paste. It’s similar to the hue and cry about the original iPhone’s lack of copy and paste, and having been reminded by Tog’s article about the design decisions made for the original Mac, I can see the method to Microsoft’s madness.

“Copy and paste already exists in Windows,” people have said, “why not Windows Phone 7?”

The answer is simple: because Windows Phone 7 apps aren’t supposed to be like Windows apps. For non-enterprise, non-industrial use, the “Windows, but scaled down” approach of previous versions of Windows for phones, which goes under the name Windows Mobile, didn’t catch on (Windows Mobile still rules the roost for compact devices used in enterprises and industries, and will be supported for years to come). Hence Albert Shum’s completely different-from-the-desktop, and even different-from-other-phones Windows Phone 7 interface, which went by the codename “Metro”.

Windows Phone 7 hubs: music+video, people, pictures, office, games

The use of copy and paste implies a keyboard-centric user interface, which isn’t what Windows Phone 7 is about. People often use their smartphones one-handed, with only their thumb to access the touchscreen. Windows Phone 7’s interface takes this usage into account, which is why it’s sensor-centric, and applications, should get their information from touch, gestures, accelerometers, location and other sensors where possible. By not including copy and paste in the first release, the Windows Phone team is “burning the boats” and asking developers “How do you write apps so that they don’t need intricate more-suited-to-the-desktop operations like copy and paste?”

(And yes, copy and paste will eventually find its way into Windows Phone 7, just as the arrow keys, function keys and even right-clicking found their way into the Mac.)

The same could be said for many other things that were purposely excluded from Windows Phone 7, such as the compact edition of SQL Server that was part of Windows Mobile. If you think about it, this design decision forces you to build apps so they store and retrieve data from the network, which makes sense, since phones are devices that network with both cellular and wifi.

Windows Phone 7 represents a radical shift in the way Microsoft stuff works, from a very minimalistic look to its task-centric organization. In order to make sure that people built apps that fit it, the Windows Phone 7 team had to burn the boats. It’s a bold move, but it’s the right one.

{ 19 comments }

MIX10 Thoughts: Design, Windows Phone and Bill Buxton

by Joey deVilla on March 23, 2010

Joey deVilla and Bill Buxton posing on the dance floor at LAX nightclub in Las VegasMe and Bill Buxton at the MIX10 Attendee Party last Tuesday night.

There’s one reason I’m particularly excited about Windows Phone 7 Series. The radically reworked look and feel is the surest sign that the company is really beginning to understand design and is willing to start from scratch (a risky and pricey proposition) to get it right. It would appear from Microsoft’s Principal Researcher Bill Buxton’s interview in The Register that I’m not the only one who thinks this:

"We kinda changed the water that we drink, in the sense that all through the design community within the company we talk, and we have a common goal in terms of trying to bring a certain change of sensibility," he said.

"For me it’s not even about the phone, but what’s interesting is that it’s the first product in the company with critical mass that’s embraced this … it will have an impact on other parts of the company."

If (or better still, when) you start building Windows Phone applications – or hey, any kind of application — I hope that you’ll follow the spirit of “Metro” (the codename for the design philosophy behind Windows Phone 7) and keep it in mind. Yes, it’s absolutely important to know the Silverlight and XNA APIs as well as how to read the touch sensors, GPS, accelerometers and so on, but it’s just as important to design your applications around the people who’ll use them. That means understanding your users, how they’ll use what you’re making, knowing how to give them what they need as quickly and unobtrusively as possible and delighting them. Yes, “a pretty interface” is included in all that – and there’s research to suggest that beautiful interfaces work better –but looks are merely part of the design equation.

Some Design Sessions from MIX10

Want some interesting lunchtime viewing on design? Look no farther than these two videos.

The first is Bill Buxton’s MIX10 session, simply titled An Hour with Bill Buxton, a conversation about design:

Get Microsoft Silverlight
Don’t have Silverlight? Get it here or download the video in
WMV, WMV (High) or MP4 format.

If you haven’t the time to watch the video of Buxton’s presentation, check out this hit list of metaphors complied by Sharon Chan at Microsoft Pri0.

If you’re planning on getting into Windows Phone 7 design, you’re going to want to learn the “design language” – not a programming language, but the guiding principles and philosophies behind the new user experience – behind it. Here’s the MIX10 presentation on that topic, Designing Windows Phone 7 Series with Albert Shum, Michael Smuga and Chad Roberts:

Get Microsoft Silverlight
Don’t have Silverlight? Get it here or download the video in
WMV, WMV (High) or MP4 format.

A World Without Design

Here’s a little something extra for those of you who like to think about design and user experience:

"A World Without Design": The same rock, described as a hammer, doorstop, paperweight and so on.

I whipped up this graphic, modelling it after a poster I remember seeing many years ago. I can’t remember what it was for – a museum, art gallery or exhibit, perhaps? – but I remember thinking that it was right on the money. If you remember the original poster and what it was for, please let me know, either via email or the comments!

This article also appears in Canadian Developer Connection.

{ 0 comments }

Get Microsoft Silverlight
Don’t have Silverlight? Get it here or download the video in
MP4, WMA, WMV, WMV (High) or Zune format.

Welcome to another installment of Counting Down to Seven, a series of articles about mobile app development that I’m writing as we count down the days to MIX10, when we reveal more about the up-and-coming Windows Phone 7 Series.

"Counting Down to Seven" badgeWe’re a week away from the start of the MIX10 conference! I like to refer to this as Microsoft’s most “right-brained” gathering, as its target audience and topic isn’t just developers and writing software, but designers, design and user experience.

With designers and design in mind, it’s only fitting that I show you a video featuring Nic Fillingham interviewing a couple of Microsoft User Experience gurus who also hail from Canada:

  • Bill Buxton: He’s a Principal Researcher for Microsoft Research, and before that, he was Chief Scientist at Alias Wavefront and a professor at University of Toronto. And I’m pleased to report that he got his bachelor’s degree – in music – from my alma mater, Crazy Go Nuts University (which some of you may know as Queen’s University). He was the guy who thought of applying Fitts’ Law to human-computer interaction, did some pioneering work with multi-touch interfaces and invented the pie menu (which means that we owe weapon selection in Saints Row 2 and the full combat/spellcasting system in Dragon Age: Origins to him).
  • Albert Shum: He’s the Director of Mobile Experience Design for Windows Phone 7. Albert’s from Winnipeg, studied engineering and architecture at University of Waterloo and went on to do design work at Nike before joining Microsoft. You can watch a video showing him talking about the new Windows Phone 7 experience and the thinking behind it in a previous article of mine, Albert Shum on Windows Phone 7.

This article also appears in Canadian Developer Connection.

{ 0 comments }

Counting Down to Seven: Lou Reed, Mobile App Designer

by Joey deVilla on February 22, 2010

Three Weeks to Go!

Counting Down to Seven (Mar 15th at MIX 10): A series about ideas for mobile appsWe’re three weeks away from the day when a lot more about Windows Phone 7 will be revealed. On Monday, May 15th, the MIX10 conference in Las Vegas is expected to open with a bang as developers and designers will learn about “WP7’s” programming and design models as well as the opportunities that Microsoft’s reworked-from-the-ground-up mobile phone OS will provide. As part of a team of evangelists who were picked to champion WP7, I’m looking forward to getting my feet wet developing for this new platform and sharing what I learn with all of you.

As good as the early indications are – the demos are impressive, and this is likely the first time that anything made by The Empire been described as “soulful” – WP7’s introduction won’t be without some significant challenges. As far as current-generation smartphones go, WP7 is a late entry into a fiercely competitive market featuring a rival who can boast about having an impressive 100,000 applications in its store. There’s the matter of the wait; the 7 Series phones won’t hit the market until later this year, and in the meantime, the Esteemed Competition will be releasing new models. There will also be the cries of “Too little, too late,” from the people who observed Microsoft squander an early lead with smartphones (I can understand the argument for “late”, but having seen some advance inside info on what these babies can do, “little” is not a valid argument).

The Real Challenge

Windows Mobile 6 user interfaceI think that the biggest challenge is going to be creating a new Windows Phone culture. I believe that one of the problems with the developer culture surrounding the old Windows Mobile was that they treated the mobile phone as simply a shrunken-down version of the desktop. As I’ve written before, the desktop is what made Microsoft a successful company, but it’s also turned into an albatross that has impeded forward movement. The company built their mobile OS in a specific way with a specific design philosophy for a specific audience: “suits”. The developers took their cues from those decisions and built applications to match. The end result wasn’t pretty in any way: business-wise, functionally or aesthetically.

We – that’s both Microsoft as well as the development community that we want to gather around Windows Phone 7 — need to create a culture that “gets” the smartphone and cares about software craftsmanship, both in the underlying programming as well as in the user experience. I want to see a development culture that encourages both technical and design chops, the way that the iPhone community does, as well as that the way web app developers like 37signals do. I want Windows Phone to set the standard for mobile applications.

To that end, I decided to write this series – Counting Down to Seven – as a way to get developers to start thinking about mobile applications. I’ve been looking at applications written for the Esteemed Competition’s phones, books and articles on mobile development for other platforms and ideas from the world of user interface and user experience design as well as from science fiction (a long-standing source of ideas for neat-o devices that fit in your pocket). My hope is to convince you not just to write apps for Windows Phone 7, but also to write apps that redefine mobile computing, do interesting and useful stuff and delight our users.

Take a Walk on the Phone Side

Lou Reed, in sunglasses, with a cigarette

There’s a mobile app that was designed by Lou Reed. Yes, that Lou Reed – the guitarist, vocalist and songwriter for the Velvet Underground, then Mr. Walk on the Wild Side and more recently, Mr. Laurie Anderson.

The app is called Lou Zoom, and although he didn’t implement it (that job went to Ben Syverson), he came up with the idea and co-designed it. That’s the sort of excitement that I’d like to see behind Windows Phone 7: so full of possibilities that even people who’d never think of designing applications start doing just that.

The idea behind Lou Zoom is quite simple: it’s a contact manager app, like the Contacts app that comes with the iPhone. The difference is that it has a couple of tweaks, no doubt born out of frustration with the current app. I’ve listed the tweaks below:

Tweak #1: Easy-to-Read Contact List

In the standard Contacts app, the list of contacts is shown as a standard list, with all entries the same size. In Lou Zoom, the list of contacts has variable-sized names: each name in Helvetica Neue, with the font size increased so that it is fills the width of the screen. Here’s a screen shot taken from the Lou Zoom page:

Screenshot of contact list from Lou Zoom app

This design might make the sort of designers who prize uniformity cringe, but think about this: phones have small screens and are often used in less-than-ideal reading conditions. If you’re going to remain under 30 forever, are guaranteed to always have 20/20 vision and vow to always remain stationary and alone in a well-lit room, you don’t need this feature. For the rest of us – including me, a guy in his early forties with standard issue Asian myopia, who finds himself squinting more and more at small type, who often uses his phone from places like dimly-lit cabs going over potholes at breakneck speeds or in crowded, dimly-lit conference spaces and having had a couple of caesars – this user interface tweak is very helpful indeed.

Tweak #2: Easy-to-Read Contact Pages

Just as the contacts are listed in nice big type, so is the info on each contact page:

Screenshot of contact info page from Lou Zoom app

As with the contact list, Lou Zoom goes for legibility and displays the information in large type. It goes one step further by displaying the text in high contrast. If the contact has multiple addresses, phone numbers or email address, a left or right swipe over the appropriate field will give you those alternates.

An Aside: Windows Phone 7’s People Profiles

The “Profile” page in Windows Phone 7’s “People” hub takes an approach that is stylistically similar to the way Lou Zoom displays contact info:

Screenshot of Windows Phone 7 profile page for a person in the "People" hub

…but it takes a markedly different approach to which items are displayed prominently. Windows Phone 7’s design is centered around what you want to do rather than with just throwing information at you. For example, the actions “call mobile”, “text mobile” and “call home” are in large type, while the person’s mobile and home numbers are in smaller text. This is a good idea — after all, what you really want to do is reach someone, not look up their phone number. The “address book” paradigm is a holdover from the days when phones weren’t smart enough to dial themselves.

Tweak #3: Search on Any Part of the Name

The standard Contacts app has a simple search function. Type in j and it will immediately present you with a list of all names in your contacts beginning with “j” (ignoring case, of course). If you expand that j to become john, you’ll get a list of all the names in your contacts beginning with “john”. The Contacts app will apply the search term you provide only to the leftmost end of the names in your contacts:

Screenshot of search for Lou Zoom app

Lou Zoom improves on search by letting you search on any part of the name. Typing in john gives you a list of all the names in your contacts containing “john” in any part of the name, such as “John Smith”, “Alice Johnson” or “Olivia Newton-John”.

The Lou Zoom site provides its own example:

Has Kate Bell recently become Kate Appleseed-Bell? Searching for "Bell" will still bring up her name in Lou Zoom. From there, her full info is just a tap away.

It’s also great for searching for people by nickname. For instance, typing in mclovin into Lou Zoom’s search will give you the name of your buddy, who’s listed in your contacts as Christopher “McLovin’” Fogell.

What Can You Tweak?

It’s time to take a page from Lou Reed’s book and find apps that could benefit from a little tweaking. Look around at mobile apps and if you find yourself and other people saying “if only it did this”. Those are opportunities! The best applications aren’t always brand-new paradigm-shattering ideas; sometimes they’re old ones with a couple of tweaks.

This article also appears in Canadian Developer Connection.

{ 0 comments }

Jason Alderman’s Pitch for His MIX10 Presentation

by Joey deVilla on January 14, 2010

Two days remain for you to cast your vote for sessions at the MIX10 conference, which I wrote about in the previous article. A number of people who submitted proposals for sessions are wooing voters, and one of the best promotions is that of Jason Alderman, who put together this comic explaining why you should vote for his session, titled Guerilla User Research – Carrying Out Missions Behind Enemy Lines to Get the Insight You Need:

Comic: MIX10 needs a session (or two) on user research and testing!

This lovely hand-drawn comic is a reminder for me to fire up the scanner I bought for Christmas and get back to something for which I was notorious during my days at Crazy Go Nuts University: cartooning.

This article also appears in Canadian Developer Connection.

{ 0 comments }

MIX10 Web/UX Conference: March 15 – 17 in Las Vegas

by Joey deVilla on January 13, 2010

MIX10: The Next Web NowI’m going to be at Microsoft’s MIX10 conference, which takes place from Monday, March 15th through Wednesday, March 17th at the Mandalay Bay Hotel in Las Vegas, where I’ll be catching sessions and posting photos and reports. If you can spare a couple of days off work to attend Mix10, you should too – and soon, because the early bird discount is going to evaporate very soon!

What is MIX?

MIX10: Where designers and developers intersect to make the web a great place

The email sigs for people involved with MIX claim that it’s a “designer/developer lovefest for the web”, and I think it’s a pretty one-line summary of the event. It’s a conference for people who develop and design for the web, with particular attention paid to user interface and experience. This will be the 5th MIX conference, the first one having been held in 2006.

What Sort of Sessions Will There Be at MIX10?

The future of web design and user experience

Here’s a selection of some of the sessions and workshops at MIX10:

There are some other cool things happening at MIX10 that I can’t talk about until the conference. Be there, or if you can’t, watch this space!

You Get to Vote!

Open call for content voting is live. Vote now for your favortie session submissions.

You can help choose some of the content for MIX10! We took a number of submissions for presentations in an open call for content, and now it’s time to vote for them. You can see all the submissions here, and voting ends on Friday, January 15th.

Early-Bird Discount

Register by Jan. 15th and save: $600 on your pass and a free night at Mandalay Bay

If you register for MIX10 by January 15th, you’ll save US$600 off the admission and pay only US$795 – and you’ll also get a free night at the conference hotel, Mandalay Bay! After the 15th, the price goes up to a full US$1395, so if you want to go, register now!

This article also appears in Canadian Developer Connection.

{ 1 comment }

Folda Lisa

by Joey deVilla on January 6, 2010

The Mona Lisa, made up using folders in different shades of yellow and brown
Found via Certified Bullshit Technician.

This article also appears in The Adventures of Accordion Guy in the 21st Century.

{ 0 comments }

Building Apps People Need (and are willing to pay for)

by Joey deVilla on January 5, 2010

If you’ve taken a psychology course or have leafed through a user experience book, you’ve probably come across a diagram of Maslow’s Hierarchy of Needs:

Maslow's hierarchy of needs: from top to bottom -- 1. Self-actualization (Personal growth an fulfillment) / 2. Ego/Esteem (Achievement, status, reputation) / 3. Social (Belongingness, love, family, relationships) / 4. Safety (Protection, security, order, stability) / 5. Physical (Food, shelter, warmth, sleep)

Dan Zambonini of the web development shop Box UK took some inspiration from it and wrote an article titled Web App Business Models: User Needs and What People Pay For. In it, he writes:

As customers, we have a finite number of needs that we’re willing to fulfill by parting with our hard-earned cash. If you’re planning a web application that can’t build a business model around one or more of these needs, you may face difficulties generating sustainable revenue.

He breaks down people’s needs into the following categories, with an explanation of each one:

He also looks at how much people are willing to have different needs fulfilled. For example, people are willing to pay geometrically increasing prices for increasing comfort. Consider the 15x price difference between “cattle class” and first-class tickets on an airplane (even though both depart and arrive at the same times), or the 27x price difference between a bargain-basement pillow and a down-filled one:

Charts showing geometrically rising prices of increased comfort (economy/premium economy/business/first class plane seats and basic fibre/duck down/goose down pillows)

Entertainment, on the other hand, is a different beast. According to Zambonini, across the wide array of entertainment options from games for their mobile phones to vacations in the tropics, people are willing to pay the same rate: $5 an hour…

Chart showing linear scaling of entertainment prices

He categorized the top 100 U.S. sites by the needs he listed — here’s how they break down:

Pie chart showing breakdown of top 100 US websites by needs fulfilled: Entertainment (30%), Wealth (20%), Education (14%), Esteem (11%), Time (10%), Belonging (6%), Survival (6%), Comfort (2%), Scarcity (1%)

Naturally, such categorization is subjective and had to be drastically simplified, with each site being slotted into a single category. Sites about food were put into the “survival” category, even though a top 100 site on food would probably cover things like gourmet food and wine, which could arguably be put into the “entertainment”, “comfort” and even “esteem” categories.

He closes the article with a series of questions that you should ask about your application, such as “Does my app allow the user to do something more quickly?”, “Does my app allow the user to express their creativity?”, “Does my app provide entertainment for the user?” and so on. Your should be able to answer “yes” to at least one of these questions, and better still, you should be able to explain why.

Links

This article also appears in Canadian Developer Connection.

{ 1 comment }

Qixing’s Big Move

by Joey deVilla on January 4, 2010

Good Luck, Qixing!

QIxing Zheng in her TechDays 2009 orange speaker shirt

We may be losing a User Experience Evangelist, but I think we’ll get a great Windows 8 in return. Qixing Zheng, who’s been with Microsoft Canada’s Developer and Platform Evangelism team for the past three years, is leaving to join the Windows UX Team as a Program Manager. While I saw firsthand that she enjoyed her work as a UX Evangelist, talking to developers and designers about building usable, comprehensible and beautiful applications, joining the Windows UX Team is the opportunity of a lifetime. After all, how often are you given the chance to design something that will get used all the time by millions of people, all over the world, at work, play and in their day-to-day lives?

Qixing’s been the sole writer for the Canadian UX Connection blog during her tenure. She posted her farewell article, A New Year and a New Beginning, on January 1st, but don’t think that’s the last you’ve seen of her online. She promises that she’ll be blogging soon – she’ll let us know where, and I’ll let you know in turn. In the meantime, you can follow her on Twitter, where her handle is @hundredflavour.

What About User Experience?

Windows 3.1, as seen using the garish yellow and red "Hot Dog Stand" colour scheme

While I’m glad that Qixing is going to be applying her skills and knowledge to Windows’ user interfaces, there remains the need for someone to help developers, designers and people who play both roles build useful, usable and beautiful interfaces, applications and experiences. This is becoming even more important as mainstream software development extends beyond the desktop OS to the web, mobile phones, tablets and even big-ass tables.

I’m planning to pick up some of the slack in the tech blogs where I write, Canadian Developer Connection and Global Nerdy. In addition to articles on programming, industry trends and reports from the field, I’ll also be posting articles about usability, user interface and user experience, as seen from the developer’s point of view. I’ve had some experience in this area, and where my skills and knowledge fall short, I can always call on my “friends in UI places” and bring their opinions and know-how to you.

Once again, congratulations Qixing, you’ve been a great teammate — and yes, we’ll keep evangelizing user experience!

This article also appears in Canadian Developer Connection.

{ 0 comments }

Is Your Code a Candidate for “There, I Fixed It”?

by Joey deVilla on October 27, 2009

There, I Fixed It is a hilarious photoblog that catalogs kludges, jury rigs and hastily-improvised duct-tape repairs and modifications to everyday objects. The photos below are a sample of some of the quick fixes shown on the site, each one somewhere on the spectrum spanning “clever and thrifty” to “cheap, shoddy and frightening”:

There I Fixed It

(Regarding the photo in the right column, second one from the bottom – the piece of paper attached to the pencil sticking out of the computer says “Pull to turn on”. It’s a jury-rigged replacement for the power switch.)

Sloppy work like this isn’t limited to the physical world. I’ve seen (and okay, sometimes I’ve written) code that could’ve been a candidate for There, I Fixed It, and chances are you have too:

  • Some of my hacks were a little more elegant and useful in the long-term, as long as you weren’t going to be too fussy about aesthetics. They were the software equivalent of the CD-ROM drive installed below the car radio and attached to it with a cable with 1/8” stereo jacks. They weren’t pretty, but they were solid, reasonably maintainable and viable in the long term.
  • Others were terrible kludges that were originally intended to be temporary solutions that forgotten and lived much longer than they should have. They were like fixes shown in the two photos on the bottom (the hasty bridge repair and the car exhaust held together with zip-ties).
  • I’ve also copped out by glossing over bad user interface design with some explanatory text or dialog box instead of actually correcting the design. This is not unlike labelling a doorknob “hard to open” or a hastily-improvised switch “pull to turn on”.

Be sure to check out There, I Fixed It. They’ve had some pretty hilarious pictures lately, and perhaps it’ll inspire (or shame) you to eschew the quick fix or kludge in favour of putting some time and thought into writing better code and building better user interfaces.

This article also appears in Canadian Developer Connection.

{ 1 comment }

being_better_is_better

Kathy Sierra, who co-created O’Reilly’s “Head First” series of books and who used to write the very inspirational Creative Passionate Users blog, is awesome at helping users become awesome. I use her lessons as guidelines in my evangelism work and even borrowed from her to create a catchphrase that I used when interviewing for my job at Microsoft: “My goal is to help developers go from zero to awesome in 60 minutes.”

The blog O’Reilly Radar points to a great Ignite presentation (a style of presentation that’s restricted to 20 slides, each auto-advancing every 15 seconds for a grand total of 5 minutes) in which Kathy Sierra talks about ways to make your users awesome. The presentation is titled Being Better is Better, and I’ve posted it below, followed by point-form notes, which I took so that it’s easier for you to become awesome at making your users awesome:

  • If we want to create passionate users, we need to help them get better.
    • ‘Nobody’s passionate about things they suck at.”
    • Many people still have their cameras permanently set on “P” – automatic mode — even though those cameras offer finer control over things like shutter speed and aperture
    • What would it mean to our users if we unlock the door and help them be awesome?
  • In Malcolm Gladwell’s book, Outliers, a major theme is the “10,000 Hour Rule”, which states that it takes about 10,000 hours of practice to become really good at something.
    • 10,000 is a long time – it’ can be a depressing prospect
    • [Joey: According to Outliers, 10,000 hours makes for about 3 hours of focused practice every day for 10 years.]
    • To get good, you have to practice all the time.
    • Anything that makes it easier for your users to get practice – any time, anywhere – will help them get their 10,000 hours (and get good) sooner.
  • Give your users patterns for success
    • In any pattern you give your users, make sure that there’s “the one thing” that they can take away as a lesson
    • You need to answer the question: “What’s the one thing you can do to be amazing?”
  • Give your users better gear
    • They’ll work better
    • “Spend the money!”
    • Give people a way to justify the better gear you’re offering them
  • Motivation is important
    • Treat motivation as a gift
    • Make a product that people will actually use
    • “Your treadmill is not in the corner gathering dust because you don’t use it, you don’t use it because it’s in the corner.”
    • “Make the right thing easy for people and the wrong thing hard.”
  • And now, some anti-patterns:
    • We focus on the tool and not the thing the users want to accomplish with the tool
    • “We treat people really well before they buy, and afterwards, we treat them poorly.”
      • This is also the reason people don’t want to upgrade
      • If we want to help people upgrade – which is what they’ll need to do if they want to go forward – we have to accept that it’s a loss and a hit to their self-esteem
    • We write FAQs as if our users they were intellectually curious and have a tablet PC handy
      • People hit the FAQs and help because they’re having a horrible experience
    • “Don’t let the ease-of-use police” step in an dumb something down
      • You don’t feel awesome when you’ve mastered something that a 3-year-old can master
    • Hiring a social media consultant is the wrong thing to do
      • They focus in the wrong direction
      • Social media consultant are focused on making your users love you, which is the wrong thing – nobody is awesome because they love you
      • They think the goal is to make users want to party with you
      • The true goal is to make your users want to party because of something you did that helped them become awesome. They should want to party because of you, but without you
      • You want to connect users with other users, not with your company
      • A much better use of social media is to find out:
        • What role we play in our users’ lives
        • What role our competitors play in our users’ lives
        • What the pain and pleasure points for our users are
      • By trying to be competitive and focusing on our competitors, we end up being uncompetitive
        • This leads to featurities
        • We end up building things that end up harming our users
        • The best thing we can do is to look at the bigger, cooler thing – the world in which our products and our competitors’ products exist, the problems that the products are trying solve, the things at which our users are trying to kick ass – and blog, tweet and use social media about that
    • Getting WOM (Word-of-Mouth) may be the social marketers’ holy grail, but the true goal is WOFO – Word of [Effing] Obvious.
      • If your users are so good, you get WOFO.

This article also appears in Canadian Developer Connection.

{ 5 comments }

24 Years of Windows Packaging and Boot Screens

by Joey deVilla on October 17, 2009

TechRadar UK is publishing a series of “Windows 7 Week” articles, some of which take a look back at the history of Windows. One of the articles presents a timeline of Windows packaging, from version 1.0 to 7:

windows_packaging

…and another is a chronology of Windows’ boot screens:

windows_boot_screens

This article also appears in Canadian Developer Connection.

{ 0 comments }