Design Problem Solving: A Task Analysis

  • Balakrishnan Chandrasekaran

task design problem solving

How to Cite


Developed By

Part of the PKP Publishing Services Network

Copyright © 2021, Association for the Advancement of Artificial Intelligence. All rights reserved.

More information about the publishing system, Platform and Workflow by OJS/PKP.

Lucia Z. Wang

Apr 19, 2017

Task analysis for design problem-solving

One of the most critical tools in the UX designer’s toolbox, task analysis helps us break down a complex process into step-by-step tasks, so we can look at the challenges the users faced in his/her entire journey with greater detail.

According to this book User and Task Analysis for Interface Design , the purpose of task analysis is to understand:

Now I rephrased some of the pointers, but the key takeaway remains the same: task analysis is meant for us to understand user goals through reliving their experience step by step, and thus gain a thorough understanding of the influences that shape their decisions and workflow.

One way to do this objectively is to write out the observed hierarchical task analysis . But since I’ve committed to being a visual thinker and creating whiteboards whenever possible, I’m going to draw out the task analysis for someone who wants to paint the room here.

As I drew the process, a few things jumped out to me:

This little drawing exercise turned out to be very beneficial! Now if I’m design a product or service that helps people like Joe to paint their rooms better, I know to offer the below in order to close the need gap:

What are your thoughts? Is your process different?

More from Lucia Z. Wang

Art school graduate & human-centric technologist. Freelance UX/UI designer specializedin FinTech. Portfolio at

About Help Terms Privacy

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store

Lucia Z. Wang

Text to speech

task design problem solving

UX Collective

Enrique Hinzpeter

Aug 6, 2020

How to solve a Design Task, step by step

What is a design task.

It is a part of the interview process used to recruit UX Designers, Product Designers, and UI Designers, based on the principle of showing a working process. It is one of the most common interview stages for designers.

After a series of interviews, it is very common for designers to be asked to do a Design Task. Most of them are focused on the company’s products, although in some cases those tasks can be external products. The goal of these tasks is to be able to show recruiters your skills in the process of redesigning or creating a product.

Some examples of design tasks are

What should I know before I start?

Consider the following points before starting to work on the task:

Read the entire Task: It’s important that you carefully read the whole Task. You should read it and re-read it until you feel you understand everything. Asking questions: If you are not sure of something or you don’t understand the Task very well, you need to raise your hand and ask the recruiter your questions. It’s better to ask in time before handing in the wrong solution. This will also help to reflect how you will work in the new company. Give hundred and ten percent: Companies are always looking for candidates who go that extra mile. It’s your time to be able to impress them, always try to put yourself in the position of the recruiter and try to imagine what would impress you about a candidate. Beware of spelling mistakes: It is very important that when you finish your Task, you check it multiple times to make yourself sure that no spelling mistakes are missed. You want to show your attention to detail and a spelling mistake could be a serious mistake in the eyes of the recruiter.

How to solve a Design Task?

This is the framework with all the steps and information that will help you get that job as a Product Designer, UX Designer, Web Designer, among others.

To explain each of the steps of the methodology I will show an example of how I solved the following Design Task:

“The new Health app of iOS consolidates data from your iPhone, Apple Watch, and third-party apps you already use, so you can view all your progress in one convenient place. For this Design Task we would like you to propose new features that increase the DAU (Daily active User) in the iOS Health App.”

The first slide should always be a simple cover with the title of the Design Task, your name, the logo of the company you are applying to and an image.

2)Design task

Write down all the information you were given about the Task along with an image.

3)Design process

Put in a visual way what will be your design process in each of the steps. This way the recruiter will know where he is in the process.

4)Context Study

You should research all the information needed to understand the product, its purpose, its history, its users and hard data. First take notes on sheets or Post-It’s and then, pass that information on a summary.

5)Competition Research

This will help see how other products were tackling this issue and taking notes of the things I did and didn’t like. Make a summary of the competition and create a graph with “x” and “y” axes to be able to see areas of opportunity within the other products (the axes should evaluate problems that your product solves).

6)User research

