Interesting read George. I love Radical Candor by Kim Scott myself as she has done a great job of simplifying how to be honest and direct at the same time.

I use a slightly different framework for giving feedback — Situation, Observation, Impact with an Open ended question. Describe the situation, followed by your observation of the situation (not the judgement). Talk about the impact and let the person reflect on this feedback with the open ended question

e.g. instead of saying “you write bad code”, say “I want to talk to you about your code (situation). I noticed that your code has many bugs (observation). Writing code with many bugs will not only take you longer to fix them all, it will be a waste of your time. It will also require a lot more time for code reviews (impact). What do you think? (open ended question)