Celebrating the moment a draft lands in the shared folder creates a hidden incentive to ship half‑baked work. When the applause arrives at the first version, the signal to the creator is “speed wins,” while the rest of the group learns that polishing is optional. The result is a cascade: reviewers spend more time fixing gaps, downstream engineers inherit vague requirements, and product managers scramble to fill missing details. In one product group, a senior designer finished a concept overnight, posted it, and received a “great start” note from leadership. The next week the team spent a full sprint untangling ambiguous user flows that the draft never clarified, delaying the release and inflating the bug count. The underlying dynamic is simple: early‑stage praise raises the perceived value of speed relative to completeness, so the cost of rework silently grows.

To break the loop, replace the “first draft” trophy with a “finished iteration” check. When a piece reaches a state where every downstream owner can act without clarification, that moment earns the public nod. The shift flips the reward curve, making thoroughness a visible currency and encouraging creators to invest the extra effort before seeking applause. Over time, the team’s rhythm steadies, handoffs smooth, and the overall velocity rises because work arrives ready to be built, not to be rebuilt.