Research everything about the users. There could be different methodologies to learn about them, for example:

With the information provided by the User Research you will be able to create the Personas. A Persona is the representative of a group of users with their context, which will help us understand and visualize how to create solutions that meet the needs and solve the problems of a specific number of people. (Create from one to three People depending on your time limit)

8)Information on Personas

Depending on the needs of the users and the problems of the product, the information to be carried by each Persona is different. Have at least the following information:

9)Understand the context and the need of the user

The objective is to understand with each persona how was its experience while using the product. In order to do this, you need to create individual tables with the following information:

10)List of User Problems

Once you have the context of the product and the users, you need to create a list of the users problems. Based on the Personas you created, write in Post-It’s all the problems these users have. Once you have a good number of problems, select all the problems that the product can solve and create a list with them.

11)Prioritize the problems

After having discovered a number of problems that users have, it is necessary to prioritize the problems to know which ones you are going to work with.

In order to do that, you must ask yourself three questions for each problem:

Give a grade from 1 to 3 to each question. 1 is low and 3 is high. At the end, add up the scores of the three questions to get a total score. The problems with a higher score will be the problems you will solve.

12)Choose problems

After prioritizing the list of problems, it will be easy to realize that many of the problems may share the same essence or solution. You need to identify these groups of problems and summarize them into one. Depending on the time limit you have on the Task, you can choose one or more problems to work on.

13) List of solutions

For each problem, you should make a list of solutions based on the information from the Context study and the User research . Brainstorm different solutions in Post-It’s and stick them on the wall. Try to make as many solutions as possible (try to think outside the box).

14)Prioritize solutions

Based on the same questions you asked yourself to prioritize the problems, you must now evaluate each solution with that same table and choose the one with the highest score.

15)Choose solutions

After prioritizing the list of solutions, it will be easier to find the solution that will generate more value, that will be easier to implement and that will help the product in the specific objective of the Task.

16) User cases

The user cases define specific events in the use of the product where it describes how the Persona interacts with the product and for what purpose. Try to remember all the information obtained in the User Research step.

17) User Touch Points

These are the moments when users interact with your brand, product or service. Developing and understanding what happens at each touchpoint will help you design a better experience.

18) Journey map UX Flow

The Journey Map tries to capture the user experience during the interaction with the product. It is a visual journey of the user through the product to the solution. In each interaction, the feelings, pain points and other moments that the user will experience must be specified. There are several layers within the Journey Map such as actions, contact points, pain points, experiences and opportunities.

19) Design System

A design system it’s a single source of truth that brings together all the elements that will help the design teams make and develop a product. This will constantly evolve along with the product. These elements must be taken into account when designing the Interface.

20) Solution — Sketches and Wireframes

After understanding the user process and the needs at each step, you should start brainstorming to generate the first solution. Start with different pencil and paper drafts, to make the process faster (make the user flows and maps simple).

21) Solution — User flow

It is the complete display of a user’s path through the Interface in order to complete a task. It will take you through all the steps, up to the solution of the problem.

22) Solution — Wireframes

A Wireframe is a design that demonstrates which elements of the interface will exist on each of the screens. It is a critical step in the design process.

23) User test — Low fidelity

The objective of this user test is to identify problems or possible improvements within the product before moving on to the final design phase. Depending on the time you have to do the Task, it is advisable to do at least one user test. To do this test, you must create 4 tasks that a user must do.

These tasks should take him through all the features of your new product or function. While the user completes these tasks, you should monitor him to see how he is doing, the difficulties he may encounter and write down all these interactions. You should give a value of 0 to 3 to each task, 0 being when the user had a lot of difficulty in completing the task and 3 when the user found it very easy and intuitive.

24) User test — Results

You should visualize the results of the user tests and make an average of them so that it is easier to perceive errors or possible improvements within the product. This will help you learn what works and what doesn’t, why it works and why it doesn’t, as well as the user needs that you may have overlooked. After analyzing this data, it will be much easier to perceive the errors that you can correct.

25) Information Architecture

