IGF 2025 - Day 0 - Workshop Room 3 - Event #59 How to develop trustworthy products and policies

The following are the outputs of the captioning taken during an IGF intervention. Although it is largely accurate, in some cases it may be incomplete or inaccurate due to inaudible passages or transcription errors. It is posted as an aid, but should not be treated as an authoritative record.

***

 

>> Nadja, do you want to do a quick mic check to make sure it's working?

>> NADJA BLAGOJEVIC:  Yes, hi everybody

>> What channel is this room?  3.

>> NADJA BLAGOJEVIC: Good morning, can you hear me?  Yes, good morning, can you hear me?

>> We are not hearing Nadja.  Do you want to try it one more time for our tech team?

>> NADJA BLAGOJEVIC: Sure, hello, everybody, good morning, how are you today?

>> Try it again, this is the gremlins on day 0

>> NADJA BLAGOJEVIC: No problem, hello, everyone

>> I see the tech guys in the back of the room scrambling to try to make it work

>> Okay, sounds great.

>> So sounds like the online participants can hear Nadja but in the room, we can't.  Is that correct?

>> Can you hear?

>> No.

>> You are on 3 both?

>> Yeah.  Nadja, try it again, I think I can hear you typing.

>> NADJA BLAGOJEVIC: Hello.

>> JIM PRENDERGAST: Yes, there we go.  I was correct.  We're good.  Are the folks in the back of the room ready?  All right, I got the all clear.  So thanks, everybody, good morning, thank you for your patience as we kick off the IGF 2025.  It's always a challenge with day 0, 9:00 a.m. for everybody to find the room, find their way around the venue and get through security and as you can see get rid of the tech gremlins we have sometimes.  I'm Jim Prendergast with the Galway Strategy Group.  I'll moderate this session for you.  Officially it's titled How to Develop Trustworthy Products and Policies.

But the folks at Google have an internal nickname for it it's called Product Manager for a Day.  So what we essentially want to do is give you an overview of what it's like to be a product manager at Google.  How do you balance all the different challenges when it comes to launching a product into the marketplace?  All the different factors these folks have to take into consideration before you actually see a product.  And different feedback cycles it goes through.

And some of the challenges that frankly you face on a day‑to‑day basis.  What I'm going to do is introduce our two speakers.  We have one speaker here in person and one speaker global.  And then they'll give a quick overview and some case studies to show you what they deal with on the regular basis.  And they'll discuss the different considerations that do go into the product development.  And next what we'll do is do essentially two breakout groups.  One will be the in‑person participation, folks in the room.  Will is going to work through you with table talk exercises for about 20 to 25 minutes and Nadja will fingers crossed work with the online participants to accomplish the same.

I think from the technical standpoint the easiest way to not hear the people online is for all of us take the headsets off.  That's the shortest way to solve that tech issue with online and offline participants and ensuring remote participation which is an important part of the IGF.

I'll start here with introductions.  First we have Will Carter.  Will is an AI policy expert with experience shaping policy on AI.  And working with product teams to deploy AI responsibly in real world applications. currently works on leading AI policy and knowledge ‑‑ sorry and knowledge and information team at Google.

Leads engagement on AI policy and regulatory standard with senior policy makers around the world.  He advised sign your leadership and C‑suite executive on AI strategy and implementation and developed AI policies governance across the company.

Prior to joining Google, he was with a international studies where he focused on policy issues including emerging technology and Artificial Intelligence.  If you got a question about AI this is your guy.

Joining us remotely is Nadja, she's based in London a trust manager in Google with over 15 years in the tech industry.  And she's an expert in online security and digital literacy and she worked with Google on work across Europe including family safety and content availability.

I'll throw it to Nadja to kick off the case studies to set the stage for us.  Nadja.

>> NADJA BLAGOJEVIC: Thank you very much Jim, and thank you for being with us this morning.  Without further ado we will jump right in.

I'm very excited to talk wow all what Product Managers do at a company like Google.  As with most job there's no one right way to do it.  If you ask 100 people you will probably get 100 different answers but there's some common element that is a we will talk about today.

