Getting attendance approval from your manager is sometimes a challenge, as it takes time and money. This page contains help and suggestions on how to make your case effectively.
When you propose attending DAC it is key to focus specifically on what you will bring back to the organization. DAC is the place to learn the latest practices and to learn how other companies and academics are tackling the same problems that your organization has with fresh ideas. Even though social contacts are an important experience, it is not advisable to stress that you go to DAC to ‘meet old friends’ as that has the air of a leisure activity. DAC is certainly fun, but it is very professional ‘work’.
To demonstrate return on the investment of attending a conference use this "benefits guide" to help you state your case.
After the conference is the perfect time to explain that attending DAC was beneficial for not only you as an attendee, but for your company as a whole. This also helps to ensure that you will be able to attend future DACs. One technique that is used by a number of attendees is the use of a Conference Report. A Conference Report states information about the conference to anyone who wasn't able to attend the conference. You may use this information to teach others, or simply give further justification to your manager. Examples of information that may be included in the report are:
DAC is the premier conference devoted to the design and automation of electronic systems (EDA), embedded systems and software (ESS), and intellectual property (IP).