Recommendations 2-4 aren’t great. Instead, I’d recommend really working on recommendation #1 which is working on communication specifically… 1. Tighten the fe

Recommendations 2-4 aren’t great. Instead, I’d recommend really working on recommendation #1 which is working on communication specifically… 1. Tighten the feedback loop for them. We all get the idea of using logs for engineering. People need the same for their performance. This means being willing to have difficult conversations and providing accountability. 2. Discuss in an open forum ways in which to solve the underlying problem and get commitment from the team as a whole to try new things like mob sessions or pair programming. 3. Most importantly, there has to be clear goal-setting. Meaning the team should be a part of that process to decide what they are attempting to accomplish and what their scope will be. This can be helpful for making sure no one is too far afield. ONLY ONCE THE TEAM HAS DONE THE THINGS ABOVE And if the engineers choose to not engage in good faith and work in the interest team would I consider termination or moving them to another team.