So you can think of a Product Manager as the person who is responsible for figuring out at its core what the problem is that needs to be solved.  Sometimes it's easy to identify what a problem is.  For example, once word processors were built it was fairly obvious a spell checker would be an improvement.  But some things can be less obvious.  For example with Google street view, when we first launched it wasn't clear to the degree to which seeing a location before a drive or a trip or contemplating a move could be.

This feature was a less obvious addition to a online map and solved a probe most people didn't realize they had.  So the PM focuses on identifying that problem and building out a vision and a strategy and a roadmap.  The vision should be informed by the problem you are trying to solve.  It should be a stable, long‑term, high level overview of what that problem is and how you are going to tackle it.

The strategy helps you navigate and leverage the technology and ecosystem factors that will be playing out over the lifetime of your product.  Your strategy should be relatively stable.  And your roadmap is thinking how you sequence what you are going to do to build your specific feature and move towards your vision.

Your roadmap usually changes frequently.  In consumer tech if you build a roadmap and it's accurate for a year, you are very lucky.  PM's partner close closely to coordinate teams and deliver the right features, right data, users, sales, marketing all the right times in the product development life cycle.  We really try to make sure that we are also the ultimate champions of our product, both inside the company and externally.

Um, and the goal is really to make sure that we are building something of value.  So that our broader teams and stakeholders can evangelize what we built as well.  As Product Managers, we work closely with our colleagues in user experience, which is sometimes abbreviated as UX.  So iteratively design and validate what we are building at progressively higher levels of fidelity.  It's very expensive to change something that's fully developed but it's very inexpensive to put a wire frame or a rough sketch of a product in front of someone that we want to use the product.  And ask questions like, would you use this?  What will you use it for?  What makes sense?  What is missing?

It can be really amazing but these small changes in language and wording and also insights can lead to huge impacts in adoption.  And lastly, but certainly not least, are our engineer count parts.  Engineers build and maintain products and make them work reliably and quickly for users.  And UX and eng are included in our roadmapping and strategy setting.  We build better plans of roadmaps when we have all three functions working together.

From the get‑go to sort of build out that roadmap and set the strategy and vision.  So as we, um, ‑‑ as Jim mentioned we'll go through the couple quick case studies to give you a sense how we approach product development walking through a couple features that we developed here at Google.

So talking now about AI overviews.

>> Nadja, could I interrupt a little bit?  Guys in the back, could we display the slides in Zoom and on the screen, is that possible?  There we go.  Okay.

>> NADJA BLAGOJEVIC: Great, thanks very much.  And if we could just advance to the next slide, please.  We'll go right into our AI overview case study.  Great.  So building on our years of innovation and leadership and search, AI overviews are part of Google's approach to provide helpful responses to queries from people around the world

They use generative AI to provide key information about a topic or a question.  And they are really designed to show up on queries where in the case add additional benefit in addition to what people are already getting on search where we have high confidence and quality in the responses.

For example if you look at the query on the right of the screen, AI overviews let you ask more complex questions.  This query is asking for help how to stand out on a first time apartment application.  And you can see you get a nuanced answer.  You get corroborating links and initial resources to dive in and learn more.  And you get that information and extra help in a very digestible way.

You can see here the user experience elements and the design with the bullet points, for example, or the placement of the links in this response.

And on the next slide, talking a little bit about that that sort of bar of high quality.  For AI overviews, we designed it to only show information that's supported by high quality results from across the web.  Meaning that generally AI overviews don't hallucinate in the way that is a other LLM experiences might.  This think this is important across the board but especially important for query that is a might be particularly sensitive for a given reason.

And for these kinds of queries whether they are about something maybe health related or finance related or seeking certain types of advice, we have an even higher quality bar for showing information from reliable sources.

We also have built into the product that for these queries, AI overviews will inform people when it's important to seek out expert advice or verify the information that's being presented.

Then finally here, we also have a set of links and a display panel here on the right‑hand side with more additional resources for relevant webpages.  Right within the text of the AI overviews.  And we've seen really positive results showing these links to supporting pages with directly within AI overviews is driving higher traffic to publisher sites

Because of AI overviews we are seeing people are asking longer questions and diving more deeply into complex subjects and uncovering new perspectives which means new opportunity to discover new content from publishers and businesses and creators

I will hand it over to Will to talk about this image.

