The library consortium digital-services ART RTE publicly celebrates only on-time feature counts and never mentions quality escapes. Why is that recognition pattern ineffective?
Select an answer to reveal the explanation.
Short Explanation
Clapping only for on-time features is like cheering the library for opening on schedule while the catalog is full of broken links. People repeat what gets celebrated, so date-only applause quietly teaches the train to ship junk.
Full Explanation
Recognition trains behavior. Publicly celebrating only on-time feature counts while never mentioning quality escapes teaches a library consortium digital-services ART to hit dates while hiding defects that member libraries and patrons eventually feel. Effective recognition reinforces outcomes and built-in quality together, not ship-date theater alone. Claiming feature counts are the only ART metric SAFe permits is false; flow, quality, and outcome measures matter, and quality talk is not confined to team retrospectives. Saying quality escapes are Product Management's private issue so the RTE should stay silent misunderstands the RTE's coaching duty for ART health and Transparency. Celebrating ship dates first as required to protect the PI calendar even if defects pile up institutionalizes technical debt and erodes trust in digital services. Exam caveat: On-time delivery can be celebrated when quality gates were met; the anti-pattern is date praise that systematically ignores escapes. Operational check: In the next library ART celebration or System Demo close-out, pair delivered PI Objectives with escape or defect signals and call out teams that protected quality under schedule pressure.