Product manager design question 1

How would you implement Chrome for Kids navigation.

Background:

Safe browsing for kids.

Personas:

1. Toddler
2. Young kids
3. Teenagers

Use-cases:

1. Education
2. Browsing
3. Entertainment

Solution: Metric: Implementation complexity:  

1. Profiling: While setting up the browser the parent/authority will set the profile in a manner so that safe browsing is always enabled. Payments are automatically disabled in this profile.
• Pros: Serves the purpose
• Cons: Extra setup and some technical expertise.
2. API call:
• When call is initiated from this profile then safe results are surfaced.
• Payment fails if the call is initiated from this profile.
• Cons: Requires expertise as to which content makes sense v/s which does not.
• Pros: Serves the purpose.
3. Notification: If weird content is requested then notification is sent to the authorities for review.
• Pros: Proactiveness
• Cons: Chances of false positive. If kids is required to do some weird searches for their biology class. It will trigger a meeting with parents/school authorities.
4. Override for parent functionality wherein they can use the same browser for their use.
• Pros: Convenience. No need of second browser on same machine.
• Cons: Chances are kid could learn how to override defeating the whole idea.
5. Reporting a summary of their kids searches.
6. Mature APIs based on search results and customer satisfaction.

Prioritization:

1. Profiling as it a basic feature & API call as its part of the basic feature as must haves in MVP.
2. Override is also MVP as otherwise the browser will be unusable for the parents.
3. Notification, Reporting, Mature APIs can be part second release.