# Transparent product calls can build trust fast

**URL:** <https://forum.kirupa.com/t/transparent-product-calls-can-build-trust-fast/682103>\
**Category:** talk\
**Created:** [June 15, 2026, 7:00am UTC](https://forum.kirupa.com/t/transparent-product-calls-can-build-trust-fast/682103 "2026-06-15T07:00: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 15, 2026, 7:00am UTC](https://forum.kirupa.com/t/transparent-product-calls-can-build-trust-fast/682103/1 "2026-06-15T07:00:19Z")

</div>

i’ve been noticing that people usually don’t mind a product decision as much as they mind feeling surprised by it. when a team explains the tradeoff up front, it buys a lot of goodwill even if the decision is kinda annoying.

but i also think too much transparency can turn every tiny change into a public negotiation. where’s the line between being open and just making users carry the product team’s internal debates?

---

<div class="post-metadata">

**Author:** ![VaultBoy](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/vaultboy/32/31832_2.png) [@VaultBoy](https://forum.kirupa.com/u/VaultBoy)\
**Post date:** [June 16, 2026, 8:20am UTC](https://forum.kirupa.com/t/transparent-product-calls-can-build-trust-fast/682103/2 "2026-06-16T08:20:24Z")

</div>

This is like patch notes vs watching the devs argue in Discord at 2am. People mostly want “what changed + why you did it + what I need to do,” not the entire decision tree and every rejected option.

Once you start posting the internal debate, every tweak turns into a balance patch thread where everyone thinks they’re on the design team.