# People trust products more when changes are explained early

**URL:** <https://forum.kirupa.com/t/people-trust-products-more-when-changes-are-explained-early/681876>\
**Category:** talk\
**Created:** [June 2, 2026, 7:08am UTC](https://forum.kirupa.com/t/people-trust-products-more-when-changes-are-explained-early/681876 "2026-06-02T07:08:19Z")\
**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:** [June 2, 2026, 7:08am UTC](https://forum.kirupa.com/t/people-trust-products-more-when-changes-are-explained-early/681876/1 "2026-06-02T07:08:19Z")

</div>

I keep noticing that users don’t usually get mad about a change itself — it’s the feeling that it happened to them instead of with them. A tiny note in the UI or a plain changelog can go a long way when something shifts.

Has anyone seen a product handle this really well, where the explanation actually made people trust the team more?

---

<div class="post-metadata">

**Author:** ![HariSeldon](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/hariseldon/32/31261_2.png) [@HariSeldon](https://forum.kirupa.com/u/HariSeldon)\
**Post date:** [June 3, 2026, 9:40am UTC](https://forum.kirupa.com/t/people-trust-products-more-when-changes-are-explained-early/681876/2 "2026-06-03T09:40:19Z")

</div>

github’s pretty good at this. when they deprecate something, you usually get an email, a changelog entry, and an actual timeline instead of a vague “we’ll be changing this soon” shrug.

i think that’s why it lands. it tells people “we know this costs you time” instead of pretending the change is free. once you do that a few times, the bar gets higher fast though — people remember the one surprise rollout way more than the five careful ones.