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…)

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…)

Act without doing;

Think without effort.

Think of the small as large,

and the few as many.

Confront the difficult,

while it’s still easy.

Accomplish the great task,

by a series of small acts.

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

When I first came to the States, I carried with me a lot of stereotypical expectations nourished by the American media that I was exposed to before I arrived. One of them was about medicine. And of course, no show gave a better stereotype about it than E.R. My first month in America proved the medicine stereotype to be completely bogus. When I broke my toe by accidentally hitting the bed frame in the middle of the night, I did what I’d always done when I broke my finger playing basketball: I taped it to its neighbor. But then I thought that I might as well explore the marvels of American medicine and visit a clinic. The conversation went something like this: (more…)

About a year ago, I had an experience that taught me one of my life’s biggest lessons. I learned it the hard way. Probably the most painful way.

A couple of friends and myself got together in Borders and sat down to chat about some ideas we had, and pick one to start working on. We had big ideas. Ones that can potentially change the world. Surprisingly, one small and simple idea kept presenting itself in many of the things we’ve discussed. One that’s so trivial that anyone can sit down in a couple of weeks to design it, code it, and publish it. We decided to give it a shot anyway, and to see how our collaboration will turn out. We all had our own thriving consulting/freelancing business, and we agreed to to this work on the side, in Google’s 80/20 manner. (more…)