 
Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

Fadi Chehadé Opening Speech (Part 3) | ICANN 46 | Beijing | 8 Apr 2013

0 (0 Likes / 0 Dislikes)
This is the working part, as you all know. And I like to take off my jacket, because we get to move a little bit around this podium.

Let me start. If I could have my slides, please.

When we started, back in Toronto, we called it a new season. I have learned now, through working with all of you, that it's really our season now. It's really our season. And during this season that I think is about to, we're in the middle of, and I think it's the beginning of a season that will last probably from now until we get to Buenos Aires. We are going into a phase of. I need my clicker, please. I need my clicker. We're going to go into a phase where we need to focus on the foundations of ICANN, on the enablement of ICANN.

Right now we believe that ICANN needs enablement at the process level, at the people level, and certainly at the systems level. And we've been working on that. During this enablement season, as I shared with you in Toronto, we will get the ground ready for the growth to come after that. And we have done some very good things in the last six months. So let me walk you through some of the enablement we have done.

Let's start with our goals and objectives. This is the slide I showed you in Toronto, where I told you these are our four key objectives and under them we outlined 16 goals. This was at the beginning of our journey together. We then committed to you that we will take all of these and translate them into a series of portfolios, programs and projects that start taking everything we do at ICANN and putting it into a system. We have done that. And the work has led to 56 portfolios, 168 programs, and nearly 500 different projects occurring into ICANN. All of this was designed and structured into a new system.

Now, if you go today to the site called MyICANN.org, you will have for the first time visibility into that system. Let me show you. So, if you go to the site today, you will see the same objectives, goals, portfolios, and programs. You can go down and look at each of them. You will see the status of the various components of that. You'll know what's at risk, what's in trouble. If you go into each of these areas, you'll see the owners. And this is the exact status of what's happening inside of ICANN in real-time. Okay? So, if we, for example, look at Akram's area, he seems to be having a lot of things in trouble. You'll be getting some calls, Akram. But, if you look into, for example, his IANA operations, in real-time it shows you the projects under that, the status of these projects. You'll get -- if you want information about Elise's business excellence initiative, you can go into that. You'll find that, it's timeline. You'll find out the details behind it. And this is just the beginning.

We're going to give you visibility, because that's your work. It's your projects. You need to know what's happening inside ICANN in real-time.

We did the same thing on compliance. Until today, getting data on our compliance is not always easy. If I want to see, for example, how many complaints are now in the system per notification cycle in real-time, you'll see that data. And this is across the board for all of the areas of this department. This is new. And this is not just slides. This is actually linked to the applications we've built in the last six months and moved all of our work into them and managed all of our work, all of your work, in a way that is structured, that is trackable so that we can all succeed together.

I want to give thanks to the incredible work that our team has put to make that happen. It was a collective effort.

Every function in ICANN is in the MyProjects section. Everything we do, including refilling the coffee in our coffee machines. Everything is in there. And now we're tying the budgets and we're tying the HR system at the systemic level into this. So now we don't even need to ask someone what are his goals or her goals for the next quarter. It will be picked out of the system, and it'll be in the HR system. And that's how we will work. Everything is now aligned inside ICANN from a structural and system standpoint.

Now, since we have so many people, I'll take the chance to remind you what is MyICANN. MyICANN is the tool we introduced in Toronto that allows you to go look at topics by topic and get information. Everything happening across all of the ICANN world is inside this area. You can look at calendars so you can track everything going on at ICANN in real-time, and you can transfer these calendars into your own calendar. So these are important advances in the way we display and we share information with you. And we hope many of you use it. And, by the way, we have now thousands of registered users on MyICANN, because you could register and then get alerts, real-time, into your inbox.

Just before I leave this page, I want to share with you that, because we're moving very fast, at the moment, this projects view is giving you a view that is cut on a monthly basis on the first of the month. By Durban it will become real-time. So by Durban, when you go into that system, you will be real-time seeing what we're doing at that moment and it will stay this way moving forward.

Back to the slides, if I could.

So what this does is it gives us the three things we committed to do in Toronto. It gives us agility, because we now can see things and be able to adjust them as we go. It certainly gives us accountability. I open every meeting at ICANN by looking into this data, and all of our leaders and executives start their meetings by looking at that data. This is how we manage ICANN. This is where it starts. This is how we keep things on track. This is what we promised you, and we're moving forward with it.

Of course, visibility is critical. We agreed with you that we are all one community. I have learned this over the last six months. ICANN is not the staff. We are ICANN. So you have to see what we see and help us improve. Full visibility to everything we do.

The next thing we talked about, if you recall, is the changing of the structure of the posture of ICANN from a presence and functional standpoint. This is the graph I showed you in Toronto. And we talked about looking at global responsibilities and local responsibilities. We have refined that model since then and it now looks a little bit like this. What we've discovered is that a lot of our global functions, instead of dividing them locally across the world, we will divide them across these three hubs I mentioned to you. So these will be distributed. Our legal department will be partly in Los Angeles, partly in Singapore, partly in Istanbul. Our compliance department will be distributed. We are putting a very difficult freeze, as best we can, on hiring in L.A. so that we can start shifting our posture and our presence to the other hubs as fast as we can.

So I want to be clear. These hubs are not what you'd call "typical engagement centers" or "offices". These hubs are ICANN's core. Every department will be distributed across these hubs, and, as I said, many of our leaders will also move to these hubs.

Now, Sally, our head of Stakeholder Engagement, will have the engagement functions which span the industry, the governments, and our community. These engagement functions will be localized. So, when we talk about an engagement center in Beijing, this is, these are the functions that will be here so we can go to the stakeholders, to the government, to the industry, and bring them into, as Minister Bing said, bring them into the ICANN structures through our engagement capabilities.

