Versions Compared

Old Version 22

changes.mady.by.user Olivier Crepin-Leblond

Saved on

compared with

New Version 23

changes.mady.by.user Olivier Crepin-Leblond

Saved on

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 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 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.) (OCL: For example, actions like a proposal for a "Second At Large Summit"; "RALO GA"; etc.)

Threats                                                                            

- Lack of means

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

  - funding of operations
  - staff headcount
  - translation services
  - Web services
  - conference call services
  - other daily logistics
  - etc.
- Less operational exposure 
Wiki Markup
\[Could do what?  Or this could result from what?\]
  (OCL: this is a result from lack of means / possible result: significant reduction in volunteer involvement)
- Lack of volunteers would limit operational planning and capabilities

...

Strengths                                                                            

- Membership diversity can bring talent
- In-house knowledge of Budgeting requirements within At-Large

Wiki Markup
\[Budgeting requirements?\]
  (OCL: yes - added)
- Improved consultation among the RALOs and their representatives on the committee ALAC
Wiki Markup
\[What committee?  ALAC's Subcommittee on Budget and Finance?\]
  (OCL: replaced "committee" with ALAC. Not only the ALAC Subcommittee on Budget & finance since some regions might not be represented on this committee)
- Cost-effective actions
- Experience sharing among RALOs  
- A bottom-up budget structure for At-Large                                                                     

Weaknesses                                                                   

- Lack of established feedback loop from ICANN
- Communication problems ICANN finance
- No possibility of ROI figure - "investing in At Large is like investing in R&D"
- ICANN currently only source of funds for At Large
- Lack of clear funding schedule/calendar with regards to face to face general assemblies introduces uncertainty
- We need to improve our interaction with the staff during the budget planning process.

Opportunities                                                                        
 
- ALAC/At-Large could provide information regarding At-Large budgetary needs in a more timely manner and in the required format

Threats                                                                            

- Limiting ALAC's budget could:
    1.  Directly and severely affect outreach capability
    2.  Allow for fewer or no face-to-face meetings, thus triggering ALSes to abandon At-Large and, thus, potentially ending At-Large's usefulness

Wiki Markup
\[(a) Review rewording; (b) by face-to-face meetings, do you mean GAs, ICANN meetings, etc.?\]

2. Allow for fewer or no face-to-face meetings (including but not limited to GAs, ICANN meetings, Summits, RALO meetings etc.)
  - possible consequence could be ALS abandon of At Large - and this would reduce At Large's legitimacy