Conference programmes are built from many proposals, and most are read quickly. A programme committee is often looking for a reason to say no, because there are more submissions than slots. Your talk title and speaker bio are the two pieces of text a reviewer sees before anything else. Getting them right is less about self-promotion and more about making the value of your session easy to see.
This guide explains how to write a talk title and a speaker bio that help a reviewer understand what you will deliver and why you are the person to deliver it. It is a guide to structure and wording, not a promise of selection.
Understand who reads your proposal
Before writing anything, think about the people reading it. A programme committee usually contains a mix of organisers, past speakers, and practitioners from the field. They are assessing fit: does this talk suit our audience, does it fill a gap in the programme, and can this speaker deliver it well?
They are also working to a brief. They may need a particular theme covered, a range of speakers, or a balance of senior and emerging voices. Your job is not to guess that brief exactly, but to make your contribution specific enough that a reviewer can slot it into a programme.
Read the call for speakers carefully. Note the themes, the format of the sessions, the expected audience, and any limits on length or tone. A proposal that ignores the brief looks careless, however strong the topic.
Writing a talk title that describes value
A good talk title does two jobs: it tells the audience what they will get, and it makes them curious. Titles that promise a clear outcome tend to perform better than titles built around a clever phrase whose meaning is unclear.
Start with the concrete subject. What will you actually cover? If the talk is about how a team introduced a design system, say so. If it is about the trade-offs of a common method, name the method. Reviewers and attendees both scan titles for relevance, and a specific title is easier to place.
Then add a sense of the angle or insight. A title such as "Lessons from Rolling Out a Component Library Across Three Teams" is specific and hints at practical value. Avoid titles that consist only of a question, only of jargon, or only of a metaphor. A short, plain statement of the benefit usually beats wordplay.
If the proposal form allows, include a subtitle or a one-line summary. Use it to state the audience and the takeaway in plain terms.
Structuring a speaker bio
A speaker bio is a short argument for why you are the right person to give this talk. It is not a full career history. Keep it focused on the experience that makes this specific session credible.
A reliable structure moves from role to evidence to relevance. State who you are and what you do now. Then give one or two concrete pieces of evidence, such as a project you led or a problem you solved. Finish by connecting that experience to the talk, so the reviewer can see why you are suited to this subject.
Write in the third person for most conference contexts, using your name rather than I. Use present tense for your current role and past tense for specific achievements. Avoid adjectives that claim quality, such as world-class or leading, unless the claim is verifiable. Concrete nouns carry more weight than praise.
Keep the bio free of confidential details. Naming a client may be fine, describing their internal numbers may not. Where you cannot name an organisation, describe the category instead, such as a mid-sized public body or a growing product team.
Matching the bio to the talk
The most common fault in a speaker bio is that it describes a general career rather than the expertise this talk requires. A bio for a talk about pricing freelance work should lead with the years you spent negotiating those projects, not with an unrelated earlier career. Trim anything that does not support the case for this session.
Adapting length and format
Most organisers ask for a short bio and a longer one, and some ask for a headline version of a few words. Write the short version first, then expand it. If you can say who you are and why you are credible in two sentences, the longer version is easier to build.
Check the requested word count and respect it. A bio that overruns suggests the speaker will overrun in other ways. Save a plain-text version without formatting, because submission forms often strip styling and a neatly arranged bio can collapse into a single paragraph.
Common mistakes to avoid
Several faults appear again and again in submissions. Titles that are vague, poetic, or purely promotional. Bios padded with awards and titles that are not relevant to the talk. Copy that talks about the speaker's passion rather than their work. Proposals that ignore the session format or the audience.
Another frequent error is inconsistency. Your bio should match your public profile, your website, and your previous talks. Reviewers may look you up, and mismatched dates or titles undermine confidence.
Submitting and following up
Submit before the deadline, not on it, in case the form has a problem. Keep a copy of what you sent. If the organiser offers feedback, take it seriously, because it is rare and useful.
If you are not selected, ask whether there may be a fit for a future programme. Many speakers are chosen on a later attempt once the committee knows their work. A polite follow-up keeps the relationship alive without pressure.
Contributing to BGTC Voice
BGTC Voice publishes practical writing from professionals who want to explain their expertise clearly. If you have refined a talk title or a speaker bio after real feedback, or developed a method for matching a bio to a session, an article on the process is a useful contribution. Submissions should describe the method and keep any confidential client or event details out of the text.
Practical checklist
- [ ] Read the call for speakers and note the themes and audience.
- [ ] Write a title that states the subject and the value plainly.
- [ ] Add a one-line summary naming the audience and the takeaway.
- [ ] Keep the bio focused on the experience this talk needs.
- [ ] Use role, evidence, then relevance as the structure.
- [ ] Avoid unverifiable praise and confidential client details.
- [ ] Produce short, long, and plain-text versions within the limits.
- [ ] Keep your bio consistent with your website and public profile.