How to get better at providing candid feedback
In a recent Performance Review, I was asked to get better at "saying no" and at "providing candid feedback".
To learn more about candid feedback, I was recommended to read the book Radical Candor by Kim Scott.
In this article, I share some key insights from the book that may be of value to you too and perhaps even inspire you to read the book as well.
Trust me, these ideas are like adding a secret ingredient to your code – they’ll make your teams stronger, your feedback more effective, and your workdays even more joyful!
So let's get started!
Let's Get Radically Candid, Joyfully!
Now, the name Radical Candor might sound a bit like a superhero power (and in a way, it is!), but it's actually a wonderfully simple concept: being truly kind and wonderfully clear with each other.
Kim Scott emphasises that being a stellar engineering teammate and leader boils down to two super important things: genuinely caring about the people you work with and being willing to give them direct feedback.
Think of it as being a supportive friend who also isn't afraid to tell you gently if you've got a bit of spinach in your teeth – all because they care!
In our engineering universe, this means we can build truly awesome things together when we're not just technically brilliant, but also masters of clear and caring communication.
Imagine our Angular projects as intricate Lego castles we're building as a team.
If one of our blocks is a little wobbly, a radically candid approach means a teammate might cheerfully say:
"Hey! This part looks great, but I noticed it might be a tad unstable under [specific scenario]. Maybe we could try [alternative approach]? Just thinking out loud!"
See? Kind, specific, and aiming for a stronger castle!
Here are a few ways we can joyfully weave Radical Candor into our engineering lives:
✅ Code Reviews that Spark Growth
Instead of vague feedback like "Needs improvement," Radical Candor encourages us to be specific and explain why something could be better, always with a tone of helpfulness.
For example, instead of just saying:
"This function is too long"
you could say with a smile:
"Hey! This function is doing a lot. To make it easier to read and test in the future, maybe we could break it down into a couple of smaller, focused functions? Just a thought!"
This shows you care about code quality and your teammate's development.
✅ Design Discussions with Zest
When we're brainstorming solutions or debating architectural choices in our Angular apps, Radical Candor isn't about winning arguments.
It's about caring enough to challenge ideas directly while showing you value your colleagues' perspectives.
If someone proposes a very complex solution, you might enthusiastically say:
"That's a really interesting approach! I'm wondering if we could explore a slightly simpler option first, maybe to get a quicker win or to make it easier for everyone to grasp initially? What do you think?"
It's about collaboration, not confrontation!
✅ Receiving Feedback with Grace (and Maybe a Chuckle)
Radical Candor isn't just about giving feedback; it's also about being open to receiving it!
When a teammate offers you candid feedback, try to hear the care behind it.
Even if it stings a little at first (it happens to the best of us!), remember they're trying to help you grow.
A good response might be:
"Thanks so much for pointing that out! I can see what you mean now. I really appreciate you taking the time to help me improve!"
Now, let's briefly peek at the less joyful zones Kim Scott talks about:
❌ Ruinous Empathy
This is when we care so much about someone's feelings that we avoid giving them honest feedback, even when it could really help them.
It's like saying:
"Your code is perfect!"
even if it has a few bugs, just to be nice.
But in the long run, it doesn't help anyone.
❌ Obnoxious Aggression
This is challenging directly without showing any care.
Think of a code review that's just a list of harsh criticisms with no explanation or empathy. Ouch!
It might get the point across, but it can damage relationships and morale.
🍍The sweet spot
The sweet spot, the place where we build amazing things and thrive as engineers, is right in the heart of Radical Candor – where kindness and clarity dance together in perfect harmony! 💃 🕺
Summary
Embracing the principles of Radical Candor is like unlocking a superpower for our teams!
By being genuinely caring and wonderfully clear in our communication, we can create an environment where everyone feels supported, valued, and empowered to grow.
Let's aim to give and receive feedback with kindness and clarity, fostering a culture of continuous improvement and joyful collaboration in our Angular and broader engineering endeavours.
Keep coding, keep communicating, and keep shining brightly! ✨
Have a great one! ☀️
Thank you! 🙏🙇
