How would you approach the design and go-to-market for a completely new bike concept?
You'll get access to over 3,000 product manager interview questions and answers
Recommended by over 100k members
Assumptions
I am Pm at Google
no constrainst on kind of bike and resources
Geographical : North India
Product goal - Awareness and adoption
Strategic goal - curbing Carbon footprint + fight hot temperatures
User Segments
daily wager
average lower middle class
students school
professionals
personal usage
tourist
Pain point
- travels by public transport
- time taking
- traffic issues
- increase temperatures
Solutions
1. Time duration
google maps, telling ETA
Impact - low, effort - low
A custmer delight feature
2. Heat waves
solutions
a. thermostate , recharge through solar
Impact - high, effort medium
b. mud based technical device
Impact - high, effort - very high ---- MS
3. Parking
reduce the parking space by folding the seat.
Impact - high, effort - medium -- F3
optimatimally charged on solar energy
Impact -v high, effort - medium - F1
4. custimizatble bike
Conversion into bi traveller from mono traveller
Impact - mediumto low, effort - high
5. Intergation with Google Home
impact - medium, effort - low
Summary
Would build a bike which could curb climate change by utilizing solar energy as engery source.
- CLARIFYING QUESTIONS:
- Should I assume that Google is designing this bike v. existing bike company (ex. Trek)? Is there a goal in mind? You choose.
- Is there a specific customer segment you are targeting? You choose.
- Is there a specific type of bike you'd like to focus on - electric, mountain, road, motorcycle, etc. You choose.
- Is there a target market? Domestic, international, etc.? You choose.
- Are we modifying existing bikes with a new bike concept or building a bike from scratch? You choose.
- Should we focus on designing a physical bike v. an app (like citi bike) to get access to bikes? You choose.
- USER GROUPS: There are a number of user groups we can think of. I'd like to focus on Cyclists, as they are most enthusiastic about new bike concepts / more willing to spend on bike accessories, bikes, etc.
- New Riders: Never road a bike. Learning to ride.
- Casual Riders: Casual riders who may ride generally to work (ex. Citi bike) or around the neighborhood or down the board walk.
- Cyclists: Cycling enthusiasts who ride to exercise.
- Pros: Racers who compete in various cycling events - ex. Tour De France, triathlons, etc.
- USER JOURNEY:
- User figures out path where to ride. Focuses on long distance or difficult riding paths. Ex. mountain bikers may look for rougher terrain that's fun to ride through. Road bikers may look for long distance paths with smoother terrain.
- User dresses in bike gear - bike shorts, helmet, etc. May also apply sunscreen, etc.
- User gets snacks or water / gatorade for riding. May also bring bike repair kit in case of flats.
- User checks bike before ride (air in tires, gears, etc.).
- User prepares GPS watch or Strava bike app (or another bike app) to track distance.
- User embarks on ride.
- User returns. Racks bike. May check it for damage or repump tires.
- USER PAIN POINTS:
- Bike Type: User is limited on type of riding / path by bike. For example, a road bike is not suitable for riding through the forest. Cyclocross bikes offer more versatility for riding on terrain types.
- Bike Shoes: User shoes will change based on bike pedals - i.e. type of pedal will dictate to a certain extent a certain type of shoe a user must use. Pros and cons to each kind of shoe (ex. a lighter shoe may be more difficult to walk regularly in).
- Bike Gear Cost: Bike gear can be expensive. Racing helmets for example can be costly if you go for more aerodynamic helmet.
- Bad Weather: If user is caught in bad weather (rain / snow), riding can be difficult and dangerous.
- Nutrition: User may have underprepared on nutrition. May get dehydrated or didn't eat enough.
- Mishap: User gets a flat or gear breaks, etc. during ride. May not be prepared to fix or may not know how to.
- Unexpected Path: User rides into unexpected terrain / bike is not suitable for riding through it.
- GPS Tracking: User's GPS doesn't track properly / ride isn't logged.
- Bike Storage Limited: User doesn't have enough space to store bike.
- PRIORITIZE PAIN POINTS: I'd like to focus on the high pain points - specifically bike type, as I believe there is a big opportunity to design novel bike type concepts that will gain big market traction.
Pain Point User Pain Bike Type High Bike Shoes Medium Bike Gear Cost High Bad Weather Low Nutrition Medium Mishap High Unexpected Path Medium GPS Tracking Low Bike Storage Limited Medium
- LIST SOLUTIONS:
- Build a Bike: Create a website or app that allows users to input preferences for riding and then build custom bikes that meet their needs.
- Universal Bike: Design a new type of bike that allows for more universal riding - ex. multi terrain, light weight for racing, etc.
- Interchangeable Bike Parts: Design a bike that allows for easy swapping of parts that permit user to ride different kinds of terrain, races, etc.
- Map a Path: Build extention into Google Maps that allows users to map bike path and see what kind of bike is best for riding that type of path. Google tells user this terrain is rough - best to use gravel bike or mountain bike, etc.
- PRIORITIZE SOLUTIONS: If I was restricted on cost, I'd would focus on "Map a Path", as it is low cost but has high impact to user.
Solution Impact to User Cost Build a Bike Medium Medium Universal Bike High High Interchangeable Bike Parts Medium High Map a Path High Low
- DETAILED SOLUTION:
- User can input standard bike ride requirements: distance, ideal time riding, etc.
- User has ability to input type of bike riding wants to do (ex. BMX, mountain, etc.). Can also add comments like "I want to ride in a hilly area" to practice riding at an incline.
- User sees various options of paths available and also has ability to choose which areas to focus in on (i.e. within 10 miles from my home, this neighborhood, etc.)
- User sees popular bike courses available too.
- User can add custom locations they'd like to stop at or Google can provide suggestions based on known bike stops.
- Map can integrate into popular bike apps, like Strava, for easy tracking.
- Rides will save in Google Maps / user can create log of paths they've riden.
- User can add comments or tags to their ride to help with tracking.
- GO TO MARKET:
- Target Customer: Cyclists - already defined in user groups
- Offering: Map a Path - see detailed solution above
- Competition: There are other bike tracking apps, like Strava, and mapping software, like Apple Maps, but they don't allow for as much customization. Having the ability to add this much customization to your bike paths is a new concept in the bike world based on my knowledge of the industry. Bike tracking apps may actually be potential partners since they may use Google Maps as for their mapping tech.
- Product Positioning / Marketing / Partnerships: Prepare marketing campaigns that focus on target customer through campaigns that they would see. Partnerships is a big area that would help target cyclists, as there are not too many major bike brands that build bikes or bike parts or offer bike services. I'd also focus on marketing with major bike brands that work with my target customer (ex. bike shops, bike gear makers, etc.). Could also focus on partnering with major brands that build digital apps that leverage Google Maps for biking and are very popular among Cyclists, ex. Strava.
- Channels: Would focus on digital, given that Google owns existing ad channels already. Includes email / SMS, Google Maps pop ups, Google SEO, etc. Could also thinking about marketing campaigns on TV or bill board pop ups. Finally, may consider paper campaigns that partner with bike brands - ex. advertise in bike magazine, include insert when customer receives letter in mail from bike shop etc.
- KPIs / Metrics: Define most important KPIs for product. Examples include:
- # number converted users through marketing / advertising campaigns
- # of new users / month
- Average # of times user uses maps / month
- Average # of routes user maps / month
- SUMMARY: I'd build a Map a Path extention as my new bike concept into Google Maps after analyzing potential user groups and focusing in on the pain points of Cyclists. Given the potential solutions to new bike concepts for this user group, I believe this one works well with the existing Google offerings (i.e. builds into Google Maps) and would have a high impact on the user.
Top Google interview questions
- What is your favorite product? Why?89 answers | 263k views
- How would you design a bicycle renting app for tourists?62 answers | 82.5k views
- Build a product to buy and sell antiques.54 answers | 66.8k views
- See Google PM Interview Questions
Top Product Design interview questions
- How would you design a web search engine for children below 14 years old?36 answers | 42.9k views
- Design a library for the future.25 answers | 23.5k views
- How would you design a consumer application for a scooter sharing business?21 answers | 18.6k views
- See Product Design PM Interview Questions
Top Google interview questions
- How would you improve Google Maps?53 answers | 228k views
- A metric for a video streaming service dropped by 80%. What do you do?50 answers | 135k views
- Calculate the number of queries answered by Google per second.45 answers | 78.5k views
- See Google PM Interview Questions
Top Product Design interview questions
- Build a product to solve the dog poop problem.13 answers | 9.4k views
- How would you design a "Google Refrigerator"?13 answers | 8.3k views
- Design a social travel product.12 answers | 13.4k views
- See Product Design PM Interview Questions