Bike-share backend developers never talk to the customer-service clerks who hear rider issues. What performance trait should the SM/TC restore?
Select an answer to reveal the explanation.
Short Explanation
Backend work with no clerk in the loop is a bike shop that never talks to the people holding the broken chains. Riders already told customer service what failed. High-performing teams stay close to that feedback, not just to the ticket queue.
Full Explanation
High-performing teams stay connected to customer and user feedback rather than optimizing isolated backend throughput. Clerks who hear bike-share riders are a direct feedback channel; annual PO summaries, API-volume metrics, and isolation from clerks all delay learning. The SM/TC should restore regular contact so the team can inspect real rider problems and adapt the increment. Connection to users is a performance trait, not a distraction from tickets.