>> WILL CARTER:  Thanks, Nadja and thank you all for coming today.  I'll talk a little bit about another feature we launched in 2023 called about this image.  Google Search has built in tools designed to help users find high quality information and allegation also to make sense with the information they are interacting with online.  About this image and synth ID are designed to help users understand the context and credibility of the images they are interacting with online, including understanding if those tool were ‑‑ or if those images were generated by Google's AI tools.

With Google image search results you can click on the three dots above the image and that will show you the image's history, which include includes when it was first seen by Google Search.  Whether it's been on other pages in past.  That can be really helpful for example if the image is taken out of context maybe it's been reused in what appears to be a story about current events in a way that's misleading.

It also shows how other sites use and describe the image.  You might be seeing it in the context of a news story described as relating to a current event.  It might actually be described different differently on other site that is a accurately describe the context and origin of the image and allows you understand the perspectives across a variety of sources related to the image

And finally you can see the image's metadata.  Increasingly publishers and content creators and others are providing metadata and takings that provide additional context about a image that can provide a variety of information, including whether it was enhanced or generated by AI, which is important to understand as powerful image alteration engines are wildly available.

So one of the key ways we do this is using a tool called synth IDs which is a tool for watermarking and identifying AI generated content.  Basically what this does is it embeds a digital watermark directly into the pixels of an image generated by Google's AI image generation tools.

 That's important because even when the image has been altered, for example by cropping it or screenshotting it or resizing or recolouring or flipping the image, those watermarks can still be detected making it more robust to adversarial behavior.  And all images made with Google AI tools are marked with synth ID.  That means if you encounter a image through Google Search generated by an AI tool you can see that in about this image.

So this last gif here shows how we recently integrated this image into one our products circumstance toll search.  Circle to search allows you to select something on the screen and select additional image about it

In this case you can circle a image and get about this image information to get information an the images you interact with online, which is a powerful way to understand that context and make sure that the image that you are interacting with is being used in the way that was intended with appropriate context and accurately.

So pass back to Jim for our activity.

>> JIM PRENDERGAST:  Yeah, sure, thanks, Will.  So give you a high level of all the different thing that is a product managers have to consider working with their teams, the privacy rights the, you know, some of the metadata you talked about with the image.  So what we are going to do now I realize it's early.  And hopefully you had your coffee and you are ready to be a little interactive.  We will break out to two, maybe three breakout groups.  I figure two in the room and one in the online room just based on how many folks we have.

What we are going to do is ask you to think for a little bit about 15 minutes or so.  And come up with ideas.  And there'll be instructions on the next slide that Will will walk you through and then we'll come back and share final ideas and thoughts  for the final 15 minutes or so.  Will, why don't you know show them what they are working with basically you

>> WILL CARTER:  Basically you will break out in a group and pick a PM who will represent your group.

You can one focus, you can pick one you prefer, info, news and quality are areas we are actively working on every day.

The idea is come up with an idea.  Come up with a feature that you think we could add to Google Search to address one of these issues.  Or make up your own product.

Then you will pitch your ideas to your VPs, that's us.  And argue for resources, based on what you need in order to make this real.  What you think the return on investment that you could generate from this product.  And that doesn't necessarily just mean how do you make money from it but add value too user and address a specific problem the users are encountering in the way they engage with our products

Don't forget about the things you need to make this a reality, that's that UXR and end support that Nadja was talking about earlier and also what is your go to market strategy and what is your success metrics and what is realistic timeline and road map?

You have about 15 to 20 minutes to do this activity and Nadja and I will engage with your groups to help you work through this exercise.  Good luck.  And maybe, what do you think?

We can, ‑‑ yep.  Maybe we can divide right about here.  So in the red right there.  And you to this side.  And everyone else to that side.  We could have our two groups in the room.  And

>> JIM PRENDERGAST:  Will will come down and prime the creative engine for everybody and Nadja has the online folks as well.  And we'll come back in 15 minutes and share the experiences and.  And we know there's a question from the chat room and we'll answer that as we come back from break as well.

>> For everyone online could you come off mute and say good morning?

>> Good morning.

>> Hello.

>> Basically we are in Norway right now but we arrived early in the morning to attend this session.

