# Communicating Out: Design Signals and Case Studies

**URL:** <https://forum.zurb.com/t/communicating-out-design-signals-and-case-studies/416>\
**Category:** Storytelling\
**Created:** [December 2, 2025, 9:18pm UTC](https://forum.zurb.com/t/communicating-out-design-signals-and-case-studies/416 "2025-12-02T21:18:01Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [December 8, 2025, 12:32am UTC](https://forum.zurb.com/t/communicating-out-design-signals-and-case-studies/416/3 "2025-12-08T00:32:48Z")

</div>

Yes! Defining a design signal moves the work beyond pure data and into the space where a designer’s judgment actually adds value (instead of a confusing mess).

It gives people a simple way to follow how you interpret what you saw. It turns your synthesis into something others can understand and use from a design perspective

It’s something you can repeat, but it’s not rigid. (Many designers struggle with creating repeatable pieces that add value in business communication).

@Helge shared a nice [viewpoint on a design signal](https://forum.zurb.com/t/which-constraints-drive-product-more-users-or-businesses/413/7).

---

_[View the full topic](https://forum.zurb.com/t/communicating-out-design-signals-and-case-studies/416)._