2 Comments
User's avatar
Pensy Group's avatar

“Never ignore it” is the line I wish every new manager would tattoo on their forehead.

Your Harrods story nails why “small” issues get expensive: it quietly resets the standard for the whole team. I also love how the 4P’s keeps it from turning into a character indictment—Purpose + Proof does so much to lower defensiveness.

When you’re doing the “Path” step, do you ever explicitly name *what support you’ll provide* (so it doesn’t feel like ‘fix it or else’), or do you keep it lean and outcome-focused?

Heather Elkington's avatar

On Path, I do usually name the support, but I keep it intentional and light. The aim is to remove the fear without removing the ownership. I’ll be clear on what good looks like, outline what I can support with if needed (unblocking, feedback, context), and then be explicit about what stays with them.

If you skip support, it can feel like 'fix it or else'. If you overdo it, you accidentally rescue. Path is about holding that middle ground.

And I’m glad you called out Purpose + Proof as lowering defensiveness is often the work before the work.

Thanks for your comments! H