Audit the halo in your introduction

Dev writes an introduction for a partner meeting that leans on prestigious companies and vague transformation work. The partner still does not know why Dev is useful today. Halo audit: impress cue, evidence replacement, listener connection The common trap is trying to sound impressive before making the interaction useful. That gives primacy to performance and invites halo to do the wrong work. Context Name the decision, pressure, or problem the other person brings. This creates warmth because it proves you are oriented to their world. Path Give the two or three-part route for the conversation. This creates competence because it…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in