Problem statement: You are asked to build an app for a new theme park in Dubai. How will you go about designing it?
Let’s structure this article as an interview simulation.
To scope out the problem, I’d like to ask a couple of clarifying questions:
Me: I want to first understand what kind of an amusement park this is. Is it like a water park or is it like Disneyland?
Interviewer: It is more like Disneyland and very out there as most things are in Dubai.
Me: Do we have any resources, budget, or time constraints for the project?
Interviewer: Not really. The park is almost ready so we have about 4 months to launch the app.
Me: Great, thanks for clarifying. Now that I have these answers in place, I’d like to start with what our goals are for this Theme park app, understand the different user personas, deep dive into their pain points, and then create solutions for them. Lastly, I’d like to prioritize the solutions we will build that help us achieve our north star metric. Sounds good?
Interviewer: Sure, let’s go ahead.
Me: People, especially kids, associate Theme parks with happy places. It is a place to create memories and it bears a lot of nostalgia for the adults. The goal of building the Theme park app is to create virality by delivering a great experience that is monetizable.
The following personas come to mind:
With the given context I would like to prioritize the personas:
Both Ramesh and Arjun are tourists who want to have a memorable experience. Ramesh would talk all about it and recommend it to all his other friends who are also parents. Arjun is already bragging about all the rides he is going to take to all his friends all over Instagram. Therefore, these two seem like a perfect fit. Vendors are very important to the ecosystem but once we have enough traction, we could solve for them. Are you with me so far?
Interviewer: yeah.
Now going through the user journey let’s figure out a few pain points that the users experience:
Solutions:
The app should have the basic functionalities of booking a ticket online, showcasing a list of all the experiences. These are table stakes and I wouldn’t spend too much time talking about them. Our north star is virality and a great user experience and therefore I’d like to discuss solutions centered around it.
The next step is to prioritize these solutions on a roadmap. The approach I'd like to take is using the RICE framework.
Feature #2 is table stakes for users to have a great experience. #4 is a hero feature of the app that not only differentiates but delights. It would also boost shareability. #5 would leverage user excitement to further drive word of mouth. #1 and #3 are good to have. Ideally, we could wait a couple of months to get enough data about what people are enjoying and then build a good recommendation engine to plan the itinerary. For #3 There could be concerns around clicking photos without consent and tagging them to each user based on their spots. This is also a hard computer vision problem that would require quite an effort to solve.
In short, we should start with #2, #4, and #5 with parallel efforts to get data around experiences people love. #1 could then come in as V2.
Metrics to measure:
Problem statement: You are asked to build an app for a new theme park in Dubai. How will you go about designing it?
Let’s structure this article as an interview simulation.
To scope out the problem, I’d like to ask a couple of clarifying questions:
Me: I want to first understand what kind of an amusement park this is. Is it like a water park or is it like Disneyland?
Interviewer: It is more like Disneyland and very out there as most things are in Dubai.
Me: Do we have any resources, budget, or time constraints for the project?
Interviewer: Not really. The park is almost ready so we have about 4 months to launch the app.
Me: Great, thanks for clarifying. Now that I have these answers in place, I’d like to start with what our goals are for this Theme park app, understand the different user personas, deep dive into their pain points, and then create solutions for them. Lastly, I’d like to prioritize the solutions we will build that help us achieve our north star metric. Sounds good?
Interviewer: Sure, let’s go ahead.
Me: People, especially kids, associate Theme parks with happy places. It is a place to create memories and it bears a lot of nostalgia for the adults. The goal of building the Theme park app is to create virality by delivering a great experience that is monetizable.
The following personas come to mind:
With the given context I would like to prioritize the personas:
Both Ramesh and Arjun are tourists who want to have a memorable experience. Ramesh would talk all about it and recommend it to all his other friends who are also parents. Arjun is already bragging about all the rides he is going to take to all his friends all over Instagram. Therefore, these two seem like a perfect fit. Vendors are very important to the ecosystem but once we have enough traction, we could solve for them. Are you with me so far?
Interviewer: yeah.
Now going through the user journey let’s figure out a few pain points that the users experience:
Solutions:
The app should have the basic functionalities of booking a ticket online, showcasing a list of all the experiences. These are table stakes and I wouldn’t spend too much time talking about them. Our north star is virality and a great user experience and therefore I’d like to discuss solutions centered around it.
The next step is to prioritize these solutions on a roadmap. The approach I'd like to take is using the RICE framework.
Feature #2 is table stakes for users to have a great experience. #4 is a hero feature of the app that not only differentiates but delights. It would also boost shareability. #5 would leverage user excitement to further drive word of mouth. #1 and #3 are good to have. Ideally, we could wait a couple of months to get enough data about what people are enjoying and then build a good recommendation engine to plan the itinerary. For #3 There could be concerns around clicking photos without consent and tagging them to each user based on their spots. This is also a hard computer vision problem that would require quite an effort to solve.
In short, we should start with #2, #4, and #5 with parallel efforts to get data around experiences people love. #1 could then come in as V2.
Metrics to measure: