Instructions:
1. You must be logged in to the Community Wiki with a valid Username and Password in order to complete forms within CROP.
2. Your organization must first complete and get approval for the Outreach Strategic Plan before any CROP trip could be processed.
3. To fill out the the form, click
(top of the screen).4. Answer each of the questions that appears within the form. Use the scroll bar (right) to reveal all contents. Click here to read the full instructions
Strategy Status |
|
Person Completing Form: | Chantelle Doerksen |
---|
FY19 Outreach Strategy | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Outreach Goals: | The Commercial and Business Users' Constituency [a.k.a. the ICANN GNSO Business Constituency (BC)] FY19 Outreach Strategy is based on fulfilling the BC’s mission [1] as described in the BC’s approved Charter. The BC Outreach goals support the engagement of business users in gTLD policy development and in ICANN’s overall governance. Further, it also supports the ongoing enhancement of multi-stakeholder engagement in relevant activities to ensure ICANN’s continued success as the coordinator of the unique indicators of the Internet as provided for in ICANN’s bylaws. The BC Outreach Strategy aligns with ICANN strategic objectives. | ||||||||||||||||||||
Strategies: | The BC has a broad Outreach Strategy that is focused on growing BC visibility and engagement in ICANN meetings and in selected and related events where business executives and others from the business user communities participate, as well as governments who may influence ICANN’s stability. The broad BC Outreach strategy is described in this document, with a specific segment focused on the use of ICANN’s Community Regional Outreach Program (CROP) funds and includes using part of its own membership funds, and other special funds [some of which are supported by ICANN funding] in collaboration with ICANN supported activities to increase engagement of business user companies and to support the broader BC Outreach Strategy. The BC Outreach activities will draw on ICANN FY19 CROP travel support for three travelers as defined in the CROP, overseen by the BC Outreach committee and approved by the BC ExCom [and consistent with CROP guidelines] and in keeping with the BC’s regional and other focus priorities. CROP events will benefit from full support from the BC Outreach Committee and always include BC membership materials suited to the event. Additional engagement and support by the BC in additional support to include a senior leader from each region from its own funds and engagement is included below, which augments and builds on the CROP funded engagement, a critical contributor to ensure broader engagement in the least represented sub-regions for business users in ICANN. Continue and enhance the reporting of all BC funded travelers attending Outreach events relying on the required reporting of the CROP program as a role model for all BC funded engagements, but where needed, include additional BC requirements. Enhanced visibility of BC’s Outreach engagement via the BC Newsletter on an occasional basis – e.g. BC newsletter for ICANN62 focused on Outreach events from 2017-2018. Previous Newsletters have also included Outreach stories supported by CROP. CROP funds will support travelers to events that are primarily focused on companies— both large and small—that fit the definition of a Business User. The BC presence and participation at events will be further reinforced by materials and presentations developed within the BC’s Outreach Committee and the designated CROP BC traveler. Such materials will be shared via the full BC list, as part of the Meeting Outcome Report required from all funded BC outreach events. Normally, CROP will primarily support the engagement in or be associated with external to ICANN events where business users can be easily reached, rather than creating unique events, in order to avoid additional organizing costs, other than those that CROP covers. The Outreach Committee will evaluate funding requests from BC members to attend an event, and specifically evaluate the effectiveness of the use of CROP funds to augment BC participation, with any additional expenditures outside the CROP budget to receive final approval from the BC ExCom. Such expenditures may include printing of brochures or fact sheets for use, which will not be covered by CROP. Responsibility for making recommendations for use of funding lies with the BC Outreach Committee, with budgetary review by the BC Financial Committee and final approval resting with the BC ExCom. Selected events might require sponsorship or registration fees. For CROP and other BC supported funding, priority for funding will be given to BC experienced members who have a speaking role at an approved event, where the speaker has the ability to directly promote the work of the BC (versus speaking on another topic). Where a unique relationship exists between a BC member and an organization [including ICANN regional teams] organizing an outside event that has high visibility within a region/sub-region with low BC membership, CROP can be considered to bring a BC member as a special “recruiter”. Given the limited funding from CROP, priority will be given to proposals that are well documented regarding high opportunity for new BC member(s). As an exception and due to the limitations of CROP funding for 2019, CROP funding could be used to support participation and the active engagement of one BC member who could not otherwise attend an ICANN meeting or another major ICANN-related event where a BC Outreach event is organized, and a particular BC member brings unique contacts in that region. In these cases, the member’s engagement must augment the legitimacy of the BC’s role and effectiveness of BC outreach within that region. This would be an exception and would be assessed on a case-by-case basis, looking at the needs of the BC and the parameters of the CROP program. Use of CROP would require a specially designated role for the funded BC member in BC outreach activities, noting that CROP guidelines must be adhered to. Any additional supporting funding from the BC for the Outreach activities will follow the usual Outreach Committee and ExCom approval processes. A written proposal, and documented plans are required for consideration of CROP, as well as any BC funding for Outreach and Awareness/Recruitment. A written report that assesses the effectiveness of a particular event, direct and indirect outcomes is required. The development of specific activities and events that utilize the BC’s presence and membership within at least three (3) developing country regions will be a priority for CROP 2019 for the BC. At this point, continued outreach in Africa, Asia/Oceania; Caribbean Islands/Latin America, Middle East and Eastern Europe and Central Asia are under discussion, given the low BC membership in such regions and BC member interest in engagement. Given the limitations of CROP funding to only 3 slots, priority will be developed by the Outreach Committee, but take a wholistic approach, rather than a first come basis. Approval of travel to these events is based on proposals submitted at least 2 months prior to the event, as CROP deadlines require six weeks prior to an event, at minimum. The 2- month requirement provides the BC Outreach committee a two-week period to review a travel request and arrive at a decision. While exceptions may occur, every effort by those proposing a CROP supported event will be asked to justify any late submissions to the Outreach Committee. Similar processes are required to apply for extraordinary budgetary support from the BC from its own financial resources and will be based on BC engagement supportive of the BC’s Outreach Strategy. An example is the BC’s use of small grants to support engagement of 4 BC members in the IGF2017. This initiative required engagement in an event that was highly supported by ICANN, and also presented multiple opportunities for the [very partially] funded BC members to have high profile engagement, not only with businesses, but also governments and IGOs. Update the two page “mini brief” on an annual basis describing the BC, its role at ICANN, and the benefits of membership, to be used at various events. The Fact Sheet for FY18 is available on the BC website, and will be updated annually. Note: All BC members are encouraged to use the Fact Sheet in any relevant events that they attend. All BC newsletters and fact sheets can be found at http://www.bizconst.org/newsletter. Completion and publication online of the “Meet the BC” document which provides short profiles of the BC members. Development of “mini-testimonials” from BC members who volunteer to provide such statements – 100-150 words and head shots, to be posted on the BC website with permission of the BC member – goal 1-2 per ICANN Region. Continued use of collaborative engagement with the VP of Business Engagement and per meeting, relevant ICANN regional VPs/staff for targeted outreach to registered attendees [and local associations/businesses] at ICANN meetings from the private sector who are not already members of the BC, through organizing occasional specialized events at ICANN meetings with a goal of holding or joining ICANN’s Business Outreach Activities with a goal of at least 1-2 such events each year. [e.g. example of highly successful outreach during South Africa organized by Affects in collaboration with ICANN business Engagement VP and again at ICANN62. The BC will continue to examine how to establish partners/mentors for new business user attendees within the BC that identify a topic they would be willing to “mentor” a new BC candidate/member on – still under development within the BC: Outreach Committee/+ BC members will examine how to further advance benefit of Fellowship and NextGen programs to the BC - 2019-2020 period to work with ICANN staff to increase recruitment from private sector into these programs, including members from small and mid-sized businesses from developing countries, as well as academics focused on business management; etc. Coordinate with ICANN on any event they are doing already to increase the visibility of the BC and make face to face contact with attending private sector members, while recognizing that the attendance of local businesses can be very challenging, due to their own business priorities that compete with a multi-day ICANN meeting. Establish a standard invitation to be sent to the local business associations in the relevant country/region, at least two (2) months before an ICANN meeting, when contacts are nominated by BC members, and then followed up with a more detailed invitation, when the ICANN agenda is available, and social events are identified. Engage with the ICANN Engagement VP for Business as a priority engagement and regional V.P. teams regarding any relevant business groups they are engaging with. For ICANN meetings, where possible, the BC will include one new senior business leader from the region/with regional affiliation as part of BC Senior Leadership Engagement. Review the Fellows who self-identify as businesses, to engage interest and inclusion in any relevant BC events/engage with Fellowship staff to determine how best to reach out to self-identified business attendees. BC Outreach strategy is developed and administered by the BC Outreach Committee with the support of the BC Executive Committee and ICANN staff. The Outreach Committee meets virtually two to three times between each ICANN Meeting, and strives to meet face-to-face during ICANN meetings with the BC membership in attendance. In addition, updates are provided to the full BC membership via the virtual BC working calls. Events and travel support requests are considered and recommendations made by the Outreach Committee. Reports of all activities are provided to the full BC membership. The Outreach Committee will notify the BC Executive Committee of any requested additional expenditures, whether from BC or ICANN funding sources, at least four weeks prior to the disbursement date. These planned expenditures are deemed as approved unless the ExCom raises questions or objections within one week of notification. | ||||||||||||||||||||
Expected Activities and Outcomes: | Through our outreach efforts, the BC expects to: | ||||||||||||||||||||
Other Details: | Sn Objectives Outputs Expected Results Key Performance Indicators 1 To create awareness about BC, its works and ICANN in low membership regions. Conduct of Outreach events in collaboration with stakeholders in Africa, Asia & Latin America. Continuous improvement of URL (bizconst.org). Factsheets Increased awareness of BC & ICANN. Increased interest in the DNS industry. Speaking opportunities for BC officials @ (Business) events Improved website completed. Completion of one or two pager/ "mini brief”, to be available at Regional and National Internet Governance Forums in appropriate languages and at IGF and ICANN booths. Increased BC membership from developing countries that lack BC presence. Retain recently recruited members via the Outreach Program activities. To realize BC’s mission by diversifying and growing its membership base thereby enriching its long-term policy development efforts and engagement in ICANN governance activities and at the same time addressing volunteer burn- out phenomenon. Outreach activities organized by BC/other organizations, or ICANN or special inclusion of participants during ICANN and directly related events in collaboration with stakeholders in Africa, Asia/Oceania and Central Asia/South Asia/MENA/Caribbean/Latin America. Individual member one-on-one outreach with business associates. More members of BC from the target regions Growth of BC membership by 7-10 members. Effective BC participation in all relevant activities at ICANN, including policy and ICANN governance activities Number of business stakeholders reached. To advance the bottom-up multi-stakeholder model of ICANN. Monthly working calls of the Outreach Committee and identification of relevant events for Outreach Effective participation in ICANN policy development process and ICANN governance discussions, including Budget, ICANN Strategic Plan, etc. Publication of policy positions via URL. Presentations at key Trade /Professional Association events provided by BC Outreach Committee Members and other BC members willing to engage with their trade associations. Submission of blogs about ICANN by BC Members/regarding relevant issues/topics that natter to business users. Increased uptake of the M/S model across entities. Awareness of BC members of various events related to ICANN’s MS model Growth in membership. Effective BC participation in relevant WGs. New members involvement in BC meetings and broader ICANN governance activities. [1] The mission of the Business Constituency is to ensure that ICANN policy positions are consistent with the development of an Internet that: [2] Evolve and further globalize ICANN Date Submitted: August 15, 2018 | ||||||||||||||||||||
Date Submitted: | 20-Aug-2018 |
Note: To be completed by a Program Coordinator (PC) designated by this organization/structure.
Acknowledgements | Confirmed? | Who Confirmed? | Date of Confirmation | Notes |
---|---|---|---|---|
The detailed Outreach Strategic Plan has been properly completed per CROP requirements. | Yes | Marilyn Cade | 15-Aug-2018 | Submitted by Marilyn Cade to CROP staff, on behalf of BC Leadership. Uploaded by Chantelle Doerksen |
The ICANN Organization / Structure's leadership has authorized this Outreach Strategic Plan. | Yes | Marilyn Cade | 15-Aug-2018 | Submitted by Marilyn Cade to CROP staff, on behalf of BC Leadership. Uploaded by Chantelle Doerksen |
The Outreach Strategic Plan has been concurred by the Stakeholder Engagement V.P. |
|
|
|
|
=============== | =========== | ============================== |
CROP Outreach Strategic Plan Template (June 2018)