# Designing for Consequences. Not Just Screens (Glaringly Obvious)

**URL:** <https://forum.zurb.com/t/designing-for-consequences-not-just-screens-glaringly-obvious/102>\
**Category:** Community\
**Created:** [July 18, 2025, 12:23am UTC](https://forum.zurb.com/t/designing-for-consequences-not-just-screens-glaringly-obvious/102 "2025-07-18T00:23:42Z")\
**Posts on this page:** 2\
**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:** [July 18, 2025, 12:23am UTC](https://forum.zurb.com/t/designing-for-consequences-not-just-screens-glaringly-obvious/102/1 "2025-07-18T00:23:42Z")

</div>

I dropped a clip from my conversation with [Martin Tomitsch](https://www.linkedin.com/in/martintomitsch/), who co-wrote _[The UX Butterfly Effect](https://uxdesign.cc/the-ux-butterfly-effect-58dd180a0e13)_ with [Steve Baty](https://www.linkedin.com/in/stevebaty/), a sharp reminder that design decisions don’t happen in a vacuum.

> **[Glaringly Obvious with Martin Tomistch & Steve Baty](https://glare.helio.app/interviews/martin-tomistch-steve-baty#design-isn-t-neutral-systems-mapping-shows-you-why)**
>
> Podcast Interview: Design isn’t neutral. Systems mapping shows you why.

In the episode, they breakdown how even small UX changes can ripple outward in ways teams rarely plan for… impacting mental health, energy usage, and even supply chains. Their approach pushes us to go beyond the user journey and into the systems that shape behavior, business, and the planet.

* * *

### Why This Matters

In our conversation, they talk about how tools like systems maps ripple canvases visuals help designers:

- Spot unintended consequences early
- Understand how product decisions affect society and infrastructure
- Move from interface thinking to systems awareness
- Balance desirability and effort with real-world impact

 ![systems-mapping](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/da4bdbf0cc3d88313e150265ba301f3baff1c1da.jpeg)

* * *

💬 **Discussion**

- Where have you seen small UX decisions lead to big impacts, positive or negative?
- How do you help your team zoom out from the interface to see the full system?

Would love to hear your thoughts.

---

<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:** [July 19, 2025, 6:06pm UTC](https://forum.zurb.com/t/designing-for-consequences-not-just-screens-glaringly-obvious/102/2 "2025-07-19T18:06:25Z")

</div>

I shared the interview and some additional thoughts on how I believe systems thinking and mapping can benefit design and product leaders.

> **[Systems thinking is more important than ever. | Bryan Zmijewski](https://www.linkedin.com/posts/bryanzmijewski_productdesign-uxmetrics-productdiscovery-activity-7352389726470852608-t7ND)**
>
> Systems thinking is more important than ever.
> 
> I believe that as AI tools speed up how we build and ship products, it's critical to bring more structure to our design decisions, especially when they affect other parts of the product or user...

Obviously, Glare is an important part of thinking about how decisions can affect users more holistically when testing with an audience. The more teams test around an idea, they begin to see the bigger impact those decisions have on the entire system.

 ![systems-thinking](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/849e2d6d35351934964d8b3d6583ed35c281b7ca.png)