The information of architecture serves to visualize in more detail the user flow through the screens. It is important to do this after the user testing, in case any modification is necessary.

26) High-fidelity prototypes

With the conclusions of the user tests and the identification of errors, it is necessary to iterate once again the design proposal. Once you are completely satisfied, start creating the high-fidelity prototype. The best tool to do this is through Sketch or Figma .

28) Interface and interaction design

It is very helpful to create animations to show what the transitions and user flows of the interfaces would look like. The best tool to do this is Principle.

Here you can learn how to use this software with the Help of Pablo Stanley

29) Mockups

Create several Mock-ups so you can show how the product or features would look like.

30) Results

It is very important that in this last slide you highlight the following points:

Remember to have fun and show all your skills! Design Tasks are a great way to practice and continue improving. I’m sure that if you follow all these steps you’ll get your dream job. Good luck!

If you are interested on this content, you can download the editable file of this presentation by clicking here .

More from UX Collective

We believe designers are thinkers as much as they are makers. Curated stories on UX, Visual & Product Design. · 459K followers

About Help Terms Privacy

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store

Enrique Hinzpeter

I’m Enrique Hinzpeter. Product Designer focused on creating designs that improve the life of others. Based in Berlin. @DeliveryHero

Text to speech

Popular related searches

task design problem solving

How to improve your UX designs with Task Analysis

One of the most important steps in the Design Thinking process that is often employed as standard practice in UX design is to define the users’ problems. This means being able to clearly identify and articulate problems in the user experience so that you can later begin the process of ideating (i.e., generating great ideas on how to solve them). Task Analysis is a simple exercise that UX designers can undertake during the definition of a problem, which can help not just in identifying where opportunities to improve the user experience exist but also to generate some preliminary ideas as to how you might approach these challenges. Let’s find out how.

Task analysis is one of the tools that you can use during the “define” stage of the Design Thinking process. The most frequent deliverable of a task analysis activity is a diagram explaining the steps that a user must take in order to complete a goal. In this diagram, you can depict the actions taken by the users (or some system) to help them achieve their goals. Once you have laid all the steps out, you will then be in a position to see where additional user support is required (for example, you might wish to automate some actions that the user currently undertakes), or eliminate unnecessary steps, in order to minimize the number of actions that a user has to undertake, unassisted.

Joann Hackos, communications expert, and Janice Redish, UX consultant and writer, advise that task analysis is useful for understanding (1998):

Your users’ goals and what they are trying to achieve

The steps that your users currently take in order to achieve their goals (very helpful to see how they follow instructions or have devised ways to work around problems in current practices!)

The personal, social and cultural experiences that users bring to the tasks

The influence of the physical environment on the users while attempting to meet a goal

A clear understanding of the above factors will help you to define and frame the users’ problems so that you can then ideate ways to help improve their experiences.

Preparing to conduct a task analysis process

Usability professionals Courage, Redish and Wixon (2007) argue that task analysis is an activity based on four core principles:

It is an integral part of a broader analysis that includes understanding users and their environments.

Task analysis includes understanding users’ goals.

Although the focus, methods, granularity, and presentation of information may differ at different times, task analysis is relevant at all stages of the design and development process.

The practical reality is that task analysis for a given project depends on many factors.

Breaking down these principles, you will notice that the first two advocate for a deep understanding of users, their environments and their goals. Since the Design Thinking methodology produces outputs during each step, it’s natural to expect that task analysis is a process that has to be informed by the outputs of the previous phase—i.e., empathizing with your users. During this step, you may have already undertaken user interviews , or collected data through observing how your users go about their daily lives, in order to understand them better and build empathy with them. In short, you will have engaged in some user research , which may result in several outputs such as user personas , scenarios and storyboards . All of this data is essential for task analysis, as you will base your work according to these outputs.

Of course, just collecting any data during your user research is far from enough. If you plan to use task analysis (or indeed many of the other tools in a UX designer’s skillset, such as customer journey maps ), your data collection must be focused. Larry Marine, a UX consultant, argues that your user research should focus on collecting the following five types of data, which you will use later during the task analysis phase:

