# Use Impact Mapping to separate noise from signals (Glaringly Obvious)

**URL:** <https://forum.zurb.com/t/use-impact-mapping-to-separate-noise-from-signals-glaringly-obvious/188>\
**Category:** Open topics\
**Created:** [August 15, 2025, 2:56pm UTC](https://forum.zurb.com/t/use-impact-mapping-to-separate-noise-from-signals-glaringly-obvious/188 "2025-08-15T14:56:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\
**Post date:** [August 15, 2025, 2:56pm UTC](https://forum.zurb.com/t/use-impact-mapping-to-separate-noise-from-signals-glaringly-obvious/188/1 "2025-08-15T14:56:17Z")

</div>

I sat down with **Büşra Coşkuner** to talk about _impact mapping_, a way to make sure the work you choose is actually worth doing. It’s not about ranking your priorities; it’s about finding the right ideas to explore in the first place.

> **[Glaringly Obvious with Büşra Coşkuner](https://glare.helio.app/interviews/busra-coskuner#b-ra-bryan-on-decision-making-and-outcome-metrics)**
>
> Podcast Interview: Impact mapping helps you focus on the right work

Büşra uses impact mapping to connect business goals with user behavior and the things we plan to build. This way, teams can:

- Check roadmaps and backlogs against real goals
- Choose features that support the outcomes in their OKRs
- Start with user outcomes that create business value
- Solve problems for specific types of users

I like how she’s made the approach more actionable: clearer terms, room for experiments, and thinking strategically _before_ you start building.

As she put it:

> “It’s to align the levels with product jargon. I don’t use ‘Impact’ at the goal level anymore because it shifts the focus from actor behavior to business goals.”

 ![impact-mapping](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/7a10beb50686042383da6b151d86775b1e642933.png)

What stood out most? Impact mapping gives teams a shared way to talk about priorities early—before time and resources get locked into the wrong things.

We use UX metrics to quickly test which ideas actually move the needle for users. This way, you know when quick feedback is enough, and when it’s worth going deeper.

💬 **Discussion:**  
When you’re mapping out your next quarter, how do you decide what makes it onto the roadmap?