Issue 1 Dashboard and Progress Chart

Final Proposal as approved by the Board

Staff, under the direction of At-Large leadership, has already begun to rework the website and Wiki to ensure that our “Policy Advice” pages are accurate and understandable. This will continue as volunteer and staff resources allow. We will also ensure that as documents are published, the classification of the document is clear.

Prioritization

1:1:1 (Low resource needs : Low risk : 1st priority)

ARIWG comments

This is one of the recognised issues that the Community, ALAC and At-Large had already noted the cause of and had prior to the At-Large Review 2  Final At-Large Review Recommendations Feasibility Assessment & Implementation Plan (FAIP) and ARI started to remedy.  Specifically, as proposed and approved by the Board, At-Large staff, under the direction of At-Large leadership, has already begun to rework the website and Wiki to ensure that our “Policy Advice” pages are accurate and understandable. Further that recently and ongoing ALAC Statements, Public Comments and Advice are clearly classified and that the classification of each type is clear. Fundamentally, this issue is meant to address some confusion inherent in the current presentation of the ALAC document database. Implementation on this matter had  already begun prior to ARIWG activity and is part of the ALAC’s continuous improvement process. Work will continue throughout 2019 and 2020 before formal review in 2021. There are two main aspects in this issue to address:

Fundamentally, this issue is meant to address some confusion inherent in the current presentation of the ALAC document database. There are two main issues to address:

1. Confusion about the type of document (i.e.,  “Advice” vs “Comment”)
2. The “End user” justification for intervention.

Accordingly, At-Large staff together with At-Large leadership, will categorize the existing documents (as advice, public comment, correspondence, etc.) in a more granular fashion and provided enhanced tools with which to filter search results based on these categories.  Staff have also created a new field in the database for “End User Issue” and At-Large leadership now populates this field both in current documents and those generated going forward. Additional staff resources are needed for any ongoing work deemed necessary. Initially around 40-50 hours of staff time between January 2019 through to June 2019 has been utilized to improve clarity of wiki and web pages.

When additional staffing resources are made available under Issue 3 Implementation, policy advice development work and communication will be a primary focus of existing staff resource time freed up from other activities. Specifically:

• Differentiate between advice and comments, potentially other categories (i.e. correspondence).
• Develop communication of revisions to the pages to end users.

Status of improvement effort / staff lead

Already underway, continuous improvement to continue / Heidi Ullrich; Evin Erdoğdu

Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation

N/A

Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?

ICANN Staff in conjunction with ALAC/At-Large Leadership

Anticipated resource requirements (FTEs, tools)

• Initially up to 40-50 hours of staff time between Jan 2019 through to June 2019 to improve clarity of wiki and web pages.

• When additional staffing resources are made available under Issue 3 Implementation, policy advice development work and communication will be a primary focus of existing staff resource time freed up from other activities.

• Differentiate between advice and comments, potentially other categories (i.e. correspondence).

• Develop communication of revisions to the pages to end users

Expected budget implications

Initially no additional, beyond already allocated, resources to At-Large.

However, as noted in Issue 3, additional staff resources are needed for any ongoing work deemed necessary.

Proposed implementation steps:

1. Finalize categorization of previous statements (comments, advice, correspondence, etc.)

2. Rename Sub Type to Document Type

3. Populate list options for document type based on document categorization exercise

4. Populate the “End User Interest” (EUI) field for previous comments

5. Begin logging EUI going forward.

Metrics

1. Clear and Accurate Distinction between statement types.

2. Statements filterable by type

3. Populated EUI fields.

How long will it take to implement this plan?

Implementation on this matter had already begun prior to ARIWG activity and is part of the ALACs continuous improvement process. Work will continue throughout 2019 and 2020 before formal review in 2021.

Link to presentation (PDF) of recent activity updates

See WS2 Dashboard for example(s).

Report due to the Board - 23 June

Report drafts should be ready by May 23 with sub-tasks completed

Two goals to address under this issue: 
(1) Confusion about the type of document (ie  “Advice” vs “Comment”)
Work in progress: Historic ALAC Advice & Comments (found on At-Large Policy Summary).
Completed: New Executive Summaries: ALAC Policy Comments & Advice page differentiates between ALAC comment, advice and correspondence, with tags and posts since ICANN60.
Completed: ALAC Advice & Comments marked accordingly since ICANN60 on At-Large website (found on At-Large Policy Summary).
(2) The “End user” justification for intervention
Work in progress: ALAC Hot Policy Topics Document (Jonathan Zuck & Joanna Kulesza to present draft at ICANN65)
Completed: New (ongoing) system of ICANN meeting "Talking Points" for At-Large community members (started at ICANN64), and At-Large Policy Workshop(s) (started at ICANN64).
Completed: At-Large Consolidated Policy Working Group (CPWG) presentation format for penholders, weekly meetings.

• EE has requested ICANN product development team to update At-Large website with "sub-type" filters.
• EE/HU to follow up with ICANN Board Ops team on historic ALAC Advice/Statements/Correspondence.

AG to advise JZ/EE on historical ALAC policy statements, to categorize as comments vs advice.

Implementation steps:

1. Finalize categorization of previous statements (comments, advice, correspondence, etc.)

2. Rename Sub Type to Document Type

3. Populate list options for document type based on document categorization exercise

4. Populate the “End User Interest” (EUI) field for previous comments

5. Begin logging EUI going forward.

Metrics

1. Clear and Accurate Distinction between statement types.

2. Statements filterable by type

3. Populated EUI fields.