Trigger: What prompts users to start their task?

Desired Outcome: How users will know when the task is complete?

Base Knowledge: What will the users be expected to know when starting the task?

Required Knowledge: What the users actually need to know in order to complete the task?

Artifacts: What tools or information do the users utilize during the course of the task?

First steps in Conducting a task analysis

Armed with the information you gathered during the empathy phase, you can then begin to sketch out how a user goes about his or her daily life by mapping out the sequence of activities required to achieve a goal. Before you begin, it’s important to have an overview of the process and its steps, so you can better prepare.

According to the UXPA’s Usability Body of Knowledge Site, the process of task analysis can be broken down into the following steps:

Identify the task to be analyzed: Pick a persona and scenario for your user research, and repeat the task analysis process for each one. What is that user’s goal and motivation for achieving it?

Break this goal (high-level task) down into subtasks: You should have around 4–8 subtasks after this process. If you have more, then it means that your identified goal is too high-level and possibly too abstract. As Don Norman (1998) said, users are notoriously bad at clearly articulating goals: e.g., ”I want to be a good mom” – where do you even begin? Each subtask should be specified in terms of objectives. Put together, these objectives should cover the whole area of interest—i.e., help a user achieve a goal in full.

Draw a layered task diagram of each subtask and ensure it is complete: You can use any notation you like for the diagram, since there is no real standard here. Larry Marine shares some helpful advice on the notation he uses, which is examined below.

Write the story: A diagram is not enough. Many of the nuances, motivations and reasons behind each action are simply lost in the diagram, because all that does is to depict the actions and not the reasons behind them. Make sure you accompany your diagram with a full narrative that focuses on the whys .

Validate your analysis: Once you’re happy with your work, review the analysis with someone who was not involved in the decomposition, but who knows the tasks well enough to check for consistency. This person can be another team member working on the same project, but you could also enlist the help of actual users and stakeholders for this purpose.

One more trick you might wish to consider is conducting a parallel task analysis. This means simply to get more than one person on your UX team to undertake the process simultaneously—so that you can later compare your outputs and merge them into a final deliverable. This can be especially helpful if you are working internationally, or where multiple personas have to be considered for the same goal.

task design problem solving

Author/Copyright holder: University of Strathclyde, Management Science Dept., Wikimedia. Copyright terms and licence: CC BY-SA 3.0

An example layered diagram from a task analysis process (goal: warm up a furnace)

Types of Task Analysis

You can approach a task analysis activity from two main viewpoints. So far, we have discussed breaking down tasks into sub-tasks, an approach termed Hierarchial Task Analysis. However, you can also differentiate your viewpoint by focusing on tasks that require decision-making, problem-solving, memory, attention and judgment. This process is called a Cognitive Task Analysis . From this viewpoint, you would be concerned not just with how the actual activities involved in meeting a goal are performed but also with finer details that aim to uncover how a novice might perform compared to an expert, the level of cognitive load required for each step, how experts make decisions, or how users develop mental models for an activity which are later reused or adapted for other purposes.

An example of Task Analysis

Let’s now work through an example to illustrate how you might undertake a task analysis. Assume that Rosie, a home-visit doctor, needs to update the hospital’s system with her whereabouts (i.e., that she’s left one patient to go to the next) via text message. Rosie uses a custom device which appears to be a mobile phone but is tailored for use by doctors. All she needs to do is send a short SMS-like text with the words “next patient” to a certain number.

Goal: 1. Send a text message to hospital’s system

1.1. Open the messaging application on her mobile phone.

1.2. Enter the hospital system’s special number.

1.3. Move to the text input field.

1.4. Type the words “next patient”.

1.5. Check the spelling (because it needs to be precise for the system to accept it).

1.6. Hit the “send” button.

1.7. Exit the messaging application.

task design problem solving

Author/Copyright holder: Andreas Komninos, The Interaction Design Foundation. Copyright terms and licence: CC BY-SA 3.0

A sample task analysis diagram for sending a short message to the hospital system. Note how each step represents a sub-task that can be broken down into further sub-tasks.

