UPDATED RDRS Impressions Doc responsibilities
Dear Members of the Standing Committee, We hope this message finds you well. As we continue our efforts to streamline our processes and achieve our strategic goals, we would like to provide you with clear instructions on how to effectively use the newly-formatted Impressions Document<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ6...>. Your proactive engagement with this document is crucial to our collective success. To make our meetings more productive and aligned with our strategic goals, it is imperative that each member thoroughly reviews and updates their change request(s) in the Impressions Document before the meetings. This preparation will allow us to move discussions forward efficiently and focus on decision-making rather than catching up on updates. Going forward, we will only discuss change requests that have SC owners during meetings. For items that do have owners but lack an SC agreement to proceed and an SC-designated priority level, we will use the meeting time to agree on these two items specifically. In order to move forward in this way, we request the following from the Standing Committee: * Each SC member is asked to go into the impressions document and review the items that are not currently owned by a SC member to see if they believe the item is important and would like to own it, noting that the SC will only discuss OWNED items during the meeting. Support staff will delete change requests without a dedicated SC owner after the next SC meeting (29 July). An SC Owner is responsible for the overall accuracy and relevance of the change request. SC members can include change requests outside the SC but need to agree to be the SC owner for them. This includes the following responsibilities: * For the items that are owned, SC owner is asked to review LoE notes from ICANN and Comments in advance of the meeting to see if ICANN org has added additional questions or comments. * SC owner should either be prepared to provide additional info during the meeting or additional information in Comments if unable to attend meeting. ICANN org will be unable to provide an LoE until outstanding questions are answered. * If there are follow-up questions from ICANN org regarding an agreed to item, the SC owner will also be ICANN staff's point person for the questions. The owner may update the full SC regarding follow-up discussions, where needed. * As the group moves through outstanding (and owned) suggestions during the meetings, Support Staff will take an action to update the sheet during the meeting, where possible or shortly thereafter. For example, if the SC agrees to a Priority 1, Support Staff will update the SC Agreed Priority ranking in the sheet. The SC Owner will be responsible for reviewing Support Staff's updates and confirm accuracy by COB Fridays following SC meetings. * When entering new change requests and when discussing to move ahead with change requests, please bear in mind the success criteria as confirmed by the ICANN Board to GNSO Council (Nov 2023). In other words, how will this specific change request meet the strategic goals of the RDRS SC? Your cooperation and commitment to this process are greatly appreciated. If you have any questions or need further clarification on how to use the document, please do not hesitate to reach out. Thank you for your continued dedication to our collective success. Best regards, Feodora and Caitlin
participants (1)
-
Caitlin Tubergen