Now, a couple of notable things on this slide. We have announced yesterday, and that's thanks to a lot of bottom-up feedback I received, that it is time for ICANN to get a Chief Technology Officer. And we have announced the job on our Web site yesterday and we will be adding this important role. Frankly, we have had many years without a CTO at ICANN, and it's time we have a leader in that area that supports us, and that job is now posted, and I hope we will fill it by the time we get to Durban. We also have -- we'll be announcing tomorrow that we're bringing on board a new head of Strategic Communications. He will report to Sally and he starts in mid-May, and this will take the whole communications function and globalize it across the world. So, very pleased to also announce this addition. Now, I didn't plan to show you the slides to just talk about people. I want to show you what we're doing to make the processes behind these structures much more scalable. So let me take an example. I'm going to focus a little bit on an area that's maybe a little bit important to many of you these days, the gTLD services area. So, if I go into that department, one of the first things we did is to build a structure for the whole gTLD area, which we needed in order to serve all of you better.

The first thing we did is to create a new DNS Industry Engagement office and we hired a new Vice President, Cyrus Namazi, who is here with us today. And Cyrus will be owning all the relationships with our new gTLD partners. Then in the middle we built a service department, a service operations department that is, obviously, responsible for all the policy implementation and the service delivery to the gTLDs. And, finally, we're building a true proper support function that helps people come on board and supports them.

Now, if I go in a little bit more detail inside Christine Willett's operations area, we've broken that down into functional areas. Each of these areas have been defined. We have put behind each of these areas all the necessary processes, all the necessary tools so that we can make these areas scalable. So, for example, let me take transition to delegation as an example. When you go behind that, you can see all the details of how this area works, what are the processes. They're documented. They're repeatable. They're trackable. They're monitored. We're doing this across ICANN. That's what I wanted to share with you on the area of structuring.

So yes, it is our season to enable ICANN. And enabling ICANN is taking three things. First, our people. Building a new culture, a culture that is agile, a culture that is adaptive, a culture that is global. Secondly, maturing our organization, as you saw, with the processes and the structure that allow us to scale it on a global level. And, lastly, building the systems. Building the systems. Without these systems, the dream of three hubs is not going to be feasible. Because, if a compliance person takes a case and then goes to sleep in Istanbul and then the stakeholder calls the next morning and the time zone gets answered in Singapore, if they don't know what happened, if we don't have the systems to do that, it will not work. So we're deploying a true CRM system, a true trouble ticketing system. This is happening as we speak. We selected the system, and it's being configured and deployed. And we will finally have the ability for stakeholders to have their trouble tickets and their calls into ICANN logged and visible through MyICANN. And you will know the progress of your communications with us. That is all in motion right now. But, as I note on the slide, this will take time.

Right now, I want you to know that, even though we started in Toronto, we're still halfway through this and it will probably take us, at the earliest, later this year in Buenos Aires, to start getting to the point where our enablement is getting there. So we can build a new ICANN, an ICANN that serves the world and is also scalable.

It's also our season to engage. And many of you have followed my blogs, my travels, our team's activities around the world. Because we committed that we will go out to the world. We will not ask the world to come to ICANN. And this we had to do by action, not just by talking. So we went out and spent time around the world. And many things have happened over the last six months. I'm going to touch on a few.

The thing I'm, frankly, proudest of are the bottom-up regional strategies we have done. This, to me, is truly what ICANN is all about. So, we started in Africa, if you remember, from the Prague meeting, and we built a team of people that encompasses all of the key stakeholders in Africa. And not only have they come up with a strategy that we presented to you in Toronto, they've been implementing it!

I went to the first implementation in Addis Ababa. It was a workshop to help new registrars understand how to become good scalable registrars. And there were 84 people, 85 people there spending days getting real support and growing and making the African community embrace the growing DNS sector. This is a success. And I want to thank in front of all of us here both Pierre Dandjinou, who has jumped right into this and made it happen, our Vice President for Stakeholder Engagement in Africa. And, certainly, I want to thank Dr. Tarek Kamel and Sally Costerton for the great work that was done there.

Where is Pierre? Where is Pierre? Is he here? If you're here, stand up. You deserve the thanks. Pierre, thank you.

Video Details

Duration: 16 minutes and 4 seconds
Country:
Language: English
Genre: None
Views: 47
Posted by: icann on Apr 24, 2013

Fadi Chehadé Opening Speech (Part 3) | ICANN 46 | Beijing | 8 Apr 2013

Caption and Translate

    Sign In/Register for Dotsub above to caption this video.
https://dotsub.com/view/29a88588-8e97-46cf-b5e6-6a72631b1116
dotsub.com
crawl=CC-MAIN-2020-40
118291
application/http; msgtype=response
sha1:FIC5QTKBRQNQUFAR5D4FIMAX2QJXYUYW
<urn:uuid:50d1a637-b2c9-4c06-ba89-693c9c71194d>
2020-09-22T04:37:02Z
104.18.31.98
application/xhtml+xml
sha1:SXCHGEH2AJGU7SJAL7MR7EWYLDSVPAZM
<urn:uuid:2c1a2edb-f20d-40f1-b82f-99931a826917>
https://dotsub.com/view/29a88588-8e97-46cf-b5e6-6a72631b1116
response
<urn:uuid:0ec09ab3-7def-4acf-8cd1-b274430a659a>
isPartOf: CC-MAIN-2020-40
publisher: Common Crawl
description: Wide crawl of the web for September 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-123.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/