๐ง๐ต๐ฒ ๐ผ๐ป๐น๐ ๐๐ต๐ถ๐ป๐ด ๐๐ผ๐ฟ๐๐ฒ ๐๐ต๐ฎ๐ป ๐ฎ ๐ฑ๐๐น๐น ๐ธ๐ฒ๐๐ป๐ผ๐๐ฒ? ๐ ๐ฑ๐๐น๐น ๐ถ๐ป๐๐ฟ๐ผ.
- Christian Hunt
- Oct 15
- 1 min read
When event organisers ask for a bio, I always double-check why.
The last thing I want is for them to introduce me by reading it out loud.

Sure, my past roles matter โ theyโve shaped how I think โ but if people only listen because of my CV, Iโve already lost them.
A bioโs fine for the ๐ฑ๐ณ๐ฐ๐จ๐ณ๐ข๐ฎ๐ฎ๐ฆ (though even then, I like it to hint at ๐ธ๐ฉ๐บ the audience should listen, not just where Iโve worked).
But when it comes to the ๐ช๐ฏ๐ต๐ณ๐ฐ๐ฅ๐ถ๐ค๐ต๐ช๐ฐ๐ฏ, I say: '๐๐ฆ๐ญ๐ญ ๐ต๐ฉ๐ฆ๐ฎ ๐ธ๐ฉ๐บ ๐บ๐ฐ๐ถ ๐ช๐ฏ๐ท๐ช๐ต๐ฆ๐ฅ ๐ฎ๐ฆ.'
What made you think Iโd have something this audience would actually find useful?
Thatโs what people need to hear, not a list of job titles.
Something like:
'I invited him here because he brings a perspective we don't have. You're going to laugh, but you're also going to find yourself re-thinking how you do Compliance'
If they really need a scripted intro, Iโll send one; Iโve got a fun version tucked away.ย
But itโs ๐ด๐ฐ ๐ฎ๐ถ๐ค๐ฉ ๐ฃ๐ฆ๐ต๐ต๐ฆ๐ณ when they make it their own.
If the content doesnโt make people curious enough to ๐ธ๐ข๐ฏ๐ต to know who I am afterwards, no bio will fix that.




Comments