...
- Keep corporate introductions to a minimum, in the interest of time. Get to the meat of the topic.
- Present a technical challenge (and if the talk abstract already presents it, this too can be short, but you may might prefer to highlight on a particular aspect)
- Then present solutions. Do not be afraid to be opinionated here, since these sessions are for "several companies unique view on a subject".
- We have a technical audience and this is not a "business track". Some tips:
- Use the opportunity to describe several different approaches (if you have experience trying them),
- include criteria for choosing one method over another, whether based on practical tryouts, or on theoretical reasoning,
- ... and try to include hard technical data which is useful to guide a technically minded audience: Memory footprint, size, lines of code, performance benchmarks, and so on.
- Finally, including negative experiences, mistakes, or reasons why an alternative did not work out, is also extremely useful for everyone. While that requires courage, please remember that these sessions are about sharing of real-world experience!
- RoE should when possible try to describe production experience. If you have experience from putting your ideas into actual car production, make sure to show this. If you don't, then of course you will rather present your experience from evaluating ideas in a trial setting.
- Finally your company is of course free to take this opportunity to mention a solution you may have in your portfolio (i.e. a solution to the presented challenge, not other irrelevant products). As you can see, the presentation is not expected to be a plain "sales pitch" – it ought to explain technical rationale for the offered product, and the rest of the presentation material should overall add to the shared body of technical knowledge.
- While considering the above, you may still interpret the topic quite freely. We are grouping together diverse aspects in this session and as you can see, the abstract for this session is a shared one. But different speakers will have different things they feel are important to highlight and if you are presenting something on the boundary of the topic description, that's probably OK too. We selected your company for a reason.
- If the shared abstract totally does not match your intentions at all, just let us know and we should discuss it, but note that there is some flexibility built in.
- Finally, there might not be time for Q&A, but in many AMM setups we have a related workshop time in which we can follow up on what was presented. That is where most audience/participant discussion is expected to happen.
Let's use this guideline for speaker slot length:
=< 20 minutes –> no Q&A
>20 minutes** -> optional Q&A, speaker decides (but stay within allotted time)
...