1. Objectives Definition Instructions Mark Melanson 8 January 2012

2. Team Activity Agenda Summary Instructions and overview ~ 20 minutes Team activities ~ 1 hour 10 minutes Break/Gather and consolidate team data ~ 10 minutes Review Feedback ~ 1 hour 2

3. Logistics Each table has been arranged to have diverse representation and perspectives Each table has a TAC committee member to help facilitate (but not contribute specifically) TAC member will help capture assessments, rationale/comments on template and keep track of time 3

4. 4 First Step – Conference Models for Review Each team (table) is assigned a conference model to evaluate Conference models (reference):  Consolidated  Integrated  Unified  Current

5. Step Two – Topics for Review 5 For their conference model, each team is assigned three topics to evaluate Discuss and evaluate how the conference model might impact each topical area Assign an Assessment level Provide supporting rationale, comments, and suggestions Strong Improvement Modestly Improves No Impact Strongly Degrades Modestly Degrades

6. Perspective and Scenario Building Please remember to envision impacts for a future period (3 to 10 years into the future)  How will technology evolution impact conferences?  What products might exist in that period?... Think about all the trends noted and consider what the future might look like to perform your evaluation  Even the current approach will have potentially significant impacts in that time frame 6

7. Template  Evaluation will be captured by your facilitator 7

8. Topics Technical Strength  depth and breadth of material available at conferences Systems and Integration Content  content pertaining to systems and systems-level integration efforts including processes, tools, technical discipline integration system level development and tradeoffs. Also contains management and technical oversight approaches and processes. High-level Keynote speakers and plenary sessions  the ability to attract senior-level speakers and participants with broad leadership experience and information. 8

9. Topics Exhibits  the ability to show or demonstrate products, capabilities, tools or other services in a collaborative environment available to conference participants. Ability to Network  formal or informal venues for collaboration with peers or peer groups during conference events. Ability to attract broad aerospace community  the ability to attract a broad range of constituencies including academia, government, and industry as well as differing vantage points within those communities including research, design, development, management, production and in field support of aerospace systems. 9

10. Topics Relevance to the aerospace community  the overall sense that AIAA conferences are addressing the broad and current range of key technical,systems, and programmatic topics germane to today's aerospace culture. Ability of mixed professional and volunteer staff to plan and execute  the ability to effectively and efficiently handle the logistics and details of planning and executing conferences Appeal to young professionals  the ability of conferences and venues to attract increasing numbers of young professionals participants 10

11. Step Three – Review and Feedback All your feedback is important and will be used, but due to the limits of the time available, we will only have time in the workshop to focus on the “strongest” feedback  We will not do specific “team report outs” We will review each conference model and invite those teams that rated a topical area with “strong” impacts (+ or -) to provide verbal support for their opinion  We will do that using the microphones on the table 11

12. Step Four – Final Feedback Each team will be given an opportunity to provide any additional comments or feedback  Facilitators, use row 20 for this input 12

13. Questions? 13

14. Leadership Lessons from Dancing Guy 14 http://sivers.org/ff

15. What’s That Got to Do with Us? Each of you is a leader in AIAA and as such will either help or hinder any strategic movement forward Bringing people onboard any proposed change is a really tough job, but as you just saw, it can be done (even if you are the lone nut initially) Please help bring your teams onboard and help create a positive movement for change 15

16. 16