Great UI’s can’t be rushed

Why?  Because even simple UI’s are complex.  There’s:

  • The need to understand who’s using your product
  • The need to understand what users are trying to do.
  • The need to understand what scenarios the UI will handle
  • The concept brainstorming stage
  • the concept fleshing out stage
  • interactive prototyping
  • Feedback throughout the design process
  • The front-end code
  • The back-end code
  • The speed of the app
  • The layout
  • Responsiveness
  • The copy
  • Typography
  • Colors
  • The page hierarchy
  • The interactions
  • White space
  • Motion
  • Personality to convey
  • A story to tell
  • Feedback states
  • Error states
  • Accessibility
  • Small delightful details
  • Internationalization
  • Retina considerations
  • Considerations for decisions vs. options
  • Browser testing
  • Device testing
  • The brand to consider
  • What did I miss?

When designs are rushed to ship, for whatever reason, chances are some of these items will fall through the cracks.  Bottom line: great UI designs take time to craft. Great UI’s can’t be rushed.

Early on, even great user interfaces suck

And that’s okay…

In fact, that’s the way it should be.

Consistently great UI designs must be crafted through a process.  This process will vary from designer to designer, and will likely change over time.  Here’s the process I lean towards these days:

  1. Gather data (who is this for, what are they trying to do, what scenarios should be considered)
  2. Based on the data, I sketch out lot’s of rough low fidelity concepts
  3. I’ll spend some time stewing on these concepts
  4. I’ll then select one concept (the one that best fits all of the criteria outlined in step 1), and flesh it out in more detail (usually still sketching with pen and paper at this stage)
  5. Get feedback
  6. Build out a rough interactive prototype (usually coded by hand, but I’ve been playing with Macaw and I’m liking it for rough prototypes)
  7. Get feedback
  8. Code it up right and add polish
  9. Get feedback, make tweaks - rinse and repeat this step until everything is just right

Myth #1: as you get better at design, you can skip some steps

Great UI designers do not skip steps just to save time.

Myth #2: the sooner you can get to a hi-fidelity design, the better

Great UI designers do not jump to high fidelity designs sooner than is necessary.  In fact, they tend to delay it as long as possible.  Great UI designers recognize the benefits of lo-fi designs, and leverage those benefits extensively.

Up until around step eight (more than half way through the process) it’s perfectly fine for your designs to still look unfinished.  The longer you can stick with lo-fidelity the better.  There are a couple of reasons:

  • Lo-fi concepts take less time to create
  • Since they take less time, you can create more of them, giving you more options to choose from
  • It’s easier to scrap a design that is lo-fi and start over
  • It’s easier to iterate on lo-fi designs
  • It’s easier to solicit candid feedback when people don’t think you’ve spent as much time on the concept

Early on, all UI’s suck, and it turns out, that that’s the way it should be.  If you outright skip steps in the design process, or if you hop straight to hi-fi mockups, your designs will tend to suffer as a result.  Great UI designs follow a process, they take time to craft, and early on, even great user interfaces are going to suck.

Note: inspiration for the title of this post came from Ed Catmull who said “Early on, all movies suck”, speaking candidly about the state of early movie concepts at Pixar.

Startups, what if you never hired dedicated support people?

I’m curious, are there any web companies – with 10 or more employees – that do not have at least one dedicated support person?

Hiring a dedicated support team is one of those things that every company seems to do without thinking about it, as if it were a requirement. But what if you didn’t? What if the founders, designers, and developers in your company continued to support your users indefinitely?

It would likely seem unnatural at first. The founders would have to lead by example. Else, I’m positive it would not work.

But I’m curious, with direct daily feedback from actual users:

  • would the designers design better products?
  • would the founders stay more in tune with users, thus prioritizing feature development more effectively?
  • would developers be more motivated to find creative ways for users to resolve their own problems?
  • would designers & developers instinctively fix more bugs?
  • would the overall product and user experience be better as a result?
  • would it be sustainable & scalable?

NOTE: I’m not trying to diss anyone in dedicated customer support roles. To the contrary, many of you are some of the hardest working, untiringly empathetic, and all around coolest people I’ve had the pleasure of working with (Both at Automattic, and Campaign Monitor).

