Difference between revisions of "Summit 2013"
m (fixed category link) |
|||
(8 intermediate revisions by 3 users not shown) | |||
Line 3: | Line 3: | ||
It's going to be so fun that we'll definitely want to do it again! | It's going to be so fun that we'll definitely want to do it again! | ||
− | + | == Precedent (2012 Summit) == | |
− | |||
+ | === Attendee motivations === | ||
Why did people decide to attend Awesome Summit in the first place? | Why did people decide to attend Awesome Summit in the first place? | ||
* cross-pollination/learning from others | * cross-pollination/learning from others | ||
Line 11: | Line 11: | ||
* curiosity | * curiosity | ||
+ | === Purpose === | ||
Meta-Question: What's the purpose of the Awesome Summit? In fact, are we actually even an organisation or just an emergent entity based on some shared interests? | Meta-Question: What's the purpose of the Awesome Summit? In fact, are we actually even an organisation or just an emergent entity based on some shared interests? | ||
+ | |||
* do we need to have an annual one that incorporates as many people from all chapters as possible vs. regional events, some other models etc. | * do we need to have an annual one that incorporates as many people from all chapters as possible vs. regional events, some other models etc. | ||
* based on a completely non-scientific and sub-optimal participatory process, seems like the general consensus of the discussion group feels that there should be another summit next year (roughly around this time of year) | * based on a completely non-scientific and sub-optimal participatory process, seems like the general consensus of the discussion group feels that there should be another summit next year (roughly around this time of year) | ||
− | + | === Boston's process for 2012 === | |
− | + | * started in Jan, but bulk of work to organize has been in the last 2 months leading up | |
− | Boston's process for | + | ** necessity of establishing venues and contracts at least half a year ahead of time however (MIT Media Lab booked in Dec) |
* $25,000 in donations which certainly helped but should not expect to exist for all future summits | * $25,000 in donations which certainly helped but should not expect to exist for all future summits | ||
− | * also ticket sales for the public component of the summit | + | ** also ticket sales for the public component of the summit |
** 124 tickets sold for the public event this time round | ** 124 tickets sold for the public event this time round | ||
* need to be aware that fewer people will generally be able to attend than desired or planned for | * need to be aware that fewer people will generally be able to attend than desired or planned for | ||
** $10,000 was used to subsidize travel for this summit | ** $10,000 was used to subsidize travel for this summit | ||
* the MIT Media lab was made available gratis, which was very helpful, otherwise would cost ~$1000/hour | * the MIT Media lab was made available gratis, which was very helpful, otherwise would cost ~$1000/hour | ||
− | |||
* agenda was decided by fiat more or less by small group of people, major driving reason was just to get everyone together | * agenda was decided by fiat more or less by small group of people, major driving reason was just to get everyone together | ||
* '''Need to establish a feedback mechanism for this summit to determine what people liked, disliked, would recommend''' | * '''Need to establish a feedback mechanism for this summit to determine what people liked, disliked, would recommend''' | ||
− | |||
+ | == Future planning == | ||
+ | |||
+ | === Goals of 2013 Awesome Summit === | ||
+ | * get everyone together | ||
+ | * learning from each other | ||
+ | * making sure we're on the same page (or at least knowing such a page exists) | ||
+ | * celebrate getting to $1,000,000 total grants, as forecast by the data mining team | ||
+ | * recurring themes: | ||
+ | ** helping with trustee turnover or expanding pool | ||
+ | ** soliciting good applications/getting through application slumps) | ||
+ | |||
+ | === Where's the AWESOME in these summits? === | ||
+ | * leaving increased capacity behind in the city i.e. stronger proposals | ||
+ | * Awesome Connect--bringing together network or resources + applicants + award mega-grant | ||
+ | * invite former grantees | ||
+ | * storytelling | ||
+ | * disruptive philanthropy | ||
+ | |||
+ | === Looking forward === | ||
+ | Towards the future: | ||
+ | * IHAS can play a continuing role to seek sponsorship/funding for future summits | ||
+ | * point of connection for entrepreneurs that want to give back''' | ||
+ | |||
+ | === Location === | ||
Deciding on a process for determining location (brainstorming) | Deciding on a process for determining location (brainstorming) | ||
* letter of intent? | * letter of intent? | ||
− | ** Boston's process | + | ** Boston's process |
− | |||
− | Decision-making process | + | === Decision-making process === |
* a lot of existing models have competing pitches presenting at the end of the current summit and then a decision is made there | * a lot of existing models have competing pitches presenting at the end of the current summit and then a decision is made there | ||
* is it at the level of a vote per(active) chapters, per trustee, what? | * is it at the level of a vote per(active) chapters, per trustee, what? | ||
Line 44: | Line 67: | ||
*** potential of the summit planning cannibalizing the vitality of the host chapter's standard activities | *** potential of the summit planning cannibalizing the vitality of the host chapter's standard activities | ||
+ | === Summit Commitee === | ||
Creating a Summit Committee? | Creating a Summit Committee? | ||
− | * separate from a committee to help decide the summit location | + | * <strike>separate from a committee to help decide the summit location</strike> |
* help to ensure that the summit happens each year | * help to ensure that the summit happens each year | ||
* '''BUT''' do we want to duplicate the effort and resources required to have two separate committees? | * '''BUT''' do we want to duplicate the effort and resources required to have two separate committees? | ||
Line 51: | Line 75: | ||
* '''NEEDS:''' a group to determine location, a group to work on logistics, a group to work on programming/content; whether these be separate groups or sub-groups | * '''NEEDS:''' a group to determine location, a group to work on logistics, a group to work on programming/content; whether these be separate groups or sub-groups | ||
− | + | === Selection Process === | |
+ | 1. Pitches made by interested chapters/locations | ||
+ | |||
+ | 2. Mandatory submission of info to committee (opens by Aug 18, closes Sept 29) | ||
− | + | 3. Committee vets submissions and creates short-list of viable possibilities (takes four weeks, requesting page content by Oct 27) | |
− | + | ||
− | + | 4. Pages posted two weeks later on November 10 | |
− | 3. Committee vets submissions and creates short-list of viable possibilities | + | |
− | 4. Vote by | + | 5. Vote by active chapters based on the short-list (2 weeks, closing Nov 24) |
− | + | * One vote per chapter for preferred location. PREFERENCE | |
− | + | * Individuals indicate ''where'' they '''could''' attend, were it to be at any of those locations. ABILITY | |
+ | |||
+ | 6. Committee takes the vote into consideration and then decides (one week) | ||
− | + | 7. Announcement of next year's location at the summit (December 1) | |
+ | [http://farm9.staticflickr.com/8025/7623606110_d208bba858_z.jpg timeline image] | ||
+ | === Tentative Selection Timeline === | ||
+ | * Application process opens | ||
+ | * Close of application process | ||
+ | * Vetting of applications by committee | ||
+ | * Deliberation by committee on short-list (Vetting) | ||
+ | * Submitting groups publish their "pitch page"/Voting begins | ||
+ | * Voting closes | ||
+ | * Announcement of location of summit | ||
+ | === Pitches === | ||
The pitch should: | The pitch should: | ||
* demonstrate solidarity and commitment of chapter (or hosting group if it's a different body) | * demonstrate solidarity and commitment of chapter (or hosting group if it's a different body) | ||
− | * demonstrate | + | * demonstrate strength of chapter and ability to execute |
* mandatory submission component to committee to demonstrate that the capacity to implement exists | * mandatory submission component to committee to demonstrate that the capacity to implement exists | ||
** form/questions to be designed by committee | ** form/questions to be designed by committee | ||
* video or other excitement building pitch would be optional | * video or other excitement building pitch would be optional | ||
− | Potential Criteria (or at least considerations) | + | === Potential Criteria === |
+ | * (or at least considerations) | ||
* urban vs rural areas? environment that leads to retreat style or otherwise | * urban vs rural areas? environment that leads to retreat style or otherwise | ||
− | + | === Value of hosting a summit === | |
− | |||
− | Value of hosting a summit | ||
* potential capacity building for the hosting group | * potential capacity building for the hosting group | ||
+ | * branding/marketing | ||
+ | * improve number/quality of submissions | ||
+ | * exposure | ||
+ | * potential collaborations and expanded network due to all of the above | ||
− | + | === ISSUES === | |
− | |||
− | |||
− | ISSUES | ||
* up till now Awesome XX:YY's have all been pretty ad-hoc groups; summits require much greater level of organization and dare-we-say, structure | * up till now Awesome XX:YY's have all been pretty ad-hoc groups; summits require much greater level of organization and dare-we-say, structure | ||
* no particular failsafe on this right now, but that's okay--worst thing that happens is there's no summit that year | * no particular failsafe on this right now, but that's okay--worst thing that happens is there's no summit that year | ||
** is that actually okay? potential damage to brand/chapters/etc. | ** is that actually okay? potential damage to brand/chapters/etc. | ||
− | * this is, of course, a work in progress and subject to | + | * this tentative process is, of course, a work in progress and subject to change due to good arguments (that could also be part of pitches, especially with regards to dates, etc.) |
− | * | + | * an actual pre-defined agenda, or a structure by which participants can create large chunks of the agenda? |
+ | * looking towards the future, if IHAS wants to expand Awesomeness internationally in a major way, imperative to involve reps from international chapters as part of future Summit Commitees | ||
+ | |||
+ | == Resources == | ||
+ | To be uploaded | ||
[[category:Saturday]] | [[category:Saturday]] | ||
[[category:Summit 2013]] | [[category:Summit 2013]] | ||
[[category:Meta]] | [[category:Meta]] |
Latest revision as of 10:24, 26 July 2012
It's going to be so fun that we'll definitely want to do it again!
Precedent (2012 Summit)
Attendee motivations
Why did people decide to attend Awesome Summit in the first place?
- cross-pollination/learning from others
- getting inspired
- curiosity
Purpose
Meta-Question: What's the purpose of the Awesome Summit? In fact, are we actually even an organisation or just an emergent entity based on some shared interests?
- do we need to have an annual one that incorporates as many people from all chapters as possible vs. regional events, some other models etc.
- based on a completely non-scientific and sub-optimal participatory process, seems like the general consensus of the discussion group feels that there should be another summit next year (roughly around this time of year)
Boston's process for 2012
- started in Jan, but bulk of work to organize has been in the last 2 months leading up
- necessity of establishing venues and contracts at least half a year ahead of time however (MIT Media Lab booked in Dec)
- $25,000 in donations which certainly helped but should not expect to exist for all future summits
- also ticket sales for the public component of the summit
- 124 tickets sold for the public event this time round
- need to be aware that fewer people will generally be able to attend than desired or planned for
- $10,000 was used to subsidize travel for this summit
- the MIT Media lab was made available gratis, which was very helpful, otherwise would cost ~$1000/hour
- agenda was decided by fiat more or less by small group of people, major driving reason was just to get everyone together
- Need to establish a feedback mechanism for this summit to determine what people liked, disliked, would recommend
Future planning
Goals of 2013 Awesome Summit
- get everyone together
- learning from each other
- making sure we're on the same page (or at least knowing such a page exists)
- celebrate getting to $1,000,000 total grants, as forecast by the data mining team
- recurring themes:
- helping with trustee turnover or expanding pool
- soliciting good applications/getting through application slumps)
Where's the AWESOME in these summits?
- leaving increased capacity behind in the city i.e. stronger proposals
- Awesome Connect--bringing together network or resources + applicants + award mega-grant
- invite former grantees
- storytelling
- disruptive philanthropy
Looking forward
Towards the future:
- IHAS can play a continuing role to seek sponsorship/funding for future summits
- point of connection for entrepreneurs that want to give back
Location
Deciding on a process for determining location (brainstorming)
- letter of intent?
- Boston's process
Decision-making process
- a lot of existing models have competing pitches presenting at the end of the current summit and then a decision is made there
- is it at the level of a vote per(active) chapters, per trustee, what?
- having a committee struck to help lead to a decision on venue
- would they decide by fiat, would they make a decision after a collaboratively decided short-list, vice versa?
- have the committee include a rep (or multiple reps) from each short-listed location
- potential conflicts of interest that result from this
- potential of the summit planning cannibalizing the vitality of the host chapter's standard activities
Summit Commitee
Creating a Summit Committee?
separate from a committee to help decide the summit location- help to ensure that the summit happens each year
- BUT do we want to duplicate the effort and resources required to have two separate committees?
- perhaps having a sub-committee that works to decide a location
- NEEDS: a group to determine location, a group to work on logistics, a group to work on programming/content; whether these be separate groups or sub-groups
Selection Process
1. Pitches made by interested chapters/locations
2. Mandatory submission of info to committee (opens by Aug 18, closes Sept 29)
3. Committee vets submissions and creates short-list of viable possibilities (takes four weeks, requesting page content by Oct 27)
4. Pages posted two weeks later on November 10
5. Vote by active chapters based on the short-list (2 weeks, closing Nov 24)
- One vote per chapter for preferred location. PREFERENCE
- Individuals indicate where they could attend, were it to be at any of those locations. ABILITY
6. Committee takes the vote into consideration and then decides (one week)
7. Announcement of next year's location at the summit (December 1)
Tentative Selection Timeline
- Application process opens
- Close of application process
- Vetting of applications by committee
- Deliberation by committee on short-list (Vetting)
- Submitting groups publish their "pitch page"/Voting begins
- Voting closes
- Announcement of location of summit
Pitches
The pitch should:
- demonstrate solidarity and commitment of chapter (or hosting group if it's a different body)
- demonstrate strength of chapter and ability to execute
- mandatory submission component to committee to demonstrate that the capacity to implement exists
- form/questions to be designed by committee
- video or other excitement building pitch would be optional
Potential Criteria
- (or at least considerations)
- urban vs rural areas? environment that leads to retreat style or otherwise
Value of hosting a summit
- potential capacity building for the hosting group
- branding/marketing
- improve number/quality of submissions
- exposure
- potential collaborations and expanded network due to all of the above
ISSUES
- up till now Awesome XX:YY's have all been pretty ad-hoc groups; summits require much greater level of organization and dare-we-say, structure
- no particular failsafe on this right now, but that's okay--worst thing that happens is there's no summit that year
- is that actually okay? potential damage to brand/chapters/etc.
- this tentative process is, of course, a work in progress and subject to change due to good arguments (that could also be part of pitches, especially with regards to dates, etc.)
- an actual pre-defined agenda, or a structure by which participants can create large chunks of the agenda?
- looking towards the future, if IHAS wants to expand Awesomeness internationally in a major way, imperative to involve reps from international chapters as part of future Summit Commitees
Resources
To be uploaded