From Chaos to Clarity: My Framework for Untangling Complex UX Problems

How I use affinity mapping to turn messy requirements and scattered research into organized, actionable design strategy.

Every UX project starts with chaos: too many ideas, too many opinions, too many “must-have” features. Over time, I’ve learned that clarity isn’t about shrinking the problem, it’s about structuring it.

In this article, I’ll share two frameworks I rely on to bring order to complex UX challenges:

1. Creating and organizing product requirements
2. Turning discovery research into key insights

Both hinge on the same principle: affinity mapping as the connective tissue between research and design.

1. Finding structure in the mess — turning requirements into a content strategy

The project began with a massive challenge: overhauling the account pages for a major travel brand.

The team handed me a jumble of requirements and each artifact spoke a different language. My first goal was to create one shared map.

Each requirement contained layers of sub-features and dependencies, creating up to four levels of potential architecture. It was far too much to be able to represent immediately in a wireframe.

I started by pulling every piece of information I could find: the client’s wish list, stakeholder interview findings, the existing native app and responsive website features, and competitor examples. Once everything was visible, I drafted an IA hypothesis, a best-guess structure informed by what I knew about the current and future state.

First IA hypothesis, including bare bones content hierarchy

Then I visualized it in FigJam. Every requirement became a sticky note. Seeing them all together revealed patterns, redundancies, and potential gaps. As groupings emerged, I refined the IA and revisited my notes to validate decisions.

Requirements arranged in line with the IA hypothesis

Once the IA felt cohesive, I ran a tree-test to validate the structure with users. The results helped fine-tune labels and structure. From there, I translated the mapped requirements into a low-fidelity content strategy — one wireframe per page with bullet-pointed content needs organized into hierarchical sections.

Content strategy representing basic component & requirement hierarchy

That artifact became a bridge between strategy and design: the first time everyone could see the product before wireframes even existed.

With the requirements organized, I turned to another challenge, making sense of our mountain of research.

2. Turning research into insight — how affinity mapping drives discovery

In the discovery phase of another large redesign, I faced a different kind of chaos: an ocean of research data. Stakeholder and user interviews, landscape analyses, SEO findings, survey results, analytics data — all valuable, none cohesive.

I’d recently read Practical Design Discovery by Dan Brown, which inspired me to build a discovery framework that mirrored his linear approach. I created a FigJam board divided by research activity, stakeholder interviews, landscape analysis, and so on, and represented every finding as a sticky note.

Figjam workshop board with research findings in sticky notes

When all the inputs were gathered, I brought the team together for an affinity-mapping workshop. The wider the mix, the better: UX and UI designers, content strategists, engineers, and product managers all contributed.

We set a 15-minute timer, put on some music, and everyone began grouping stickies individually, creating names for each cluster. Afterward, we reviewed the results together, refining names and hierarchies, and discussing what emerged as key insights.

120+ research findings clustered into 3 themes under a 15-minute timer.

“Affinity mapping works because it gives everyone oversight and ownership over the discovery direction.”

When the chaos settled, three clear opportunity areas stood out. Those clusters became the outline of our discovery presentation, and because every insight traced back to a specific sticky, we could instantly show the evidence behind each recommendation.

3. Why affinity mapping works

Affinity mapping externalizes complexity: it turns hidden connections into visible systems.

• It builds consensus because everyone sees the same landscape.
• It bridges qualitative and quantitative data.
• It’s flexible: it works for requirements, insights, or even early visioning.

Over time I’ve realized that “clarity” isn’t something you stumble upon at the end of a project. Clarity is something you design from the beginning, by giving chaos a structure and letting patterns emerge naturally.

Key takeaways

My rules for designing clarity:

• Start broad, then group until patterns emerge.
• Label everything, clarity begins with naming.
• Involve the team early, shared ownership builds alignment.
• Retain the threads, connect every insight back to its evidence.

Closing thoughts

Whether you’re mapping product requirements or wrangling research data, the principle is the same: make it visible, make it collaborative, and let structure guide you to insight.

Every messy list hides a logical system, you just have to draw it out.

Have you used affinity‐mapping in a different context? I’d love to hear what worked (or didn’t) in the comments below.