Choose the Talk, Not the Résumé

Start from the problem your room already feels, then test the talk against it. Ask for the proof a booking decision deserves: a watchable film of the talk in a real room, the one-sheet, and a planner who has hosted it. The Library exists so that test can be run before anyone gets a call back.

That ordering, problem first and credentials second, is the whole argument of this piece. A résumé answers the question, "Who is this person?" A booking decision has to answer a different one: "What will this talk do for the people in our room, on our date, with our problem in the air?" The two questions are related, but they are not interchangeable, and committees that confuse them pay for the confusion in the only currency that matters: an hour of their audience's attention that does not come back.

Résumés are also the easiest material to overvalue. They are written to accumulate: degrees, titles, stages, logos. Accumulation feels like evidence, and in a committee meeting it has a practical advantage, because it can be compared quickly. One speaker has spoken at more places than another, so the discussion moves to arithmetic. But a long list of rooms says where a speaker has been, not what happened in those rooms, and it says nothing at all about what will happen in yours. The talk is the product being bought. The résumé is, at best, supporting documentation for the talk, and it should be read in that order.

So run the test in the right sequence.

The third leg of the proof, the planner who has hosted the speaker, deserves more weight than committees usually give it. A reference from a working planner is not a testimonial; nobody puts a critic on their reference list. It is something better: a witness to the operational facts a film cannot show. Did the speaker arrive prepared on the audience? Did the talk land with this kind of room, at this size, in this slot? Did the room do anything afterward? Two of those three questions cannot be answered from a résumé at all, and the third can only be answered by someone who was responsible for the outcome. Ask them, and ask them before the call back, not after the contract.

A worked example from the founding issue

Take the founding issue's cover talk, "Storytelling That Sells" by Ron Lynch, and run the test in both orders. Résumé first, you get a remarkable career: more than $6 billion in consumer products sold, roughly 30 brands launched, a partnership at Cesari Direct Television, work for GoPro, Samsung and OxiClean, and a Screen Actors Guild card earned under Robert Altman. It is the kind of résumé that ends committee discussions early. But notice what it does not tell you: whether a room full of your members should spend an hour on storytelling.

Problem first, the evaluation changes. The talk's stated problem is precise: most speakers tell stories that entertain and evaporate. Its three pillars then read as a working method rather than a performance: attention first, because the hook is a promise the story has to keep; demonstration over description, because people believe what they watch happen; and the story the buyer tells himself, because that is the version that actually moves a decision. The origin story, a career in direct response where a story lived or died by whether the phone rang, now functions the way a credential should: it explains why this speaker's method is disciplined rather than decorative. A committee booking for a sales, marketing or leadership audience can defend this choice on the talk's merits. A committee that booked the résumé alone could not have told you what the room would do differently on Monday.

The committee checklist

• State the room's problem in one sentence, in the audience's own words, before any speaker is discussed.
• Read the talk's stated problem and pillars first; read the biography second, as corroboration only.
• Watch the film of the talk in a real room, not a sizzle reel cut from applause.
• Check the one-sheet: problem, pillars and origin story on a single page, consistent with the film.
• Ask for a planner who has hosted this speaker and put the question to them directly.
• Ask what the room will do differently the week after, and require an answer from the talk itself.
• Record the reason for the booking in terms of the room's problem, so next year's committee inherits the reasoning.

None of this diminishes credentials. It demotes them to their proper rank. A speaker's history is the evidence that a talk's promise is earned; it is not the promise. Committees that keep that order find their post-event conversations change character. They stop asking whether the speaker was impressive and start asking whether the room moved, which is the only question the booking was ever supposed to answer. Choose the talk, and let the résumé do the smaller, honest job of confirming that the person delivering it has earned the room's trust.