5 Questions to Ask for a Better Solution

Are you a business owner or product manager looking to improve the design of your product? Even if you do not have a designer on staff, you have design minded team members that can be guided with right questions. Here are some questions to ask to get your team to drive to the optimal solution.

Question 1: What is the problem you are trying to solve?

There is a tendency to jump immediately to solutions without first stating the problem. Stating and clarifying the problem itself will crystallize the issue for both the product manager and the team. Ask this question to have team members verbalize the problem.

For example, I had a project manager ask me to design an icon to put on the screen. This button was the solution he determined for the customer problem. I asked him a series of questions around the problem and it turned out the button was a band-aid that would resolve the specific customer request. The real problem was much larger. Users were not able to get their work done smoothly and they wanted to speed up a process they did frequently throughout the day.

Question 2: Who has this problem?

There is a tendency to focus solutions on the most recent set of user requests or complaints, rather than generalizing to the overall user population. This question is asking about the persona or the archetype of the user. Identifying the persona determines the persona’s needs, goals, activities, environment and how the company wants to interact with this type of user. 

For example, I had a project manager come to me for help with a specific product enhancement. One customer was asking for a specific feature. By having a conversation about the type of user this request came from, we were able to do a better job of generalizing the problem and solving this issue for a greater number of customers.

Question 3: What is the user trying to do?

Understanding the context of the interaction is the essence of user experience and product design. Everyone should be clear on the tasks and workflows that the user is doing when encountering this problem. Diagramming, story-boarding, or videotaping helps to communicate the workflows clearly to the team.

For example, I have been designing software for traders. Traders work in an information dense and noisy environment. Many traders attend to 3 to 6 monitors, multiple phones and a TV broadcast while in an open space with many people talking and shouting. The trader runs several applications with very different visuals. Each application has many moving parts: flashing data, programmed sounds and interdependent information. How do you design incoming information about a stock that is not visible on any screen without interrupting the traders current work? Knowing the context of the environment will ensure a design that meets the users needs.

Question 4: How are we going to design the product?

As the business owner you should expect many solution ideas for each problem. All possible solutions that impact the user should be sketched. Encouraging many different team members to sketch on their own will triangulate on a better design than one person designing.

For example, I worked on a project where not only did the internal team come up with sketches but so did the client. We presented and explored the sketches everyone put forth. We compared two designs to identify what worked and what did not work (do not allow personal opinions unless you are building the product for that individual). This was one of my most successful designs from the perspective of user acceptance and client and team buy-in.

Question 5: How are we going to figure out which design is going to work?

Identify the three best designs to prototype. Create and review a storyboard for each of the designs. Have the team prototype the designs on paper, in PPT, Balsamiq or whatever means that result in a quick turnaround.

For example, I use PPT to mockup and prototype the UIs. I have created PPT squares that illustrate the UI framework we are working with, which allows anyone to  prototype and edit the screens. Since interaction design requires small movements and transitions, I have found PPT very useful to illustrate small changes that the user can click through. The PPT click-through allows the user to move forward and backward at their own pace and replay the interaction over and over. I have found that some users will be able to provide feedback as to whether the design solves the problem or not. I look for trends to emerge.

The result of this process is that you will get quick, tangible feedback from users before coding has begun. Completing the process allows more members of the team to be able to accurately visualize the solution, resulting in team cohesion and better execution in the engineering stages. These steps provide a rapid means of investigating the solution space and throwing away poor ideas before time is spent coding. In hours or days, depending on the size of the problem, you come away with a more confidence in the design of the solution.


Hiring an interaction designer?

Do you know what you are looking for? Do you know what to ask? Do you know what to look for? Do you know who they would work for? Why?

In the enterprise software world, what do you want to look for in an interaction designer? What is an interaction designer? Do they just drawing pretty pictures?

Interaction designers focus on how the user flows through the application. Their goal is to make the user’s life as easy as possible to get their task or job done. So what do they do? I like to describe the responsibility of the interaction designer is to understand the context of the business problem and the limitations of the technology to deliver the best design to be built. An interaction designer spends 80-90% of their time communicating. Working with business people, product managers and users to understand the context and the problem, translating that problem into design choices that is narrowed to the best solution and then representing the different stages of design to different people in the way they need to see it.

So here is what I did.

  1. I screened my candidates by having them send a resume with a portfolio. The portfolio is a visual resume. Very little of this can show interaction but it does show communication tools.
  2. If they pass I had a 45 min conversation with the designer. I wanted to find out how well they listened to me and then communicated their abilities. I also had them descibe their design process to see how they approach design to see if they can fit with the team. 
  3. If they passed, they had to call back the next day with 1/2 hour of questions. Every good interaction designer should know how to ask questions all the time. Here I was looking at how they asked their questions and whether I thought their was a fit for the team.
  4. If they passed we had them in for an in-person interview. Here they needed to take a couple of hours with the team explaining their work. Walk through examples and answer questions. Here is where we would bring up examples of challenges to see what the candidate would do. Would they ask more questions? Did they show examples? Did they just jump into the answer?

Interaction design is not about the answer. There are many answers to a problem. Interaction design is about the questions. The interaction designer needs to gather enough information to make reasoned choices in the design process. At each stage in the process he will need to work with users, business people, product managers, designers and technologists.

Are you hiring an interaction designer? Make sure they can fit culturally within your team since they will be spending so much time trying to influence and communicate.