In the above diagram, you will notice that we have identified different “plans” about how Rosie might achieve a certain goal. In the diagram, pretty much everything except for displaying matching contact names is performed by the user. We can see that Rosie is not getting much support here. Perhaps we can intervene by redesigning the device’s messaging application.

We can eliminate the “hit search icon” step by showing a list of matching contacts to Rosie as soon as she begins typing any letters or numbers in the “To:” text input field.

We could even eliminate the typing by displaying a “frequently used contacts” dropdown under the “To:” field, even when Rosie hasn’t yet typed anything.

We can help Rosie spellcheck her message by highlighting the words that are spelled incorrectly or by causing the device to vibrate whenever a word is misspelled.

In order to prevent errors, we could disable the “send” button if spelling mistakes are present in the text.

We can eliminate the “exit message” step by automatically closing the messaging application once the message has been sent.

You will note that some of the ideas for improvement discussed here are based on the simple hierarchy of tasks (i.e., eliminating needless steps), whereas others depend on a cognitive analysis approach (i.e., lessening the mental workload of the user). What we ultimately decide to do will depend on how the user visualizes the problem. If the users believe that entering correctly spelled text is the source of their greatest frustration, then our design should focus on that aspect. Solving the real issues has the biggest impact on the project, and you should continuously strive to see the task analysis from the user’s perspective and not what you could actually do (or want to do).

“In my 25 years of experience on over 250 projects, not one single product has been focused on solving the right problem.” —Larry Marine, UX consultant

Larry Marine likes to annotate his task analysis diagrams using different colors in the various flows:

Green represents the actions that users need to do.

Yellow represents a step the system can do.

Purple represents objects, tools, or information that the users need.

Orange represents questions or issues about the task.

A task analysis would probably have a greater proportion of “green” flows originally. A re-designed task would probably have fewer “green” and more “yellow” flows, to show that you’ve really managed to off-load tasks from a user to a system, thus improving their overall experience by making their lives easier.

The Take Away

Task analysis is one of the most powerful tools in a UX designer’s skillset. As you will have undoubtedly seen, it’s not hard to get to know how to do it. However, the difficult part is remembering to keep the user’s perspective and resist the temptation to generate your own interpretations of the problem, or to “stick in” bits of design just for the sake of doing it. Remember also that task analysis is useless when it isn’t backed by rigorous user research. Without user research data, any efforts to proceed with task analysis will be in the blind and will result in failure, because you will be capturing mostly what you think the problem involves, as opposed to what the users’ actual needs are. Remember also that task analysis is not a one-off process. You can repeat it on your own designs later in the process, since Design Thinking is an iterative process that will eventually lead you back to the “define” stage at some point. Finally, remember that—like any other activity in UX design—task analysis requires time, resources, people and budget. Be sure to balance these requirements carefully and engage in the process only if you have a sufficient amount of all!

References & Where to Learn More

Hero Image: Copyright holder: falcowata, Flickr. Copyright terms and license: CC BY 2.0

Christou, G. & Saraiva, C. (2012). Hierarchical Task Analysis

Courage, C., Redish, J. G., & Wixon, D. (2009). Task analysis. Human-computer interaction: Development process, 33-53.

Hackos, J. T., & Redish, J. (1998). User and task analysis for interface design .

Hornsby, P. (2010) Hierarchical Task Analysis

Marine, L. (2014). Task Analysis: The Key UX Design Step Everyone Skips

Min, L. (2014) Experience mapping vs. Task analysis

Saraiva, C. & Bevan, N. (2012). Cognitive Task Analysis

Sudhindra, V., & Saraiva, C. (2012). Task Analysis

Task Analysis, according to

User Experience: The Beginner’s Guide

task design problem solving

Get Weekly UX Insights

Topics in this article:, make design better: share this article, what you should read next, how to change your career from graphic design to ux design.

task design problem solving

Apple’s Product Development Process – Inside the World’s Greatest Design Organization

task design problem solving

What is Interaction Design?

task design problem solving

Shneiderman’s Eight Golden Rules Will Help You Design Better Interfaces

