3 ms·

I think correcting in private makes sense if also paired with a no-blame oriented retro after the fact for everyone to know what happened and to brainstorm abou

• mulmen 3y ago
  How can a correction be private and blameless? In a 1:1 if you talk about what “we” did wrong you’re clearly talking about me.
  • ineptech 3y ago
    Those are two separate discussions. Even if I do something dumb and am rightly blamed for it, we can still have a retro to discuss process improvements that would make it harder for that mistake to happen again in the future.
    • jjice 3y ago
      This is what I had in mind, thank you for putting it into better words that I could. Taking responsibility for messing up is important and part of personal growth. Having the team be aware of an issue and then together develop a way to avoid that issue in the future is huge. I had a boss who told me that when something like this happened, it was usually an issue with a system in place. Merged bad code that shouldn't have gone to production? We need to improve review processes and testing. Production server outage after system dependencies changed? We need a more accurate staging environment and testing process for our infra. That mindset was so great to learn and I fully embrace it still.
      • mulmen 3y ago
        Teams should introspect at a group level. That’s not controversial or relevant. Unsolicited individual feedback has the potential to cause harm and an outside observer (you) can’t know the situation. So the safe and respectful move is to simply ask first. It costs nothing, your feedback is heard, and no harm is done.