Client work is the strongest raw material for a conference talk, because it carries the one thing an audience cannot get from a summary or a blog post: a real decision made under real constraints. At the same time, client work arrives messy, shaped by a brief that interested only one account, and often wrapped in confidentiality. Preparing a talk from it means extracting a transferable lesson and leaving the identifying detail behind.
This is a checklist for turning a single engagement into a session you can deliver with confidence. It assumes the client has agreed that you may speak about the work in general terms, and that anything you present is honest about your own contribution and the team around you.
Start with the lesson, not the project
A strong conference session is built around a method other people can reuse, not a story about how clever your team was. Before you write a single slide, ask what the project taught you that you did not know at the outset. What assumption did you start with, and what evidence forced you to abandon it? Which step would you now repeat, and which would you drop?
If the answer is only that you delivered the thing on time, there is no talk yet. Curators and audiences are looking for a claim they can test against their own work. A useful lesson is usually a decision rule: when this condition appears, this approach is safer than the obvious alternative. That kind of insight survives being moved out of its original context.
Shape the story around one decision
A project contains dozens of choices, and trying to cover all of them is the fastest way to lose a room. Choose the single decision with the highest stakes and the clearest reasoning, then build the talk backward from it.
Explain the situation in plain terms: the constraint you faced, the options that were genuinely on the table, and why the obvious one was not the right one. Show the trade-off you accepted rather than pretending it did not exist. Then describe what actually happened, separating the outcome you can evidence from the outcome you merely hoped for.
This structure, problem, options, trade-off, result, carries an audience through a talk without needing dramatic hooks. It also keeps you honest, because every section has to answer a question a sceptical peer would ask.
Remove what belongs to the client
Most client work cannot be presented verbatim. Trade secrets, unreleased plans, financial figures and named individuals are usually off the table, and that is exactly where the temptation to overshare is strongest. Remove the identifying material before you design anything else, so the talk is built on what you are allowed to say.
Protecting confidentiality without losing the point
There are established ways to share a real lesson while respecting an agreement. You can describe a single client relationship as a composite pattern drawn from several engagements, as long as you say that is what you have done. You can express an absolute figure as a relative change, or describe a direction rather than a number. You can talk about a category of organisation instead of the organisation itself.
If the confidentiality terms are unclear, read the contract and, where it matters, take advice before you submit an abstract. Event organisers can normally accommodate a talk that has been cleared in advance, and they will respect a speaker who takes the boundary seriously. Nothing on stage is worth a breach of trust.
Build slides that carry the argument
Slides should support the reasoning, not replace it. A common mistake is to reproduce a project deliverable on screen and talk around it, which turns the session into a portfolio review. Instead, design each slide to make one point in the argument you mapped earlier.
Use a small number of words per slide, and let the diagram, the before-and-after, or the simple flow do the work. Put the responsibility on yourself to explain the nuance out loud. If you find yourself reading slides aloud, they are too dense.
Rehearse for the clock and the room
Conference sessions are timed, and overrunning is remembered far longer than a slightly rushed conclusion. Rehearse with a timer until you consistently finish with a couple of minutes to spare, which leaves room for questions and for the small unplanned moments that make a live talk feel human.
Rehearse out loud, once in front of a colleague who is not close to the project. Their questions will reveal the parts of your argument that only make sense to you. Adjust those parts before the audience does the same job less gently.
Turn the talk into lasting proof
A talk that nobody can find afterwards has limited value for your profile. Ask the organisers whether the session is recorded, and if it is, keep the link in one place alongside the abstract and the slide deck. Where recording is not offered, a clear set of slides and a short written summary still document what you delivered.
Place a short, dated entry on a speaker page on your own site. Over time, this record shows a consistent line of thinking rather than a single appearance, which is what organisations check when they are deciding whether to invite you again.
Practical checklist
- [ ] Ask what the engagement taught you that is reusable outside the original brief.
- [ ] Choose the single most consequential decision as the spine of the talk.
- [ ] Map the problem, options, trade-off and evidenced result before designing slides.
- [ ] Remove client names, proprietary detail and unreleased information at the start.
- [ ] Confirm what the contract allows and take advice when the terms are unclear.
- [ ] Anonymise or composite examples, and describe relative changes rather than absolute figures.
- [ ] Rehearse out loud with a timer until you finish with time left for questions.
- [ ] Archive the recording, slides and abstract so the talk becomes documented proof.
Contributing to BGTC Voice
Turning a client engagement into a clear, confidentiality-safe talk is a skill that transfers directly to writing. If you have prepared a conference session around a real decision and want to explain your method in more depth, BGTC Voice welcomes practical contributions. Submissions should stay within what client agreements allow and focus on the reasoning behind the work.