[off microphone] and we'll do the afternoon sessions in person.  And we are from Kuwait and from the information technology.  My name is Hasan I'm in charge of the CCLT

>> Wonderful to have you with us.  Are others able to come off mute?

>> Hi Nadja, can you hear me?

>> Yes, I can hear you.

>> Hi, this is Nidhi, I'm joining in from India, hello.  I'm doing my Ph.D. somewhere between tech and public policy.  And various areas of metrics so I'm very happy to be here.  Good to see you.

>> Wonderful, good to see you.  It's wonderful to know that everyone is able to come off mute.  At this point, I would ask everyone to please unmute yourself because for the next few minutes we'll be having a group discussion, which I will not be leading, that will fall to you all.  As Will and Jim mentioned, for these next ‑‑ this next session, in the breakout, we will be ‑‑ rather you will be brainstorming an idea as product managers.

And  it can be related to Google Search, it could be related to another Google product or just any technology idea that you think solves a problem.  Can everyone please come off mute?

>> Please confirm if you can hear me.

>> Yes.

>> I'm Aqdar I'm from India and working as a internet governance intern.  So I work somewhere between tech and policy.

>> Wonderful.  I'll pose the question to the group.  When you think about a product that you would like to build, or a problem that you would like to solve, what springs to mind?  And this is open to the entire group, please.

>> Well I do regularly have a lot of real case scenarios.  And some projects undergoing right now.  We can get ‑‑ I can share some information with you.  And maybe if you guys are interested to help us develop appropriate policies or get insights from you for the upcoming products in the dot KW domain space.  If you are interested, I can pitch the idea for you guys and move with it.  Or otherwise I'm really open to work with the other team members on other ideas.

In the end it's all going to benefit us all in the way we will think about how to build the policies and what aspects we need to consider when making a strong policies.

>> Great, other thoughts from the group?

>> I think I heard Hasan correctly.  He has an idea and would like to share that with us and we can pitch that together, is that correct?

>> Yes, that is correct.  I do have some ideas from our day job I can share with you.  For example, since we are in charge of the dot KW domain space, we are thinking of implementing AI tools to help us make the registration process for domain names in Kuwait faster and easy process with the benefit of AI, we can like process the domain request almost immediately without waiting for someone to look up the documents and make all the choices.

So just I'll give you a brief how the domain space works in Kuwait.  We do have two zones to register.  We have, for example, who would like to register a name.com.kw.  Since we have the extends dot com.kw for the business entity in Kuwait.  There's a requirements  for the entity to register like having a valid trade license in Kuwait and having a representative in Kuwait.  Someone is either going to be a Kuwaiti citizen or someone with a work permit in Kuwait.  So these kind of documentations are right now manually uploaded throughout the portal.

Then it has to be checked by a person to validate all the information and making sure that when the registration request is valid, what we are thinking of implementing right now is AI tools and some sort of integration between the government entities so to make the process seamless and we could a domain up and running within minutes, instead of like, for example, 48 house right now.

>> Great.  When you think about building out this AI tool, what kind of resources do you think you would need to be able to develop it?  And this is sort of a question for the group.

>> I can give them a hint, basically.

>> Yeah.

>> (Laughter).  The process is going to be similar somehow like the client would like to register a domain need.  They will need to at the moment to upload their trade license.  Once that's uploaded we can use a image recognition tool to validate the document.  And make sure it's not a fraudulent document one of the regulations we have in Kuwait is the domain name registered the commercial entity has to match the name of the entity in the commercial trade license.

So we can with that image recognition tool or text recognition tool, it can match the requested domain name, for example, with the name and trade license.  If it find a conflict, it shouldn't reject that request.  It should pop up some sort of suggestions for the clients to pick names from.  That's one example.

>> Mm‑hmm.  And what kinds of sort of internal partnerships, which department dos you think, whether that's UXR or engineering would you need to work with legal departments.  Who would you need to work with to have the tool be able to do what you just described?

>> Mm‑hmm, well we enjoy in our department it's a one‑man show.  (Laughter).  Where basically we do set the policies and we do have control of the technical aspects of the whole registration process.  But we do seek some help from the legal department, that's for sure.  Because we have to set some sort of like guideline when unloading these documents and we need to check with what kind of document to accept and how to handle the sensitive information, whether it's confidential data that can be shared.  What kind of level of confidentiality is these documents to be uploaded and how to be handled and whether we can share them with third parties or not.

