The launch-call screen share no one wants to challenge
Redirect a blame-heavy client update toward shared purpose, observable facts, and a repairable request.
The client joins in two minutes. Leo is about to frame the delay as another team's fault. What should Maya say before the client joins? Anchor on the shared client outcome and turn the slide into observable risk plus a decision request. Right. This protects mutual purpose, keeps the SBI data clean, and ends with a concrete NVC-style request instead of a blame story. Let Leo vent on the call so the client hears how serious the internal breakdown was. Weaker. It confuses emotional release with candor and violates the Crucial Conversations safety principle by making another team the target.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in