...

Goals and Approach

Workshop

...

focus

Topic(s)

Influence and Leadership Skills for Architects - driving strategic decisions

...

Example Topics

Getting

...

Consensus  --  Voting Structures, Minimum Specs (Liberating Structures), Affinity Diagrams

...

F2F meeting structure

This would be like an (un)Conference where we would be The structure uses principles from hackathons and unconferences where we are agile in the agenda and deliverables but and focused on creating a set of resources for ITANA members

1. Use break-out groups each concentrating on a topic

Outcomes

...

.

...

1. Most

...

Strawman for an approach

Using principles from hackathons and unconferences.

1. Use most of day 1 is for stage setting. The items listed in Example Topics provide a starting point and by the end of the day we should have topics, leads, and teams to tackle them (topics, not leads).  Teams are encouraged to eat dinner together and begin discussions on their topics.
2. Day 2 is hackathon day.  Teams work on their topic, creating all of the outcomes listed abovebelow.  If they complete their topic, the can choose another one.  This continues throughout the day.
3. Day 3 is presentation day.  Each team should will present their completed topics to the assembled group.

Questions

What about partially completed topics?  Do we want to do something with them?

Do we want to do some presentations on day 2, in order to give the attendees who didn't work on the topic a change to provide feedback and still give the teams time to incorporate the feedback into their tool?

Possible Scenarios

...

Outcomes

1. In person idea sharing and exchange
2. A best practices library relating to the use of these tools
3. A set of guidelines for each tool.  In what context is the tool useful?  Who is the intended audience? What kinds of information does it best convey?
4. Information that can be applied to one or more problems at the home institution.  Ideally that work can be fed back to the library started in the F2F.