>> Mm‑hmm.  Yes, great, data privacy and data security seem like they would be very essential for the project development process.  When you think about timeline do you have an estimated time frame for how long something like this might take to develop?

>> Usually these sort of tools or ‑‑ there are a lot of out of shelf solution ready to be picked up and integrated.  So we are expecting around 6 month.  This is the time frame to have it done.  And technical aspect.  Since we are working with governmental entities here and maybe we need some governmental integration, you know how sometimes the government might extended to more than 6 months.

>> I like that very much.  [overlapping speakers]

>> We always encourage optimism, even if the entire repetition of government to work takes a lot of time we always push for more efficiency and faster time, even though.

>> I think this is great, I think maybe we have a hand raised.

>> Yes, I had an opinion on that.

>> Sure, go ahead.

>> Yeah, so basically what Hasan is saying is what I'm understanding is right he's saying there needs to be a capacity building.  Making the public servants familiar with this.  And integrating this AI into the framework.  Right?  Is that right?  What I'm understanding?

>> Yeah, that's correct.  Yes.

>> And you have to train the public servants how to use these tools, and basically there needs to be a capacity building.

>> There has to be some sort of training how to use the tools and yeah, that's absolutely correct.

>> Does anyone on the call have ideas about what we should ask our "vice presidents" for in terms of resources to develop this kind of capacity building?

>> We should tell them to be patient.

>> (Laughter).  I ‑‑ I agree with that.  (Laughter).

>> Yeah, the process takes time and you have to be patient.  And Hasan, if you are looking into some global case studies then you can look into Argentina, they have a similar program to this.

>> Thank you for the insight.  We have a couple of success stories in the region.  Mostly in the United Arab Emirates and they have some tools and at Qatar they have some tools.  And we are in talk with them at the moment to benefit from their experience.  And since we are ‑‑ we are like a [off microphone] countries in the Middle East like Gulf countries we share the same policies and we have the same structure for domain name.  So it's easier to get experience from these countries.  And they've been very helpful.  But definitely we will look into Argentina.  And we have also looked into Austra ‑‑ Australia they had a great help for domain name.  Very beneficial.

>> I think we'll be rejoining the group in about 2 minutes.  When we go back into the main group, Hasan, would you like to present at the Product Manager?

>> Definitely, but I would also love to ‑‑

>> Hasan is our presenter.

>> Great.

>> Any final thoughts for anyone on the call or questions or point that is a we think should be made as Hasan pitches this idea?

>> You should communicate to what you are doing for the public.  Since it's a public sector you have to communicate with them even with the failures effort.  So the build test.

>> Aqdar, do you have suggestions how to do that?

>> No, as you are doing you can do a small press briefing or something like that, even on your website.

>> Definitely, we do usually have some press releases.  And briefs sometimes whenever we enable new features and conduct KW domain space.  For example, last year in September when we released the roadmap for registering the second level domain name, your name.kw without dot com.  We released a roadmap how we release domain names and on the basis it will be released so basically yeah we do regular press releases whenever we have new features.  And this is this is the one of the best ways to communicate with the public.  Aside from social media.

>> Because they are the ultimate users.  So you always need their interaction and their feedbacks.  If there's no interaction you won't get proper feedback.

>> One thing that came to my mind we are in the process of releasing a dispute resolution policy for the domain names for Kuwait.  And the national dispute resolution policy.  When we release that policy, we seek public consultation.  We have [off microphone] on the websites and we give participants around 60 days to participant and give their idea on what are the policies.  And what has to be changed or improved.  And we have received really good feedback from the public.

>> That's really nice to hear.  And 60 days is a good time frame.

>> This is the approach we are doing in Sitra [sounds like] Kuwait it's like the TRA the access for information and communication.  Whenever there's a new policy we push it to the public consultation to get feedback.  And then we analyze, get the feedbacks and improve.  And then we release the final version.

>> Sound like we will be rejoining the main group in just a second.  And so Hasan will be our representative presenting the product idea and we'll also hear from the other two groups who have been workshopping their product ideas in person at IGF.

