This book found ME, actually. I’d been personally struggling with this topic and been working to develop my skills in this area; as I was walking back from my development meeting at work, I saw it on a coworker's desk, staring me in my face, kinda glowing from its faded yellow cover. It was practically BEGGING me to pick it up.
Without further ado, here are the pieces I found most effective in helping me with this effort.
- Think sound bites. The news ditches any interview it can’t explain in a snippet; similarly, others will disregard the substance of your conversation if it can’t be explained in 30 seconds or less.
- Don’t waste words. It’s surprising how often opportunity is wasted because there isn’t a clear objective being communicated.
- What are you trying to accomplish?
- Know the objective of the right person to generate the right result.
- Find your hook. It can be in question form, or a visual hook, which can be a 30-second anecdote. It can be dramatic or humorous, but know your audience!
- Keep a hook book to jot down ideas when you think of them, in case it inspires ideas when needed.
- Ask for what you want! At the end of a meeting where you are trying to decide how to proceed on a project, don’t EVER say, "let's think about it" as a response to an idea, without a clear action plan for results.
- Decide what kind of 'close' is warranted for your objective. 'Action close' with a specific deadline, or the 'reaction close', which is a more subtle, indirect ask strategy.
- Paint a picture with words - e.g. "Deficits will spread a subtle, devastating poison through the economic bloodstream” is clearly more effective than simply saying, "deficits will badly affect the economy."
- Use simplified language and analogies when appropriate.
- Videotape your workshop or session. In our case, we can also listen to a recording of a call to determine what we need to improve articulation-wise.
- Outline / don’t memorize content.
On paper, the same rules apply. Present no more on paper than can be read aloud in 30 secs.
- Most importantly, know when to stop. 😉
(How did I do?)