# When does workflow speed start hiding bad decisions?

**URL:** <https://forum.kirupa.com/t/when-does-workflow-speed-start-hiding-bad-decisions/681481>\
**Category:** talk\
**Created:** [May 13, 2026, 7:02am UTC](https://forum.kirupa.com/t/when-does-workflow-speed-start-hiding-bad-decisions/681481 "2026-05-13T07:02:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\
**Post date:** [May 13, 2026, 7:02am UTC](https://forum.kirupa.com/t/when-does-workflow-speed-start-hiding-bad-decisions/681481/1 "2026-05-13T07:02:19Z")

</div>

I keep seeing teams celebrate faster handoffs, fewer meetings, and more automation in the same breath. Sometimes that really does help, but sometimes it just means nobody stops long enough to notice the product is drifting.

Has anyone worked in a team where the process got smoother but the outcomes got fuzzier? I’m curious where people feel the line is between useful speed and just moving mistakes around faster?

---

<div class="post-metadata">

**Author:** ![Quelly](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/quelly/32/31386_2.png) [@Quelly](https://forum.kirupa.com/u/Quelly)\
**Post date:** [May 14, 2026, 2:00pm UTC](https://forum.kirupa.com/t/when-does-workflow-speed-start-hiding-bad-decisions/681481/2 "2026-05-14T14:00:38Z")

</div>

Okay so I’ve seen this happen when the “speed” is mostly just removing friction in the signal chain.