My big hypothesis here is that by forcing founders, designers and developers to share the support load, and not pawn it all off on someone else, chances are:

  • founders and designers would have a much clearer vision of what they should be building throughout the life of the business.
  • your product would be better, because designers and devs would experience the pain users go through, and fix more things along the way.
  • your customers would get answers to their questions faster, because your developers – seeking to automate repetitive tasks – would invest more time in solutions for users to solve their own problems. Thus reducing the support load by reducing the number of support tickets that get created in the first place.

I’m mostly just curious if this has ever been tried.

Perfectly Impatient Ramen

I love ramen.

When I get in the mood for Ramen (usually after 10:00pm), I’ll do just about anything to get my hands on some.

A couple of things to keep in mind:

1) I live in Apex, NC.  The epicenter of Ramen, it is not.
2) I’m cheap.  There’s a place you can get Udon from nearby, but it’ll run you about $15.00 (including tip).  If I were in SF, or NYC, I’d happily pay $12-20 for a good bowl of noodles.  But not in Apex…

What to do…

Instant ramen has been a part of my life for as long as I can remember.  I have fond memories of coming home from school, sitting down to watch cartoons, eating a bowl of Maruchan Ramen, with a glass of Tropical Punch Kool Aid to wash it down (those were the days).

Unfortunately (or perhaps fortunately), Maruchan with it’s default seasoning packet just doesn’t do it for me anymore…

My ideal ramen solution:

  • Available, even after 10:00pm.
  • Tasty noodles cooked just right.
  • Meat, and veggies are mandatory, but should require as little effort as possible.
  • Ramen broth made from scratch in a big batch, which can then be used for half a dozen bowls.
  • Broth needs to take at most 20min to cook – I don’t have patience for the traditional 8-48 hr broth.

I’ve played around with a bunch of different ramen hacks.  After much experimentation, I think I’ve settled on the perfect solution (at least for me).

Here’s my approach:

NOTE: I use approximations for everything.  My cooking skews more towards art than science.  I measure nothing, and never follow a recipe.  I cook by taste.

The broth (prep time 10-20 min)

  • Cooked rotisserie chicken (usually from Target) – I pull the white meat, and shred it
  • 1 carrot – shredded
  • 1 bunch of green onions – chopped
  • Chicken bouillon + Mr. Yoshida’s (this is the magic ingredient) – 90% chicken broth 10% Yoshida’s
  • Fish sauce – just a dash

This gives me a good batch of broth:

The noodles (prep time 0 min)

I’ve tried a bunch of the instant ramen noodles.  Even tried making my own.  In the end, I always come back to Maruchan.  I just use the noodles, and throw the seasoning packet away.

The bowl (prep time 5-8 min)

Whenever I get in the mood for ramen, I ladle out a couple spoons full of broth:

I’ve got some pre-diced cabbage, and shiitake mushrooms that I toss in:

I bring all of that to a boil, and then toss in the Maruchan noodles:

I let it boil for another couple of minutes and Voila:

Ramen purists, I mean no disrespect. While this is no perfectly crafted bowl of ramen, it’s about as close to (admittedly impatient) perfection as I can get.

Shiny New Idea Syndrome

I have SNIS. As far as I can tell, it’s genetic (my dad has it too), and it’s nearly impossible to overcome.

I grew up in an entrepreneurial home. Dad was an entrepreneur who got distracted easily. He would start a business, get it running to the point that it was no longer a challenge, and then lose interest and abandon it for another shiny new idea. I witnessed this dozens and dozens of times throughout my life.

You’d think that I’d have learned from his lesson. But truth be told, I’m drawn to the exact same behavior, and it’s maddening.

Let’s say I start a side project with the intention of devoting a year to it…

Sure enough, not even 2 months later, there I am, tinkering with another shiny new idea. It doesn’t make sense. It’s eternally frustrating.

The interesting twist is that there are some things that I have no problem sticking with. I’ve been married for 11 years for example, and have no problems sticking with that (I love you Liesl!). I’ve worked at Automattic for close to 4 years, and have no intention of leaving any time soon. I’ve had the same hair style for longer than I can remember. ;-)

What is it about side projects that makes them so fleeting for me? If you’ve experienced this yourself, how has it affected you?  Any thoughts on how I might train myself to stick with something, and avoid that inevitable shiny new idea?

Thoughts?