Skip to main content

How to create problem statements in UX discovery

About Us
Published by jetbi
03 January 2023
55

When it comes to designing products or services that meet the needs of users, the user-centered design (UCD) process is a popular framework for ensuring that the design team is solving the right problems. One of the key components of the UCD process is the creation of problem statements. Problem statements are concise, actionable statements that define the challenges or obstacles that users face and that the design team needs to solve. In this article, we will explore the importance of problem statements in UX discovery and how they can help design teams create successful products and services.

 

Why Are Problem Statements Important in UX Discovery?

  1. Focus on the User:

Problem statements help design teams stay focused on the user and their needs throughout the design process. By identifying the specific challenges that users face, designers can prioritize solutions that will have the greatest impact.

  1. Clear and Actionable:

Problem statements provide clear and actionable guidance for the design team. They help to define the scope of the design challenge and provide a framework for making decisions about design solutions.

  1. Align Stakeholders:

Problem statements help to align stakeholders around the goals of the project. By clearly articulating the challenges that need to be addressed, problem statements can help to create consensus among stakeholders and ensure that the design team is focused on the right issues.

 

How to Develop Effective Problem Statements:

  1. Conduct User Research:

The first step in developing effective problem statements is to conduct user research. This can include interviews, surveys, and other methods to understand the needs and pain points of the target user group. 

  1. Synthesize Findings:

Once user research is complete, the design team can synthesize the findings to identify the most critical challenges and obstacles that users face.

  1. Write Concise Statements:

The problem statements should be concise, focusing on the most significant challenges that users face. They should also be actionable, defining the specific issues that the design team needs to solve.

 

In conclusion, problem statements are a critical component of the UCD process in UX discovery. They provide a framework for designing solutions that meet the needs of users and ensure that the design team is focused on the most significant challenges. By conducting user research, synthesizing findings, and developing clear, concise problem statements, designers can create successful products and services that meet the needs of their target users.


Kirill Sedelnik
UI/UX Designer
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026