>> Make us proud.

>> No worry.  (Laughter).

>> We are only like 10 minutes away from the forum, by the way.

>> Great (Laughter).

>> It's now raining.  And then after this session, we will join you guys on the floor, in shala.

>> Wonderful, great to meet you in person.

>> I'm still in India, I am not so lucky.

>> JIM PRENDERGAST:  Okay, Nadja, can you hear us from where you are?

>> NADJA BLAGOJEVIC: Yes, we can.

>> JIM PRENDERGAST:  Great, I was listening to all three groups and I was impressed the creative juices got flowing at this hour, especially with the jet lag.  And congratulations to everyone who partook.  And Will do you want to share insights ‑‑ well actually let me ask you the question while the other groups get organized and prepared to read out.

And the question that came in before the break is how do you scrape high quality content?  What are the parameters of what you call high quality?  And as Will is answering that, each spokesperson give us get ready to share a 2‑3 minutes of your deliberations.

>> WILL CARTER:  I wish there was a simple answer.  This is something we struggle with every day and this is a significant area of innovation and investment for Google.  There's a few approaches we are taking currently and they evolve all the time as we try to figure out how to do this better and better.

One way is to work with fact checking organizations around the world that can validate information for us and do additional research.  And those partnerships are really key.  Another way is to identify news sources that are consistently providing high quality information that are independent and that are generally reliable and validated by fact checkers.

And but really at the end of the day I think the most important thing we do is provide context to our users as much as we can about where the information they are interacting with came from.  So that's providing additional links, providing counterarguments, providing access to metadata and additional information.  Because there is no one metric or one definition of high‑quality content.  And there's no one accepted, um , you know, source of truth for this.

So I think empowering users to really understand the content they are interacting with and make their own informed decisions on what to believe and not to believe is the most important thing that we can do.

>> JIM PRENDERGAST:  Okay, great.  So if I can, I'm going to call on the group to my left.  To maybe go first.  And then we'll go to online group and then the group to the right.  Did nominate a spokesperson?  Great.  There should be a mobile microphone I put tonight table.  There you go.

>> Can you hear me?  Great.  You said 2 minutes?  Okay.

In our group we discussed a feature that would be added to Google Search results that include news articles.  And the goal of the feature is to give users information about the validity of the news article, some kind of flag or visual signal to show them if they are looking at something trustworthy.  We specifically talked about identifying news that is ‑‑ that can be known to be false or known to be generated by AI.

And we would ‑‑ if we are able to determine that, add a flag to show that to users to show they are looking at something that is AI generated.  And they can still view it but it would be a visual cue.  We discussed some of the ways to kind of generate this information using fact checking organizations that are credible.  And based on the country or location where they are reviewing information.

Um, we talked a bit about some of the resources needed to do this, of course you need an engineering and UX team.  But we also talk about kind of cultural competency.  And having a group or a some type of experts on knowing news sources and what kind of the cultural dialogue is in different context.

And also kind of the legal and ‑‑ legal framework to know that.  Um, and, yeah, talking about the ROI of this feature.  We talk about why a company like Google should incorporate this feature.  And the ROI would be increasing trust in the product.  Giving users insight into the information they are looking at, which is something they are seeking and would be a unique value that would bring them to use Google Search as opposed to other search engines and generally increasing trust and enabling users to rely on the information they are getting and encourage usage.  And the roadmap we can't really get that far but this is the idea we came up with

>> JIM PRENDERGAST:  Great.  You covered a will the of territory in a short period of time especially with a cold start.  We appreciate that.  I'm not sure who was nominated to represent the online participants but we will unmute you if you try to talk or Nadja dorks you recall who is your spokesperson?

>> Yes, that would be Hasan, are you able to come off mute.

>> Good morning, everyone.

>> JIM PRENDERGAST:  Good morning.

>> My name is Hasan. I'm from Kuwait and the TRRA for the country.  And I work with the domain names and the policy making.  With my colleagues in online session we discussed a feature that would be added for dot kw domain name registrations.  For example the current process right now, we do have two zones.  We have a restricted zone for registration.  And a unrestricted zone.  What we mean by restricted the third level domain name such as dot com.kw, your name.com.kw indicates a business entity.  To enter a domain your name.com.kw you have to have requirements you have to be a ‑‑ to be a commercial entity in Kuwait with a valid trade license

