The deadline to submit is just two weeks away, and it is time for new year’s resolutions. Do you have some knowledge to share? I see everyday on SCN where individuals freely share their knowledge with the community. Consider sharing your knowledge at ASUG Annual Conference, which is June 3-5, 2014 in Orlando, Florida.
The ASUG program / tracks are listed here. I’ve written tips in other blogs, but to expand even more on this, I recommend the following:
1. Strong Title to Remember
Some session titles I remember from last year include “How to Build Your Crystal Ball” using SAP’s Predictive Analysis. Another great title came from SAP’s Timo Elliott who had BI Culture Eats Technology for Breakfast.
If you are submitting a customer story, place the customer’s name in the title, similar to last year’s The Schwan Food Company Develops a Roadmap to Employ Data Warehousing on Enterprise HANA
2. Customer Stories
Any abstract that covers how a customer solved a business problem is a welcome abstract for a user conference. Case studies and best practices are also welcomed.
Avoid jargon and abbreviations in your abstract. As an example, using “BOE” in an abstract may not mean all things to all people. In a previous life, this meant “Board of Equalization”.
4. Why should you submit?
I am going to copy (with attribution) the following:
“You don’t need to present on “newest stuff” to get accepted….It is also a great way for you to deepen your own personal understanding of a particular topic. Even though you may think you know a topic very well, it is amazing how building the presentations will force you to pick up every single detail as part of you research. ” – Stephen Johannes
Speakers (following ASUG speaker policy) also obtain complimentary registration to one of the largest SAP events of the year. More importantly, you build your knowledge when you present.
5. Where should I submit?
Submit your abstract here
So Don’t Delay – Submit your Abstract Today” – Kristen Dennis
Follow hashtags #ASUG2014 #SAPPHIRENOW on twitter.
Photo by ASUG