task design problem solving

The Principles of Service Design Thinking - Building Better Services

task design problem solving

A Simple Introduction to Lean UX

task design problem solving

Dieter Rams: 10 Timeless Commandments for Good Design

task design problem solving

The Grid System: Building a Solid Design Layout

task design problem solving

The 7 Factors that Influence User Experience

task design problem solving

Adaptive vs. Responsive Design

task design problem solving

New to UX Design? We’re giving you a free ebook!

The Basics of User Experience Design

Download our free ebook The Basics of User Experience Design to learn about core concepts of UX design.

In 9 chapters, we’ll cover: conducting user interviews, design thinking, interaction design, mobile UX design, usability, UX research, and many more!

New to UX Design? We’re Giving You a Free ebook! is archived and no longer updated

External links may not function and information on the site may be out of date. Visit for current information.

expand navigation menu

task design problem solving

Home > How To & Tools > Task Analysis

Task analysis is the process of learning about ordinary users by observing them in action to understand in detail how they perform their tasks and achieve their intended goals.   Tasks analysis helps identify the tasks that your website and applications must support and can also help you refine or re-define your site’s navigation or search by determining the appropriate content scope.

Purpose of Task Analysis

In their book User and Task Analysis for Interface Design , JoAnn Hackos and Janice Redish note that performing a task analysis helps you understand:

When to Perform a Task Analysis

It’s important to perform a task analysis early in your process, in particular prior to design work.  Task analysis helps support several other aspects of the user-centered design process, including:

Types of Task Analysis

There are several types of task analysis but among the most common techniques used are:

How to Conduct a Task Analysis

Your task analysis may have several levels of inquiry, from general to very specific.  In addition to market research, competitive analysis, and web metrics analysis, you can identify top tasks through various user research techniques. 

Site exit disclaimer

It’s important to note that you need to decide to what level of detail you are going to decompose subtasks so that you can ensure that you are consistent across the board.

At a bare minimum to identify tasks, you can simply ask users what overall tasks they are trying to accomplish or how they currently accomplish the task.

What overall tasks are users trying to accomplish on our website?

How are users currently completing the task? People are completing that task using:

Related Content

Related Resources

Related Categories, go to the homepage

U.S. Flag

task design problem solving

Nov 7, 2021


How to Solve a Product Design Challenge

Improve your chances of success with these tips.

Hurray! You’ve passed the Portfolio Review and have now reached the final stage of the Product Design Interview: the Design Challenge. Admittedly if this is your first time interviewing, a Design Challenge can be nerve-wracking!

I will walk through an example of a Design Challenge that I submitted as part of my interview with Canva and highlight ways in which you can prepare for your own submission to improve your chances of success.

What’s a Design Challenge?

A Design Challenge is a way for employers to assess how well you approach design problems and is often a good way to put your skills to the test. This typically happens towards the final end of the interview after you’ve completed the Portfolio Review. There are typically two types of Design Challenges that an employer can ask you to solve:

White Board Challenge

Expected time: 30min — 1 hour

A whiteboard challenge is usually done live in front of a panel of interviewers. This type of challenge will allow you to collaborate with the interviewing team and demonstrate your ability to problem-solve on the spot.

Take Home Design Challenge

Expected time: 4–6 hours

The take-home Design Challenge is done (as the name suggests) at home, separate to the live interviewing process. This type of challenge allows you to spend more time focussing on the end-to-end design process and go deep into tackling a complex problem or scenario that you normally wouldn’t have time to complete during a shorter interview.

Why a Design Challenge?

A Design Challenge is a practical task to assess how well you approach design problems by applying your design skills to a real world scenario. The goal of this exercise is not to focus solely on the end solution, but to understand what your process is and evaluate where your strengths and opportunities lie. In addition to this, recruiters also look for these skills:

How should I approach the Design Challenge?

Regardless of whether this is a take home or whiteboard challenge, you should aim to communicate your design process and the steps you took to get to the solution as part of your submission.

Consider using the Product Design Process to guide your approach:

Example Design Challenge: Spotify Kids

