April 8, 2025

Understanding Design Tasks

We are JetStyle: a full-scale digital studio with 9+ years of expertise in design. We have 50+ inhouse designers with various backgrounds: from motion and graphic design to UX/UI, VR, font, industrial, and web design. 

At JetStyle, we create interaction design, because we believe human interaction is the core of any digital product. We believe design is not a tool for self-expression, but rather an art of engineering. When we assess the quality of design, we ask one main question: does this design solve the communication task? 

In this long read, we share our vision on how designers at JetStyle understand design tasks and process clients’ briefs. The way designers understand the brief impacts how the interface will work. To truly grasp a design task, a designer should follow five key steps. Let’s break down each one: 

How Designers Understand Clients’ Briefs 

A designer should be able to identify:

  • The business goal

  • Changes in customer behavior patterns

  • The desired event on the website

  • Customers’ barriers and problems

  • The solution to the problems

In simple terms, every time we design something, our goal is to remove existing barriers and issues with visual tools. As a result, the right event should occur on the website. This event indicates that the user's behavior has shifted in the desired direction, and our client has achieved the business goal. If we lose track of the business goal at any point, something has gone wrong.

Now, let’s dive into each step in more detail.

  1. The business goal should specify the task. We recommend not using “increased profit” as the goal: this is a general objective in 95% of cases. Instead, focus on something more specific, like increasing upsell or improving LTV (Customer Lifetime Value).

  2. A designer must be able to describe how a person currently behaves and how they should behave when they encounter the new interface. The key is the difference between the old and new behaviors. For example, right now, a person enters the kitchen, sits down at the table, and doesn’t eat their oats, but the goal is for them to start eating them.

  3. To evaluate whether the interface solves user problems, you need to know which event on the website will indicate that the problem is solved.

  4. Problems and barriers are best described via a user story: “When I’m in a certain role and do something, I want X. Here’s what’s preventing me from getting it.”

  5. Solutions to problems are the decisions the designer will make for the interface. Should this banner be bigger? Where should the "Buy" button go? Should the user options be presented as a grid or a list? But before making these decisions, you need to go through the previous four steps.

We recommend working through all five steps, and you’ll be surprised at how much clearer the task becomes and how much easier it is to solve.

If you need skilled designers, just describe your task to us at orders@jet.style.

FAQ
What should a “good” design brief include to get predictable results from an agency?
A strong brief ties design to outcomes: a specific business goal (not just “increase profit”), the current user behavior vs. the desired behavior, the key website event that proves success, the user’s barriers, and what needs to change in the experience to remove them.
How do design teams translate business goals into interface decisions?
By linking every UI decision to a communication task: remove barriers with visual and interaction tools so the right event happens on the website. If the design loses the business goal at any stage, the interface may look fine but won’t move metrics.
What metrics or goals are best suited for design work in B2B projects?
Goals that describe a concrete business task: increasing upsell, improving LTV, raising conversion at a specific funnel step, or improving lead quality. These are clearer than generic “growth” and help teams define what exactly should change in user behavior.
How do agencies identify user problems before proposing UI solutions?
They describe problems as barriers in context, often via a user story: “When I’m in a certain role and try to do X, I want Y, but something prevents me.” Only after the role, intent, and barrier are clear does it make sense to decide layout, hierarchy, CTA placement, or navigation patterns.
How can a business tell whether a redesign actually worked?
By defining the “desired event” upfront: the on-site action that signals the barrier is removed and behavior changed (e.g., completing a purchase, submitting a qualified request, using an upsell flow). That event becomes the shared definition of success for both the business and the design team.
Hello!
Hello JetStyle,
I would like to discuss a project idea with you.
My name is
you can email me at
or reach me on
Book a call
or let's chat
By clicking the submit button you agree to our Privacy Statement
Sent!
We’ll get back to you soon
Oops! Something went wrong while submitting the form.
Let’s talk