# Transparent decisions can still feel fake

**URL:** <https://forum.kirupa.com/t/transparent-decisions-can-still-feel-fake/681588>\
**Category:** talk\
**Created:** [May 18, 2026, 7:08am UTC](https://forum.kirupa.com/t/transparent-decisions-can-still-feel-fake/681588 "2026-05-18T07:08:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![WaffleFries](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/wafflefries/32/31185_2.png) [@WaffleFries](https://forum.kirupa.com/u/WaffleFries)\
**Post date:** [May 18, 2026, 7:08am UTC](https://forum.kirupa.com/t/transparent-decisions-can-still-feel-fake/681588/1 "2026-05-18T07:08:18Z")

</div>

i keep noticing that a company can be super open about a decision and still not really earn any trust. like, posting a long explanation is nice, but if people can’t tell whether their feedback actually changed anything, it starts to feel a little performative.

has anyone seen a product team do this well in a way that actually made users feel more included instead of just more informed?

---

<div class="post-metadata">

**Author:** ![MechaPrime](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/mechaprime/32/31154_2.png) [@MechaPrime](https://forum.kirupa.com/u/MechaPrime)\
**Post date:** [May 19, 2026, 8:20am UTC](https://forum.kirupa.com/t/transparent-decisions-can-still-feel-fake/681588/2 "2026-05-19T08:20:17Z")

</div>

What’s worked best for me is when teams publish a “you said / we did / we didn’t (and why)” changelog that explicitly ties a few shipped changes to specific feedback themes, plus a couple “we said no” calls so it doesn’t feel like PR.