Speaking at STPCon

Speaking at STPCon

The value of a conference is defined by its ability to present cutting edge content (including strategies, techniques and tool solutions) that will enable the attendee to apply what has been learned in his current work environment benefiting the entire test organization by improving processes, techniques, team work and efficiency.

At STP, we seek to provide this cutting edge content by inviting practitioners, consultants and other professionals in the testing industry to share their knowledge and experiences with the attendees at our conferences. After all, who knows better than those who are experiencing the same challenges every day? If you have faced a challenge and found a solution, or if you have developed an expertise that will benefit others in the testing community, we invite you to share your knowledge with your peers. As you think about submitting a proposal to speak at one of our conferences, please consider the following tips as you draft your proposal.

We are now accepting proposals for our Fall 2016 conference.
SUBMIT A PROPOSAL TO SPEAK

3 Tips For Improving Your Chances of Selection at STPCon:

Speaking at STPCon
1-130

Make your title extremely appealing.
Many attendees will scan through the conference schedule and a strong title will catch their eye and take them further into reading your abstract. Think of creative ways for catching their attention. Numbers usually get them (for example “10 things you can do to improve your testing experience”). Hot topics get them as well (for example “why is everyone using Selenium and why am i not?”). Catchy titles get them to read further as well (for example “How Obama helped me learn to test” or “Angry Birds Testing”)

2-130

Catch their attention with an opener that makes them feel like you understand them.
In other words, if you ask a question in the opener or state a fact, it makes them feel a connection. For example “Does your senior management respect your testing team?” or “Do you find it hard in your testing organization to keep your automation scripts updated” or “It has been stated many times that 7 out of 10 people will always miss a simple change in a product – and not test it”. Once you have their attention, then give them specifics on “WHY” they should be there. Imagine yourself reading your abstract and ask yourself “if i knew nothing about this, would i be interested in it”? Then design your description so that when someone reads it, they can’t stop – they are racing from word to word so that they can get to the takeaways and see more and more on this abstract.

3-130

What’s in it for me?
Imagine you are the attendee. Imagine you are reading this abstract. What would make you want to come here. What things would you want to see that will be given to you in this session or workshop that would be so useful that you could take it back and use it right away? Make your bullet points sell your product. Guarantee them things you know you can deliver. But don’t overdo it. Don’t say “i will give you the secret to testing and you will know how to improve testing by 500%”. We know we can’t do that. But you could say that one of your takeaways would be “5 tips to improving the communication between your testing organization and the CXO staff”. After you’ve written your 3-5 takeaways, go back through them, and imagine that you’re not the speaker. Would you want to have these takeaways? Would they appeal to you? Attendees will read abstracts, and descriptions, but the takeaways are the appeal. Promise them what you can deliver, and make them say in their mind “I got to attend this – i can use this RIGHT NOW!”