Versions Compared

Version Old Version 14 New Version 15
Changes made by

seth.greene

Olivier Crépin-Leblond

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

B.S - STRENGTHS                                                                          

B.S.1 - Membership diversity can bring talent
B.S.2 - Local organizational knowledge brings unbiased view of operations: 
    1. Lower costs of implementation 
    2. Local political insight
B.S.3 - Local community input: 
    1. Grassroots input 
    2. RALO involvement is an asset   
B.S.4 - On-the-ground, workable and well-defined actions 
B.S.5 - At-Large uses electronic tools to bring its members' different backgrounds and experiences to bear on planning process

ADD ALS CONTRIBUTIONS HERE

B.W - WEAKNESSES                                                                   

B.W.1 - At-Large reacts slowly
B.W.2 - At-Large maturity still not completely achieved
B.W.3 - Translations: 
    1.  Number is limited
    2.  Delays exist

ADD ALS CONTRIBUTIONS HERE
- Lack of travel support to members for at least once a year face to face meeting producing a two tier volunteer experience.  Those who are subsidized have a vested interest to be more involved leaving a second class group of volunteers OCL: yes
- Minimum news on ICANN development in the news and social media OCL: no this does not fit in operational planning processes
- Lack of real leadership on the phoney pharmacy sites, etc OCL: no this does not fit in operational planning processes 

|

B.O - OPPORTUNITIES                                                                      

B.O.1 - Strengthen maturity of At-Large by improving processes
B.O.2 - Use At-Large as a powerful communication channel
B.O.3 - At-Large operating plan could be a useful step in preparing an accurate budget
B.O.4 - At-Large's abilities and reach could be used to convey ICANN's message locally
B.O.5 - At-Large could incorporate public participation into ICANN's operational planning
B.O.6 - At-Large comments, as result of consensus-based process, should be considered by ICANN Board and staff 
B.O.7 - Plans (such as a Second At-Large Summit or RALO GAs) proposed by At-Large should be considered by ICANN 

ADD ALS CONTRIBUTIONS HERE

B.T - THREATS                                                                            

B.T.1 - Lack of resources (including operational funding, staff headcount, translation services, Web services, conference-call services, other daily logistical needs, etc.) 
B.T.2 - Less operational effectiveness and visibility leading to a lack of volunteer interest
B.T.3 - Lack of volunteers would limit operational planning and capabilities

ADD ALS CONTRIBUTIONS HERE

...