How to announce a talk you are giving
Announcing a talk asks for something no other announcement here asks for: a block of somebody's future time, committed in advance, on the strength of a description of an argument that does not exist yet.
You are asking for future time on an unfinished thing
The reader has to decide now about an event later, and the only evidence available is your description of a talk you probably have not written. That is a genuinely hard sale, and the standard post makes it impossible by describing the occasion rather than the content: the lineup, the venue, the excitement. None of that helps somebody decide whether to be in the room, because the room is not the product. The claim is. A talk announced by its argument gives a reader something to agree or disagree with immediately, which is the only mechanism available for making a future commitment feel worthwhile now. It also has a useful secondary effect on the speaker, since a stated argument is much harder to fill with a survey of the field later.
The rule for this one
State the argument, not the occasion. One sentence a reader could disagree with, then the practical details.
What the category publishes, and what the rule produces.
The first draft is a composite written to match the register the ranking pages for this query actually publish. It quotes no company and no real post. The second obeys the rule above and nothing else, so anything that changes between them is the rule doing it.
The version everyone posts
Excited to share that I will be speaking at the conference next month! I will be joining an incredible lineup of speakers to share insights on the future of our industry. It is going to be an amazing few days. Come say hello if you are going to be there!
The version that obeys the rule
I am giving a talk next month arguing that most design systems fail for an organisational reason rather than a technical one, and that adoption is a staffing decision. It is 25 minutes on the Thursday afternoon track. If you disagree with the premise, that is the conversation I actually want to have afterwards.
It describes the event, not the talk. A reader cannot tell what will be argued, so there is nothing to decide about, and "come say hello" is a request aimed only at people already attending.
6 of 10 measured dimensions moved.
Both drafts were read by the engine behind our free brand voice generator. It is arithmetic over the text rather than a judgement, which is the reason it is used here: every figure below can be checked by counting the draft printed above it.
| Dimension | Before | After | Moved |
|---|---|---|---|
| Sentences | 4 | 3 | Yes |
| Words | 50 | 53 | Yes |
| Average sentence, in words | 12.5 | 17.7 | Yes |
| Longest sentence, in words | 18 | 29 | Yes |
| Contractions per 100 words | 0 | 0 | No |
| Speaks to the reader | No | No | No |
| First person (we, our, us) | 3 | 2 | Yes |
| Second person (you, your) | 1 | 1 | No |
| Vocabulary richness, out of 100 | 74 | 83 | Yes |
| Contains a stock phrase | No | No | No |
Read across all fifteen moments the pattern is sharper than any single page: the hub has the corpus numbers.
What earns the post
- The claim the talk makes, phrased so somebody could take the other side.
- The specific slot and length, so it can go in a calendar rather than a vague intention.
- What you want from the room afterwards, which is usually an argument rather than a hello.
When not to post it at all
Skip it when you have not decided what the talk says. Announcing the slot first and the argument later produces a post that has to be repeated, and the second post gets less attention than the first would have.