Community | People

Journey Of Design - Define - Part 2

Feb 01, 2024 | Vidhi Siwal

Welcome to the second part of the blog series. This is the define stage. Define is the stage where all the information from the empathy stage is put into a proper template and is categorised into usable action points. Define is where the designer has to define various important aspects of the design thinking stage. One is the problem statement. Another is, the target audience, design brief, costing etc.



What is a problem statement?

Problem statements serve as focused descriptions of design challenges, providing a framework for design teams to understand, articulate, and ultimately solve complex issues. These concise statements, akin to points of view (POVs), guide teams in defining the current and desired states, offering a user-centric perspective. The philosophy echoed by Albert Einstein emphasizes the importance of spending a significant portion of the problem-solving process contemplating the issue itself. In design thinking, this principle is fundamental: dedicating ample time to thoroughly understand the problem ensures that subsequent solutions are well-informed and address the root causes. Problem statements become the navigational tools throughout a project, allowing teams to gauge the relevance of generated ideas against the established criteria, ensuring a user-focused and effective design process.


How does one write a problem statement?

Crafting effective problem statements is crucial for guiding design teams through the design thinking process, particularly during the Define stage. To uncover optimal solutions, it is imperative to articulate the problem accurately – hence the importance of a well-defined problem statement.

A successful problem statement serves as a beacon, illuminating the dimensions of the issue and inspiring a systematic quest for suitable solutions. By rallying around a shared problem statement, teams gain a unified perspective on users' challenges, knowing precisely what to explore and what to avoid. Here are key principles for constructing impactful problem statements:

  • Human-Centered Focus:

Problem statements should stem from insights about users and their needs, ensuring a human-centred approach that resonates with the intended audience.


  • Scope Balance:

Striking the right balance in scope is crucial – broad enough to foster creative freedom but narrow enough for practicality, enabling teams to explore a variety of solutions.

  • Action-Oriented Verbs:

Formulate problem statements with action-oriented verbs like "create" or "adapt," driving teams towards actionable and solution-oriented thinking.


  • Full Development and Assumption-Free:

Ensure problem statements are fully developed and free from assumptions, providing a clear and unbiased foundation for the design process.

Referred to as a "point of view" (POV), a well-crafted problem statement reflects the users' perspective, guarding against bias. This POV becomes the team's focused definition, directing their efforts toward the right challenge in subsequent stages. With a potent POV, teams can navigate the design process effectively, addressing the right problem in a manner aligned with user needs.

How to write a user persona 

Step 1: Unveiling Insights

  • Embark on a thrilling exploration of data gathered during the Discovery Phase, a treasure trove of user interviews and stakeholder perspectives.

  • Tag the gems within, focusing on user problems and aligning with the grand goals of the business.

  • In the absence of direct user research, venture into the realm of stakeholder insights and competitor analyses.

Step 2: Decoding Patterns

  • Enter the mysterious world of data analysis, seeking patterns and secret connections.

  • Embrace the understanding that diverse user groups might hold unique keys to unlocking design mysteries.

  • Talebook's tale reveals UI Designers craving step-by-step guides, while seasoned UX Designers grapple with the enigma of stakeholder reporting.

Step 3: Persona Alchemy 

  • Witness the magic unfold as components come to life:

    1. Photo: Each persona gets a visual identity, an image that resonates.

    2. Name: Bestow is a name, a symbol of rational identification.

    3. Description: Weave a narrative summarizing background, motivations, goals, and the heroic journey through challenges.

    4. Problems: Illuminate the specific problems each persona battles, adding depth to their character.

Step 4: Share the Epic

  • The saga of personas finds its climax in sharing and distribution.

  • Make sure every team member is a protagonist in this narrative, intimately acquainted with the primary personas.

  • Utilize the magical Talebook link to transport everyone into the world of personas, fostering discussions and uncovering design secrets during every conversation about the app or service. The adventure awaits!

Onto the next chapter

As we step into the enchanting realm of Ideation, the design thinking adventure takes a creative turn. Picture this: What if every defined problem and empathetic insight were seeds waiting to burst into a garden of innovative solutions?

In Part 3 of our design thinking saga, we'll plunge into the brainstorming battlefield, where ideas clash, combine, and evolve into something extraordinary. Get ready to witness the magic unfold in "Ideation Alchemy." It's not just about generating ideas; it's about transforming them into design gold.

The plot thickens, and the possibilities are boundless. Will we uncover the elixir of creativity? What groundbreaking concepts will emerge from the crucible of ideation? Join us in the next blog as we embark on a journey through uncharted territories where ideas take flight, and design brilliance knows no bounds. The adventure continues; don't miss the next chapter in the saga of design thinking's Ideation Odyssey!




I Understand

By continuing to use this site you consent to the use of cookies.

Know More.
X