Versions Compared

Key

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

...

Strengths                                                                          

- Membership diversity can bring talent
- Local organizational knowledge brings unbiased view of operations: 
    1. Lower costs of implementation 
    2. Local political insight for ICANN

Wiki Markup
\[Now this seems to simply repeat that AL offers local knowledge, which is already in header point\]
  (OCL: local knowledge & local insight is slightly different since the "local knowledge" is of an organizational matter, and "local insight" is of a political matter. This might need to be amended/word-smithed) 
Wiki Markup
\[Olivier:  (a) Do the blue addtions above solve the issue?  (b) Why "for ICANN"?\]

- Local knowledge community input:
Wiki Markup
\[Must distinguish this heading from similar heading above; both refer to local knowledge; state how second one here is different than above\]
  (OCL: agreed - and I must admit I am stalling on this, so I'd like the input of others, please) (OCL: replaced the word "knowledge" with "community input)
    1. Grassroots input 
    2. RALO involvement is an asset   
- On-the-ground, workable and well-defined actions 
- At-Large uses electronic tools to bring its members' different backgrounds and expereinces experiences to bear on planning process

Weaknesses                                                                   

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

Opportunities                                                                      

- Strengthen maturity of At-Large by improving processes
- Use At-Large as a powerful communication channel
- At-Large operating plan could be a useful step in preparing an accurate budget
- At-Large's abilities and reach could be used to convey ICANN's message locally
- At-Large could incorporate public participation into ICANN's operarional planning
- At-Large comments, as result of consensus-based process, should be considered by ICANN Board and staff 
- Actions proposed by At-Large should be considered by ICANN

Wiki Markup
\[What kinds of actions? Pt. right above refers to policy advice\]
(OCL: others might wish to comment on this.)

Threats                                                                            

- Lack of means

Wiki Markup
\[Unclear.  "Means"?  Suggestion:  Lack of funding \-\- and then state what it risks\]

- Less operational exposure 
Wiki Markup
\[Could do what?  Or this could result from what?\]

- Lack of volunteers would limit operational planning and capabilities

...