Welcome!
Hi this is John with this week’s Developing Skills - Skills for Developers looking to develop their careers.
If there is a topic you’d like to see covered, please let me know by replying to this email📧
Tip of The Week: Learn To Correct People Without Offending Them
As I returned from the kitchen with a fresh cup of coffee Simon ran out of the office in tears. What was that about? I looked at his fellow junior engineers questioningly, wondering what had happened. They looked embarrassed and uncomfortable then away.
As I put my coffee down, I noticed a private message flash up on my laptop from one of the senior engineers: “Hey John, poor Simon has just been torn apart by Bob. Sure Simon was wrong - hey, he’s a junior it’s gonna happen - but Bob was pretty harsh every time he corrected him.”
When I went outside and spoke to Simon he confirmed it, Bob has been correcting him all day and it was undermining his confidence. He wanted to quit his job right then.
Like Bob, it’s inevitable that at some point in our career we will have to correct someone. It’s an unavoidable part of being in a healthy, growing team. After all, we can’t all know everything, so we should be able to correct each other and lift each other up.
When it’s done well, correcting someone can change their behaviour, helping them achieve better results and strengthen your relationship with them. Yet too often we do it badly, damaging the relationship and causing resentment. Like Bob did.
Here are four steps you can take to avoid that.
1. Be like Elsa from Disney’s Frozen and “let it go” - a lot of the time it really doesn’t matter if someone is wrong. So before you rush to correct them, take a moment and ask yourself - does it really matter if they are wrong? Is there anything important at stake here if you don’t correct them? If not, let it go.
2. If you really do need to correct them, correct them in private - it’s human nature to be embarrassed when we’re wrong. We’re even more embarrassed if we’re wrong in public. So, to limit that embarrassment correct people in private. If you really need to correct in public take care to minimise the impact. For example if someone is presenting a plan that you believe is flawed, don’t pick it apart publicly, instead slow things down and offer to help. For example:
Thank you for the work you’ve done on this proposal. There are a few suggestions I’d like to make, perhaps we can get together after this meeting and work on it together?
You’ve stopped the current issue and can later in private constructively correct them and help refine the proposal.
3. When you are correcting someone, focus on the behaviour or outcome, not the person - when you focus on the person, it becomes personal and intended or will feel like a personal attack. That is going to make the other person defensive, damage your relationship and lead to a negative outcome.
Instead focus on the observable behaviour or outcome and not on them. For example:
I noticed some errors in the proposal, I would like to see them addressed before we review it with the team again.
Be sure to then provide specific examples of the issues that need to be corrected.
4. None of us like being corrected, we’re embarrassed by our mistakes so when you have to correct someone, soften the blow - don’t just knock them down and then keep kicking them, instead praise what you can. Offer some positive feedback and support.
You can do this well by beginning with a positive statement about their work or behaviour and some praise for their achievement so far. Then provide the correction and follow it up with a reminder of the praise and wrap up on a positive, supportive note.
For example:
Thank you for taking on this difficult challenge, I really appreciate you stepping up and volunteering to work in the proposal. Especially as I know you’d rather be writing code than documents. I really appreciate the teamwork.
I noticed some errors in the proposal, I would like to see them addressed before we review it with the team again. List specific examples...
This was a difficult task, so I really appreciate you taking it on and getting us to where we are today. Thank you for stepping up. Please let me know if I can help with the revisions in any way.
Unfortunately, this was very early in my career, when I wasn’t experienced enough to give Bob this advice. Instead we had a frank discussion in private, but without me having the experience to cushion the blow and stick firmly to talking only about the behaviour.
Sadly that meant Bob felt wronged too.
Therefore his behaviour didn’t change and a few weeks later he was fired. The working environment improved for those that remained, but it was a net loss for all of us. Bob lost his job, we lost his expertise.
So please don’t be like Bob or I were, learn from our mistake.
FINAL CALL! Would You Like To Build a Personal Brand on LinkedIn?
Starting on the 22nd July I’m running a course and 30 day challenge where I show you how I:
✅ Grew my LinkedIn following from 3,000 to 130,000+ in just 12 months.
✅ Became the No. 1 ranked ‘IT & Tech’ influencer on LinkedIn in the UK and 34th worldwide.
✅ Generated over 40 Million post impressions on LinkedIn.
✅ Grew my newsletter to over 100,000 subscribers on LinkedIn and over 50,000 on Substack.
And how you can too. You can learn more and sign up here: https://johncrickett.gumroad.com/l/30day-li-challenge/
I’ve been really enjoying your posts on soft-skills. Very helpful!
Interesting article John! I 100% agree with the importance of focusing criticism on the behavior NOT the person. In the real world, you are working in a team and not as a long wolf, so using the word "we" more often than "you/I" helps you come off as easier to work with.
One area of improvement in the example from the article could revolve around the wording: "I noticed some errors in the proposal, I would like to see them addressed before we review it with the team again. List specific examples..."
If I were in the shoes of that communicator, I personally think that you can still be direct and encouraging. Instead of saying "errors in the proposal", I'd phrase it as "suggestions/areas of improvement" that way the recipient focuses on the "improvement" aspect rather than "you have 20 errors in your proposal"
Just my 2 cents