[Gnso-rpm-practitioner] REMINDER FOR REVIEW: Draft Questions for Practitioners

[Greg Shatan]

I have a conflict today and will only be able to join halfway through, if
at all.  As a member of the small group, I am satisfied with the outcome
being presented today.  There may be a few questions where it could be
better to have “Somewhat Agree” and “Somewhat Disagree” available as
choices (in addition to “Strongly...”).

Nitpick: In 7 there’s a comma after yes that should be deleted.

Talk sooner or later,

Greg

On Wed, Apr 11, 2018 at 10:30 AM Julie Hedlund <julie.hedlund at icann.org>
wrote:

> Dear all,
>
>
>
> Further to the message below, this is a reminder to review the attached
> draft questions that we will discuss on today’s call.  Here also is a
> suggested agenda:
>
>
>
>    1. Review Agenda
>    2. Review of draft questions for practitioners
>    3. Review list of practitioners/identify contacts
>    4. Next steps: survey and data analysis
>    5. AOB
>
>
>
> Best regards,
>
> Julie
>
>
>
> *From: *Gnso-rpm-practitioner <gnso-rpm-practitioner-bounces at icann.org>
> on behalf of Julie Hedlund <julie.hedlund at icann.org>
> *Date: *Monday, April 9, 2018 at 1:23 PM
> *To: *"gnso-rpm-practitioner at icann.org" <gnso-rpm-practitioner at icann.org>
> *Subject: *[Gnso-rpm-practitioner] FOR REVIEW: Draft Questions for
> Practitioners
>
>
>
> Dear all,
>
>
>
> Per the notes below from the meeting on 28 March, a small group of
> volunteer editors was established to prioritize, consolidate, and edit the
> questions for practitioners.  Accordingly, please see attached in Word and
> PDF the draft of the questions for your review and discussion at our next
> Sub Team call on Wednesday, 11 April at 1700 UTC.
>
>
>
> The volunteers advise the Sub Team that this new version takes into
> account comments from ICANN61 and the last working group call.   The
> volunteers’ work streamlined and restructured the original rough, free flow
> of questions into a more user friendly presentation to encourage response
> and allow the Sub Team to obtain useful data.  Questions were structured to
> provide a multiple choice answer format, and where it appeared necessary
> (or advisable), additional supporting information is requested to provide
> context for the answer.
>
>
>
> It will be helpful if all Sub Team members could review the draft
> questions in advance of Wednesday’s call.  If you have comments, suggested
> edits, and questions you are encouraged to post these to the list in
> advance of the call and staff will gather them for Wednesday’s discussion.
>
>
>
> Best,
>
> Julie
>
> Julie Hedlund, Policy Director
>
>
>
> *From: *Gnso-rpm-practitioner <gnso-rpm-practitioner-bounces at icann.org>
> on behalf of Julie Hedlund <julie.hedlund at icann.org>
> *Date: *Wednesday, March 28, 2018 at 2:20 PM
> *To: *"gnso-rpm-practitioner at icann.org" <gnso-rpm-practitioner at icann.org>
> *Subject: *[Gnso-rpm-practitioner] Action & Notes: RPM Sub Team for URS
> Practitioners call on Wednesday, 28 March 2018 18:00 UTC
>
>
>
> Dear all,
>
>
>
> Below are the action items and notes staff captured from the RPM Sub Team
> for URS Practitioners meeting today (28 March 2018).  The notes from the
> call are posted to the Sub Team wiki space, together with the call recording and
> attendance records.  See:
> https://community.icann.org/display/RARPMRIAGPWG/2018-02-28+Sub+Team+for+URS+Practitioners.
>
>
>
>
> Best Regards,
>
> Julie
>
> Julie Hedlund, Policy Director
>
>
>
> *Action Items:*
>
>
>
>    1. Staff will provide a link to a Google Doc for Group of Editors
>    (Georges, Scott, Petter, and Jason) to prioritize, consolidate, and edits
>    the questions.  DONE – See:
>    https://docs.google.com/document/d/1sobXBGnVZV9zKazKvq5Nf2QtDo4-u1hmpieh4xB_fe8/edit?usp=sharing
>    2. The Group of Editors will provide the revised list of questions to
>    the full Sub Team by Monday, 09 April for review and discussion on the all
>    on 11 April.  The Group of Editors will use the meeting slot on Wednesday,
>    04 April at 1700 UTC.
>
>
>
> *Notes:*
>
>
>
> 1. Questions for Practitioners:
>
>
>
> -- Constructive suggestions from the full WG at ICANN61.
>
> -- Get the questions into better organization.
>
> -- Edit the tone of the questions
>
> -- Reorganize the questions – perhaps have some more substantive questions
> and sub questions.
>
> -- Get the questions into shape and then consider how to reduce the volume.
>
> -- What is the goal here and how do we achieve it?  Open-ended questions
> may not get us anywhere.
>
> -- Include a final open comment box.
>
> -- How to manage the edits – look for volunteers for each section?  What
> are we trying to get?  Try to get down to 10 manageable topics and
> questions related to them.  Also, figure out what kind of answer we are
> looking for.  Use click boxes to reduce questions.
>
> -- How to prioritize and edit the questions?  Get volunteers to edit:
> Scott Austin, Georges Nahitchevansky, Petter Rindforth, and Jason
> Schaeffer; the goal is for the group of editors to present the revised
> draft questions to the Practitioners Sub Team by April 9th.
>
>
>
> Questions from Documents Sub Team:
>
>
>
> -- Note that there also are the suggested questions from the Documents Sub
> Team.
>
> -- How do we synthesize these?
>
> -- They all seem to seek anecdotal responses.  Seems like a set of
> suggestions.  Questions need to be more precise.
>
> -- Look for gaps between what we cover and they have suggested.
>
> -- Once we edit our questions it may be easier to synthesize them with the
> Documents Sub Team questions.
>
>
>
> 2. List of Practitioners: How many do we contact?  Do we have different
> questions for different practitioners and level of experience?
>
>
> _______________________________________________
> Gnso-rpm-practitioner mailing list
> Gnso-rpm-practitioner at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rpm-practitioner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rpm-practitioner/attachments/20180411/2afb622a/attachment.html>