Product manager design question #2

How would you implement Google Chrome for Kids navigation.

As usual we will tackle this design question with keeping Goal in mind. We will then list out the personas, their use-cases, features, metrics to track, and prioritization.

Goal: Safe browsing for kids.

Personas:

1. Toddler
2. Young kids
3. Teenagers

Use-cases:

1. Education
2. Browsing
3. Entertainment

Solutions/Features

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.
1. Pros: Serves the purpose
2. Cons: Extra setup and some technical expertise.
2. API call:
1. When call is initiated from the safe profile then safe results are surfaced.
2. Payment fails if the call is initiated from the safe profile. This ensures that child doesn't order digital products by mistake.
3. Pros: Serves the purpose.
4. Cons: Requires expertise as to which content makes sense v/s which does not.
3. Notification: If weird/questionable content is requested then notification is sent to the authorities for review.
1. Pros: Proactive notifications ensure parents are on top of their kids searches.
2. Cons: Chances of false positive. If kids is required to do some weird searches for their biology class then it will result into false positives.
4. Override for parent functionality wherein they can use the same browser for their use.
1. Pros: Convenience. No need of second browser on same machine.
2. 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.

Metric:

1. Customer satisfaction: Need to ensure that parents are satisfied with the product. And children are able to use it with ease.
2. Implementation complexity: Based on customer satisfaction, we will prioritize features based on implementation complexity. High complexity features can start earlier. Features on which a lot of other features are dependent can start earlier.

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.