Amir Khella

[Inspired by Caleb Chung’s TED talk.]

In the summer of 2004, I had my first entrepreneurship experience in an unlikely place. I was still working on my PhD, when I received an invitation to spend the summer at Microsoft Research. Some of the finest researchers there have been working my topic of interest, and I was eager to see what they’d been working on, and to contribute to it. So I took the blue pill.

After the first day orientation, I went to my mentor’s office to find out which project I’d be working on. When I sat across the desk, he peeked at me through the stacks of research papers and notes, and said with a big smile: "Well, here you are. You’ve got 12 weeks to spend with us, so come up with something useful and exciting!" I looked at him waiting for a specific task, and he proceeded " You’ve got access to hundreds of researchers and thousands of employees. Make good use of it. Good luck!". He then introduced me to the rest of the team members, and showed me the way to my office where I would spend the next 12 weeks coming up with the next big thing. Or at least, that’s how I felt back then.

On the following morning, other interns were already printing out research papers, looking at source code, and discussing tasks among their teams.  I didn’t even know where to start. I was scared and excited.

(more…)

During a pitch practice at the Founder Institute, I heard something that really captured my attention and  inspired me to think about product stories in a new way. After describing a scenario, the founder in the hot seat said:

“… and I want to own that moment.”

I started thinking about which successful products own which moments in my daily life. Here are some examples:

• ” I want to share some files with my team”. DropBox owns that moment
• “I’d like to show you how I am imagining this interface”. Balsamiq owns that moment
• “I want to embed a form in my blog”. Wufoo owns that moment
• “I want to create a cool slideshow for my website”. Animoto owns that moment
• “I am starting a new client project”. BaseCamp owns that moment
• “I’d like to know what my friends have been up to lately”. Facebook owns that moment
• “I’d like capture some thoughts.”, Evernote owns that moment.

You get the point. (more…)

Yesterday, I read a post on Derek Sivers’ blog about how drama can be mapped on a two-dimensional charts, and I was inspired to think about the user’s journey through a product in a similar fashion.

One of the most useful design practices to create good landing pages is to visualize each website visit as a journey that leads users to a destination. That destination is not just a goal that the user needs to accomplish, but also an emotional state that the user would like to experience.

It’s important to understand that the journey doesn’t typically start when the user reaches a product’s homepage. It starts earlier, when she identifies a need to have or accomplish something, or when she finds a recommendation from a friend or blogger to try a new product. When she comes to the site, she will have many questions in her head that she wants answered.

There is a wide range of emotions that users experience during a website visit, including: indifference, boredom, confusion, disappointment, curiosity, engagement, and ecstasy.

Let’s look at how a good design can create an ecstatic user experience:

(more…)

When the iPhone O/S update brought a voice recording feature to the device, I was happily surprised because I love using recorders to take voice notes on the go then transcribe them later on.

When I started using the application, I liked the visual skin of the application but was frustrated by its usability: the application, as shown below, dedicated the largest screen real-estate to a giant microphone icon, and placed the functional buttons of the app in the two bottom corners, occupying less than 5% of the screen space. (more…)

Few months ago, we started experimenting with a new Design workflow that we called D3. D3 stands for Deep Dive Design. Prior to D3, we used a communication-intensive process where we involve clients and users in the input and output of each design iteration: vision, usability metrics, stories, tasks, requirements, brainstorming, sketches, wireframes, and visual designs. The earlier and more frequently we communicated, the better quality designs we got, and the happier clients and users were.

We then thought about raising the communication bar further, and wondered what it would be like to have clients as active participant in the design process. So we decided to invite each client to spend a full week on-site with us. During that week, the client brings marketing, business and engineering team members to our offices and we spend 5-6 hours a day together, working on the following: (more…)

During the 2008 web 2.0 expo in San Francisco, I held a round table discussion about design thinking for start-ups. The premise of the discussion was to 1) learn the difference between design (the artifact) and design thinking (the mindset), and 2) to discuss how to integrate best practices for design thinking into the product life-cycle. Start-ups running on shoestring budget cannot typically afford big consulting agencies like IDEO. But that shouldn’t stop them from becoming design-driven, and use the available tools and processes to differentiate through design and user experience. If you’d like to get your company up to speed with design thinking best practices and tools, get in touch with me for an on-site training session.

[Update] This presentation is currently featured on SlideShare’s homepage

[Update 2] I’ve received numerous emails and comments asking about the video for this presentation. I will be delivering a webinar next month that will use this presentation as a guideline to discuss the topics covered, answer the most common questions that I received so far, and dive into some case studies. If you’d like to be notified when the webinar is available, please sign up here.

During the last startup weekend, a friend pointed me out to a fun tool for creating  typographic word clouds called wordle. Today, I decided to play more with it and I gave it the testimonials that clients left in my LinkedIn profile.

After some tweaking to the fonts and colors, here is what the output looks like:

Click on the image to see it in full resolution.

Last year I worked with Delve Networks to design their user experience. This week, O’Reilly’s InsideRIA blog mentioned Delve as one of the most usable Rich Internet Applications.

Here is what Theresa Neil thought of the design:

Delve designers realized content creators weren’t interested in navigating through a bunch of screens to accomplish tasks. They have applied the one-screen-per goal philosophy which results in a lot less screens, each with deep interactions. To keep these rich screens from being completely overwhelming they have employed the following patterns: inline editing, dialog overlays, refining search, and progressive disclosure.

This is a very accurate description of our design goals. We were not interested in creating yet another digital asset manager. We studied the tasks that users wanted to perform at every step, and we took a task-centered approach in creating the interface and interaction. One of the unique interaction paradigms in Delve is that each screen contains a component that acts as a bridge to connect it to subsequent screens and tasks. Animated transitions are used to enforce that mental model for the user and keep them in context while taking them to the next part of the interface.

Here is a demo of Delve’s UI in action