The PDP3.0 call is scheduled for Friday, 25 October 2019 at 00:00 UTC for 60 minutes.
To check your time zone conversion: https://tinyurl.com/y28stlxd
PROPOSED AGENDA
The GNSO Council comments in the Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model provide very helpful information and background concerning the PDP 3.0 Implementation work. For tomorrow's call, I wanted to let you know that I am primarily interested in understanding the following:
- the work of the small team of Councilors; how it was organized, structured and resourced
- how proposed documents, processes and tools were developed
- how implementation documents were developed and the implementation process that follows
- greater detail regarding work on Precision in Scoping the Work, Prioritization and Consensus in PDP 3.0
The PDP 3.0 Implementation work holds the potential to be instructive for improvements in the functioning of ICANN's MSM beyond GNSO PDPs and non PDP work. I appreciate you willingness to share your experience with me.
BACKGROUND DOCUMENTS
PARTICIPATION
Notes/ Action Items
Action Items
- None
Notes
- Interested in understanding the PDP 3.0 implementation process.
- PDP 3.0 may help address some of items in the MSM workplan. Can be a model to address other areas of work in ICANN.
- Rafik explained the background/process how the 14 improvements were developed, and how the small team carried out the work.
- What resources are needed to develop the implementation documents and proposed procedures? Mostly inhouse as a collaborative effort between the small team and staff (e.g., project management related improvements by Berry). Expertise resides within ICANN (e.g., staff + community). One improvement is outsourced to external party (Improvement #4).
- Each improvement has a Council member as the lead. Also reached out to other leaders in the GNSO (e.g., Heather) and liaisons to seek input.
- Nothing in MSM project is designed to disturb in any way of the PDP 3.0 implementation.
- The MSM workplan will be presented in Montreal and be part of the 5-year operating plan. Not Brian’s responsibility to figure out the cost.
- Curious about the cost of implementing PDP 3.0 improvements. Not counting internal resources, only additional cost is the $30K ABR allocation for Improvement #4 (consensus playbook). However, human resources (e.g., volunteers + staff) are the biggest item and hard to quantify.
- Approval for the ABR for #4 is contingent upon being used by the wider community. ABR process does not guarantee that all requests will be granted.
- Don’t underestimate the time needed to develop the implementation documents. Weekly call is quite a commitment of the community, not to mention the number of hours staff have put into meeting preparation and document development. PDP 3.0 is close to the heart of the GNSO support team; the more efficient the process is the better for everyone involved.
- The MSM workplan will include: 1) who will be tasked to carry out certain work, 2) timeline, 3) statement of resources, etc. None of the work will disturb any of the work that the GNSO is doing with PDP 3.0 implementation. Let GNSO continue the work, and the ICANN community will observe the implementation and impact. Other SOs/ACs can take the solution and use the outcome of the GNSO PDP 3.0 as a guide.