And be represented by someone who is based in Kuwait either a Kuwaiti citizen or a work permit.  So the process now is semimanual.  Whoever needs to register a domain name they need to upload a document like the trade license.  Their civil ID, for example.  And these are being checked manually by one of the employees at the dot kw domain name space.  And then we can grant that domain name registration

But we are looking into other solution that is a might make the process faster, much easier.  We are thinking of blending AI tool to do these sort of scrubbing and checks.  One condition if you would like to register a dot c om.kw domain name.  The name you select has to match with your trade license or your trademark license.  So instead of doing that manually checking, we can have some sort of scrubbing that will check the name of the license.  Or the name of the trademark.  And then it will process the request almost immediately.  In case of, for example, the whoever is registering a dot kw that is selecting a name that doesn't match the name or license the AI tool will give them a suggestion of what appropriate domain names could be registered.

>> JIM PRENDERGAST:  Thanks, Hasan, we are short on time.  I am getting a ticking down sign from Oliver in the back.  Briefly to our folks in the room on the right.

>> I'll be brief.  We are building on a product that was mentioned earlier but on a public news classification.  Like what Will was saying about creating a informed audience we want to build right now when you go on Google Search you have three dots when you come up with a news article that provide some context about the news outlet.  This feature isn't in the news aggregator tab when you go to Google news so we want to build on that where you have a classification of based on whether a neutral contact or a sensationalist content, we would give users the information they would need to make informed decision on what they think is credible and trust.  And that's hard to define internally and externally.  And build on the other team, we would work with UX and engineering and also leveraging subject expert expertise at Google and with the Google news team and Google to build a framework that could be taken to product.

In terms of ROI we want to drive user engagement and by providing additional context and other links within the Google ecosystem they are able to continue staying on the platform and continuing to engage with the content that Google would provide.  And also at the end of the day it's about providing more context and building information quality online, subject to their own understanding of what they are ‑‑ they being the users but also what ‑‑ like what quality looks like in different political contexts.  So yeah, I think we are all interested in news credibility.

>> JIM PRENDERGAST:  Yeah, no, that's definitely a common theme and this being the beginning of the IGF I'm sure that's the common theme that will carry on.

Will I'm impressed good themes and thoughts.  And do you want to create and Nadja can wrap up in the next 90 seconds.

>> WILL CARTER:  Sure I'll keep it brief and then kick it over to Nadja.

There's a reason why these issues are top of mind.  These are things they are all struggling with on a day‑to‑day basis, whether Google or users on the web trying to understand all this information inundating us every day and trying to make sense of is and what is credible and what isn't.

You came up with great ideas.  And this gives you a sense how when you think of a problem that you interact with every day, how you actually start to translate that into a product tuition, identify your needs, turn it into something that can work and solve that problem day‑to‑day.  This is what we do at Google.

 This is exactly what our workday looks like.  So really excited to ‑‑ [cell phone ringing] really excited to have you all participate in this process.  Nadja.

>> NADJA BLAGOJEVIC: Yes, just a fully agree with Will.  It is wonderful to be with you and hear everyone's ideas.  And, you know, these are all topics that we care very deeply about internally at Google.  And we are very grateful for the opportunity to be here and be in dialogue with you all to hear your point of views.  To learn from you.  And to share what we are doing.  Not only in terms of how we think about product development and design and how we approached some of these issues within our own suite of products but also, you know, to sort of share and be in exchange when it comes to, you know, our philosophies.

And ultimately, these topics will need robust collaboration between public, private sector.  Academia.  Civil society.  So thank you very much for being with us right from the very beginning of day 0.  And I very much hope you enjoy the rest of your IGF.

>> JIM PRENDERGAST:  Great, thanks, Nadja and speaking of slab ration I'm getting the hook from the back of the room.  And thank you for participating online and in person.

Will will be here for the rest of the week if you have questions, track him down, that's how these IGFs work if you have never been.  And goodbye and have a great meeting.

>> Goodbye, thank you, everyone.

(applause)