Attendees: Cheryl Langdon-Orr, Olivier Crepin Leblond, Dev Anand Teelucksingh, Sala Tamanikaiwaimaro, Natalia Enciso, Beau Brendler, Yrjo Lansipuro
Apology: Tijani Ben Jemaa
Staff: Seth Greene, Matt Ashtiani, GIsella Gruber, Nathalie Peregrine, Heidi Ullrich, Silvia Vivanco

Review of Action Items

HU gave an update on the content of the status report. Announced that the SIC would like to meet with the Taskforce.

Rec 5

Strategic Planning - Continuous movement is taking place.

Sala - Agree that people must be informed that the strategic planning process is an ongoing process.

OCL - Need to highlight that the one Taskforce AI deals with the strategic planning, one with operational planning and one with financial planning.

CLO: Remind the SIC and in the Taskforce in CR, by highlighting the flowcharts for the strategic and financial planning. While there is a set of interdependent cycles, we need to make sure our report blends them back together. How should we prepare the visual for the  SIC?

Dev - Strategic and Operational - not sure how you can define them as one process.

CLO: Not so much one process, but how do we illustrate it?

Dev: Helicopter view - the strategic - C1, Operational - C2, financial - C3.

OCL: The plan is to speak to Finance a better timing for us to discuss the process. A less stressful way than the current one. It won't change the process, just the timing.

CLO: We should give that as an example as an immediate continuous improvement (OCL and Senior ICANN Finance staff).

CLO - Should C2/C4 be added as an addemdeumn?

OCL - Append it.

Sala - footnote it for ease of reading.

Conduct periodic SWOT analyses of the At-Large strategic planning process in conjunction with the RALOs.  -

- A first SWOT has been developed.

- The suggestion is to update the SWOT on a yearly or every other year basis.

Dev - An update every two years.

Sala - think it should be a continous update/yearly.

Yrjo - Amendments every two years.

OCL  - Asked Seth re amendments

Seth - Yes, continous update is ok

OCL: Ok, so we will note that with dates, etc for the process

BB: What is the output of the SWOT. IE, who gets it, who is it presented to, and who is to act on it? The current SWOT appears to have some rather strong negatives. How are these to be addressed?

CLO: Asked OCL.

OCL - The SWOT itself is purely for ourselves. For the ALAC to find out wihether we are doing weell, where things need to improve. If something needs to be fixed, it comes down to ourselves. It shows where we are performing our duty, etc.

Yrjo - re Mission Statement, should there also be a....?

Sala  - Is it possible to put it up ont the wiki? So everyone can eventually...get consensus? ...a lot of feedback...review. Keeping the SWOT on the wiki allows for constant update.

CLO: Rather than being locked into time re updates, perhaps we could discuss during our Taskforce Prep call to develop lanugage re continous improvement, but also recognize that there needs to be a planned periodicity, at least in the short term, annual.

  • No labels