Introduction

Designers frequently confront problems that seem impossibly vague. When a stakeholder declares we need something like this, urgently, the actual challenge often lies hidden beneath layers of assumption, unfamiliar territory, and unclear user needs. Developing the habit of investigating before designing can determine whether you build a solution that truly resolves the core issue or merely add to the noise.

What Happened

Valeriia Vyrva began her tenure at YCLIENTS, a B2B platform for beauty salons that had expanded primarily through engineering efforts. The product had evolved into a tangled web of ambiguity—complex user flows, an unfamiliar business domain, and tasks where boundaries were blurred. After deciding to end her probation period after roughly a month, she recognized the urgency of building competence in handling uncertainty. In the ensuing six years, she cultivated a structured approach inspired by investigative work to transform vague directives into clear, actionable design problems.

Why This Matters

Job postings frequently mention comfortable with ambiguity or strong problem-framing skills, yet designers routinely receive vague briefs with tight deadlines. Without a deliberate framework, teams risk developing features that overlook genuine user needs, consume resources, or fail to achieve adoption. A structured investigation approach converts ambiguity from a dead end into a resolvable case.

Key Takeaways

  • Before sketching any solution, map the problem's origins, identify the users involved, and distinguish between what the team truly knows and what rests on assumption. A simple fact-vs-assumption separation can instantly cut the mystery in half.
  • Every organizational shift stems from a underlying driver—revenue growth, reduced churn, market expansion, or a competitive response. Pinpointing this motive clarifies whether you're addressing the real problem or implementing someone else's proposed fix.
  • Employ the 5 Whys technique to probe beyond the initial problem statement. Repeatedly asking why often uncovers the root cause rather than surface symptoms, revealing the actual problem to solve.
  • Establish success criteria with the team before development begins. Whether the goal is improved conversion, reduced support volume, a successful usability test, or a strategic pivot, having clear evidence of victory prevents wasted effort on features whose impact remains unproven.

Conclusion

The Poirot approach isnt a magical superpower—its a disciplined practice of gathering facts, tracing connections, and breaking a massive unclear problem into smaller, manageable pieces. When faced with a vague brief and an imminent deadline, resist the impulse to jump straight into design. Instead, turn to your analytical mindset, begin questioning, and recall: the most effective designer isnt necessarily the one who finds an answer quickest, but the one who persists in asking the right questions longest.