This was a Design Challenge that I completed as part of my interview with Canva two years ago. Coincidentally enough, Spotify went ahead and launched their own version of the product a few months later!

Spotify has captured a majority of the music streaming market. Their product design is clean, clear, steps back and lets the artists shine. However, Spotify have left one segment out of the mix — children.

Internal research has shown that kids between the ages of 3–6 years old either don’t have any access to Spotify or have to ask their parents to play their favourite music. Artists like The Wiggles, Peppa Pig and Yo Gabba Gabba are all missing out on customer engagement and revenue. It feels like the Spotify experience is aimed at grown-ups chilling out and rocking out; not for kids who like to have fun, dance and goof around.

YouTube has a standalone experience for kids. Spotify want to explore the same space — an unbundled, unique kids music experience. Spotify Kids wants to be the best music app for kids.

As part of the Spotify product design team, you are leading the design team to create the best music app for kids. The starting point is the music player UX. Focus on the Spotify native app only — your choice on either iOS or Android.3

1. Start with Why

Before you jump into solution mode, take a moment to understand your goal. Don’t be afraid to ask your interviewer clarifying questions to understand what their expectations are and what you should be aiming for.

It’s important to describe the context of the problem and its significance in a few sentences. Consider the following:

In my case study, I focussed on communicating the positioning of the Spotify Kids brand in relation to the main Spotify product:

A brand for Spotify’s boisterous little cousin. Spotify is looking to diversify their proposition and explore an untapped market that offers an unbundled, unique kids music experience for young children. We created Spotify Kids, an app that parents could trust and allows 3–6 year olds to select and stream songs so that they can easily access and enjoy listening to their favourite music.

Spotify is a music, video, and podcast streaming service that aims “to help people listen to whatever music they want — in a completely legal and accessible way”.

How might we:

2. Empathise with your users

Once you’ve established your Why, show how you conducted research to understand your user’s pain points to define your user persona:

I conducted desk research to understand the needs of 3–6 year olds and the parents of 3–6 year olds:

Children (3–6 year olds):

Parents of 3–6 year olds:

From these insights, I went ahead and fleshed out the key product requirements. The Spotify Kids experience should meet the following criteria:

3. Define the scope

Mapping out the user journey will help to communicate the end to end experience of a product from a user’s perspective. You should use a flowchart tool such as Figjam , Whimsical or Miro to show what steps a user would take to complete key actions in your product. Consider the following:

For the Spotify Kids user journey, I identified the following tasks that a user should complete to achieve their goal:

I also went and defined what was critical for MVP vs. a nice to have (post-MVP):

4. Generate ideas to the solution

If you’re working on an on-site exercise, aim to deliver the following:

For take-home exercise, the final deliverables would be a high-fidelity clickable prototype, but all the techniques described above would be used to create a foundation for the high-fidelity solution.

Competitor analysis

Competitor research is important in the ideation stage as this allows you to refer to how other products have solved for this problem and also potentially seek inspiration for new ideas. Consider:

I conducted competitor research with children apps such as YouTube Kids, Foxtel Kids, Khan Kids, ABC Kids, Endless ABC, Nickelodeon Play and identified the following common design patterns:

Parental controls

I then considered these patterns as part of my design solution in the high fidelity prototype. As a general rule, aim for 6 screens at a maximum when you are designing the end to end experience.

5. Prototype the solution

Once you have settled on a final solution, it’s time to mock it up in a design and prototyping tool. I would recommend using Figma but you can also choose something like Sketch or Marvel .

For the Spotify Kids app, I had a prototype prepared but I also crafted slides for the key screens to communicate the core parts of the user journey.

Browse music.

Users can either browse by:

Music player

Once inside the Spotify player, users can:

Search songs

Settings for the app are gated with questions that can only be understood by parents. This allows parents to set a timer on app usage, manage child profiles, and more.

6. Measure success

Remember to tie your solution back to the original goal of this project by considering how you will track the usage of your feature in product and specifically which success metrics you should be monitoring.

Some useful metrics to monitor would include:

