Thank you. That's an excellent question. I'm very glad to have a chance to answer it in more detail.
What the member said about making sure that you know what you don't know and that you know who to ask is very key to the training and the process improvements we're putting in place. It's very important for us to educate all of our engineers and product managers, but we're not going to be able to make them international experts in all aspects of privacy. If we were to aim to do that, it would not be setting up to succeed.
Above all, we want to educate them to not try to figure this out for themselves. Privacy is a complex topic, and addressing it properly within Google--or anywhere, really--requires a wide variety of expertise. It requires expertise in law, obviously and most certainly. It requires technical expertise to make sure there's a clear understanding of what exactly the technology is doing, what the systems are doing, and what the potential of that technology is. It requires expertise in the psychology of user understanding: of how the people who are going to interact with products will understand the options available to them. And it requires expertise in policy and communications in all of these things.
A very important point we will be making over and over again in our training is that individual engineers should never be making these judgment calls by themselves. We want to educate them on the privacy landscape and privacy concerns.
We want to very much educate them on Google's own articulated privacy principles of transparency, control, and responsible stewardship above all, but we also want to educate them very, very strongly and reinforce that education in many ways on the improved processes we are putting in place, to make sure that those fail-safes are there, that the thoughtful review is in place, and that individual engineers don't try to “lawyer” questions by themselves.