[ICANN Academy WG] Draft outline for a Pilot Leadership Training Programme in Toronto

[Gomes, Chuck]

Very well said Rumy.  Thanks.

Chuck

> -----Original Message-----
> From: at-large-icann-academy-ad-hoc-wg-bounces at atlarge-lists.icann.org
> [mailto:at-large-icann-academy-ad-hoc-wg-bounces at atlarge-
> lists.icann.org] On Behalf Of Rumy Kanis
> Sent: Friday, August 24, 2012 3:29 AM
> To: sandra hoferichter; Filiz Yilmaz
> Cc: at-large-icann-academy-ad-hoc-wg at icann.org
> Subject: Re: [ICANN Academy WG] Draft outline for a Pilot Leadership
> Training Programme in Toronto
> 
> Hello,
> 
> I noticed there is some discussion on content already, I won't be
> commenting on actual content. However, I hope that my points will make
> the content discussion a bit easier.
> 
> My first reaction upon reading this document is that this does not read
> like a training programme, but more like a mini conference. Nothing
> wrong with that, and could still be very educational, but this is not a
> training programme.
> 
> For this to be a training programme, 2 crucial points are missing.
> 1. A clear definition of the target audience.
> 2. Learning goals
> 
> 1. A clear definition of the target audience.
> Roles and names are not enough.
> What are their needs. What are their prerequisites? What should or will
> they know before attending the programme? And what should or will they
> know afterwards?
> I know the target audience is quite varied in terms of prior knowledge,
> so I can see this is not a simple task, however, it is still important
> to try and determine (and document) what it is they need to know after
> the programme, and why. Which brings me to the next point:
> 
> 2. Learning goals
> I am missing the learning goals! In the design of any educational
> programme/tool, a crucial first step is defining the learning goals.
> Without these, it becomes very hard, if not impossible, to write a
> successful programme. Since you don't really know which topics to cover
> into what depth and why, and with what result. Without these, you can't
> prioritise between topics (already apparent from the discussions on the
> list). You can't really select trainers, methods and materials either.
> You won't be able to assess afterwards if the programme was successful,
> because you can't measure whether the goals were accomplished. And
> finally, the participants will not know what to expect.
> 
> My suggestion would be to start by establishing overall learning goals.
> After that, more specific learning goals should be written. Per day,
> and per section.
> 
> In the case of this programme, clear learning goals are even more
> important, because you will be making use of guest speakers. Each
> speaker needs to know the overall goal of the programme, and the
> specific learning goal for their section, or else they won't know what
> exactly to cover in their material. Without clear explicit learning
> goals per section, you also run the risk that sections end up
> overlapping or covering double content. And, as I mentioned before, you
> won't be able to measure whether the particular section was successful.
> 
> A learning goal should always be expressed from the point of view of
> the learner/participant.
> 
> Let's take the second session on the first day as an example:
> 9:45-11:15 ICANN Multi-stakeholder Environment (I)
> 
> A properly defined learning goal would be something like this:
> After this section, the participants will be able to distinguish
> between the various stakeholders. They will know the difference between
> each of them, and their functions and tasks. (just an example, I'm sure
> you can come up with a better description). A section can have multiple
> learning goals, btw.
> 
> Another example, on the second day:
> 9:00-10:15 Technical Functions
> *	How DNS works
> *	IANA Function and how it fits in the ICANN picture
> *	Root Zone management
> *	How DNSSEC works
> 
> I may be wrong, but I don't think it's possible to teach someone "how
> DNS works" and "how DNSSEC works" in an hour. We can't even do it in a
> full day. Believe me, we've tried ;-).
> I would rename that to "brief introduction to DNS" and "brief
> introduction to DNSSEC", and think about the specific goal of the
> "technical functions" section. Do the participants just need to be
> aware of these functions, or do they need to know more than that? What
> do you want to achieve with the section?
> 
> And so forth for each section...
> 
> Once the learning goals are established, it's a lot easier to decide
> which topics are relevant for the programme, and into what depth they
> should be covered.
> 
> Hope this helps.
> 
> Some other important things to take into consideration for a successful
> training programme, not as part of the curriculum necessarily:
> - student notes
> - instructor notes
> - maintenance of material
> - evaluation
> - quality control
> 
> Kind regards,
> Rumy
> 
> 
> --
> Rumy Kanis
> Training Services Manager
> RIPE NCC
> 
> Follow us on Twitter for the fastest and latest RIPE NCC Training news!
> @TrainingRIPENCC
> 
> 
> On Aug 22, 2012, at 3:22 PM, sandra hoferichter wrote:
> 
> > Dear WG members,
> >
> > after a summer break Filiz and I started working on a draft outline
> for the pilot project in Toronto. Based on the FY13 Operating Plan and
> Budget and the results of this working group so far, we present you
> herewith a draft programme inviting you to comment.
> >
> > While drafting this outline we already discussed various options, how
> to optimise it and what should be the focus. We expect that some of
> these options will be raised in this mailing list and we are happy to
> answer any questions and remain open for ideas, as long as they fit in
> the given framework.
> >
> > In the FY13 Operating Plan and Budget document it is stated:
> >
> > <<<"The ICANN-Academy concept is still being developed and reviewed
> > within the SO-AC groups and further consensus is ongoing though a
> > process led by ALAC / At-Large. While this process is ongoing, in
> > early anticipation of the direction of the effort, a staff pilot
> > project will be focused on the executive training of new SO-AC
> leaders
> > on ICANN organisations, policymaking and related activities. The
> pilot
> > would include usage of online tools where possible and an orientation
> > session in Toronto. This pilot project should be seen as a first step
> > in testing the overall concept and providing a basis for a future
> > training program as well as experience to build on for future
> > improvements if deemed necessary. ">>>
> >
> > Furthermore this draft concept is based on the proposed curriculum.
> (see:https://community.icann.org/download/attachments/31168402/Draft+In
> itial+Proposal+%28as+of+18.02.2012%29.pdf?version=1&modificationDate=13
> 29954389000 ).
> >
> > The comment phase is open until: 31 August 2012 Nominations for
> > participants should be sent to filiz.yilmaz at icann.org until 1
> > September 2012
> >
> > We are aware, that the discussion in the expanded WG is just about to
> start and this outline will not cover all the needs and ideas, however
> this pilot project should be see as a first step to build on an
> inclusive capacity building programme within ICANN. The WG is should
> review the pilot project critically and develop strategies and
> recommendations for future projects. To get a feedback from the
> participants this WG is asked to develop a survey, to be filled in by
> every participant in this programme.
> >
> > We are looking forward to your comments.
> >
> > Sandra and Filiz
> >
> >
> >
> <Toronto_draft_outline_20120822.pdf>__________________________________
> > _____________ at-large-icann-academy-ad-hoc-wg mailing list
> > at-large-icann-academy-ad-hoc-wg at atlarge-lists.icann.org
> > https://mm.icann.org/mailman/listinfo/at-large-icann-academy-ad-hoc-
> wg
> 
> 
> 
> 
> _______________________________________________
> at-large-icann-academy-ad-hoc-wg mailing list at-large-icann-academy-
> ad-hoc-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/at-large-icann-academy-ad-hoc-wg