To measure the success of the Spotify Kids launch, we would look at the:

7. Next steps

Lastly, talk about the things you would’ve done if you had more time or what you would do differently. Recruiters may ask further questions related to your submission so be prepared to answer these. Consider the following:

Key takeaways

Final words

Finally, know that an interview is not just a one-way conversation — it’s a two way street. Treat this as an opportunity to learn more about the company and whether the role fits in with your goals as a designer. Don’t forget to ask the interviewer questions towards the end. Good luck!

Subscribe to learn more

Thanks for reading! If you want to learn more about other design topics, sign up to Medium to read more of my stories .

Feel free to subscribe to me via email or connect with me on Linkedin if you’d like to chat or just to say hi!

Ready to take the challenge?

We’re hiring at Canva ! Come and join one of Australia’s fastest growing startups where our mission is to empower the world to design. Take a look at the roles available here !

More from UX Planet

UX Planet is a one-stop resource for everything related to user experience.

About Help Terms Privacy

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store

Product Designer at Canva

Text to speech


  1. What Is Problem Solving In Design?

    task design problem solving

  2. Problem Solving Tools

    task design problem solving


    task design problem solving

  4. Powered by Design: An Introduction to Problem Solving with Graphic Design » GFxtra

    task design problem solving

  5. Infographic Design Elements With Six Options For Problem Solving Steps Stock Illustration

    task design problem solving

  6. Problem Solving Design Thinking TASK A3

    task design problem solving


  1. Philadelphia Science Festival: Fashion Design Problem Solving


  3. Task Analysis

  4. Main Task

  5. Dynamic Task Assignment

  6. Unit 3 Multitasking task state segment part 1


  1. What Are the Six Steps of Problem Solving?

    The six steps of problem solving involve problem definition, problem analysis, developing possible solutions, selecting a solution, implementing the solution and evaluating the outcome. Problem solving models are used to address issues that...

  2. How Do You Solve a Problem When You Have Different Bases With the Same Exponents?

    When multiplying or dividing different bases with the same exponent, combine the bases, and keep the exponent the same. For example, X raised to the third power times Y raised to the third power becomes the product of X times Y raised to th...

  3. What Is a Task Environment?

    An organization’s task environment is the collection of factors that affects its ability to achieve goals. Common factors in the task environment include competitors, customers, suppliers and distributors.

  4. Design Problem Solving: A Task Analysis

    The analysis shows that there is no one ideal method for design, and good design problem solving is a result of recursively selecting methods

  5. Design Problem Solving:A Task Analysis

    WINTER 1990 59. Design Problem Solving: A Task Analysis1. B. Chandrasekaran. Design problem solving is a complex activity involving a number of subtasks.

  6. Task analysis for design problem-solving

    Task analysis for design problem-solving · User goals: what they are trying to achieve · What is needed to be done to achieve these goals · What

  7. How to solve a Design Task, step by step

    Once you have the context of the product and the users, you need to create a list of the users problems. Based on the Personas you created

  8. How to improve your UX designs with Task Analysis

    Task Analysis is a simple exercise that UX designers can undertake during the definition of a problem, which can help not just in identifying

  9. Task Analysis

    on understanding tasks that require decision-making, problem-solving

  10. Thinking in Alternatives—A Task Design for Challenging Students

    To challenge organic chemistry students to shift their problem-solving approach from rote learning to meaningful learning, we designed task

  11. How to Solve a Product Design Challenge

    A Design Challenge is a practical task to assess how well you approach design problems by applying your design skills to a real world scenario.

  12. Blueprint for Designing Digital Problem Solving Tasks

    Task design needs to be grounded in observations and pertinent data of learners engaged in actual problem solving in technology rich environments such as using

  13. How To Use Task Analysis in UX Design

    1. Define issues · 2. Conduct research · 3. Diagram tasks · 4. Add the narrative · 5. Review the data.

  14. Task Analysis by Problem Solving (TAPS): Uncovering Expert

    KEYWORDS: Task analysis, instructional design, training, assessment, training technology. 1. INTRODUCTION. When instructional designers or educational