Dare to Lead — Rumbling with Vulnerability

Sixty minutes, five parts, and a rehearsal you actually do out loud. Built for product teams, because prioritisation, saying no to a stakeholder, and telling leadership a date is slipping are all the same skill wearing different hats.

1. Part 1 Vulnerability is not weakness

   Brown's definition is uncertainty, risk and emotional exposure — which is a description of shipping a product, not of oversharing. Four myths get killed here, including the one that unlocks the sceptics: vulnerability is not disclosure, and vulnerability without boundaries isn't courage.

2. Part 2 Armored vs. daring leadership

   Five of Brown's sixteen armored behaviours, translated into things that actually happen on a product team. The PM who has already decided and then runs discovery to confirm it. The spec rewritten four times before anyone sees it. The eye-roll for every new initiative. Feedback about a person delivered to everyone except that person. It ends with ten seconds of silence: of those five, which one is yours?

3. Part 3 Clear is kind. Unclear is unkind.

   The most useful idea in the book, and the one to keep if you keep only one. Being vague isn't consideration — it's a transfer of your discomfort onto someone else, with interest. The tool is Paint Done: describe the finished thing together before work starts, and ask for it painted back when someone hands you an unclear brief.

4. Part 4 Two tools for the rumble

   "The story I'm making up is…" — six words that separate what happened from what you concluded about it, and hand the other person a door instead of a wall. Then empathy versus sympathy, with a reliable tell: an empathic response almost never begins with "At least".

5. Activity Rumble Rehearsal

   The back half is theirs. Write the thing you are currently not saying at work, rewrite it as an opener you could actually use, practise it out loud on your own, then one debrief question. Anonymous, never naming the other person, cameras off while you write.