Instagram teardown: goal, personas, creator and viewer features, metrics, usage patterns

You are interviewing for a product manager role and are asked to walk the interviewer through Instagram as it exists today: its main features, who they serve, and how you would judge whether the product is working. Organize the walkthrough into the five parts below, and treat the people who post content and the people who consume it as two distinct sides of the product. ### Clarifying Questions - Should the walkthrough cover every surface (feed, Stories, Reels, Explore, Direct messages, Live, shopping) or go deep on the core loop of sharing and viewing? - Are businesses, advertisers and professional creators in scope as personas, or only everyday people who post and browse? - Should success be judged from the user's point of view, the company's (engagement and ad revenue), or both? - In the last part, what does the interviewer mean by a "reliable" user: one who is more likely to stay, one who is worth more to advertisers, or one whose engagement is healthier? ### Part 1 — Goal State what Instagram is trying to achieve, both for the people using it and for the business behind it. ```hint Two goals, one loop Think about why someone opens the app and why the company earns money when they do, and how one goal feeds the other. ``` #### What This Part Should Cover - A user-facing purpose stated in one or two sentences. - The business goal and how it depends on the user-facing one. ### Part 2 — User personas Describe the main personas, keeping people who create content separate from people who consume it. ```hint Motivation, not demographics Two people of the same age can use Instagram for completely different reasons. Group personas by what they want from a post or a scroll. ``` #### What This Part Should Cover - Distinct creator personas (for example someone sharing with friends versus someone building an audience) and distinct viewer personas. - What each persona needs and what frustrates them. - Recognition that one person often plays both roles. ### Part 3 — Features for posters and for viewers Walk through the existing features, grouped by whether they mainly serve the person posting or the person consuming, and say which persona each one serves. ```hint Follow the content Trace one photo or video from the moment it is captured to the moment someone else reacts to it, and list every feature it passes through on both sides. ``` #### What This Part Should Cover - Coverage of the major formats and surfaces, not just the main feed. - A clear mapping from each feature to the poster or viewer need it meets. - Features that connect the two sides, such as feedback that brings posters back. ### Part 4 — Success metrics Propose the metrics you would use to tell whether Instagram is succeeding. ```hint Both sides of the marketplace A feed with plenty of viewers but few posters eventually runs dry. Make sure your metrics would catch a problem on either side. ``` #### What This Part Should Cover - One headline metric, with a reason it reflects the goal from Part 1. - Supporting metrics for creation, consumption and monetization. - At least one guardrail that would catch engagement that hurts users or the platform. ### Part 5 — Comparing two usage patterns Two people use Instagram every day. User A opens it 5 times a day and spends about 10 minutes per visit. User B opens it 50 times a day and spends about 1 minute per visit. Which of them would you consider the more reliable user, and why? ```hint Start with the totals Multiply each pattern out before comparing, then ask what the remaining difference tells you about why each person opens the app. ``` #### What This Part Should Cover - An explicit definition of "reliable" before choosing. - A comparison on several dimensions, such as habit strength, depth of engagement, dependence on notifications and value to advertisers. - A clear choice, the conditions under which it would flip, and the data that would settle it. ### What a Strong Answer Covers - A walkthrough organized around the goal and personas instead of an unstructured feature list. - Consistent treatment of the poster and viewer sides across personas, features and metrics. - Metrics tied to specific features and personas, with guardrails. - A defended position in the usage-pattern comparison rather than "it depends" with no decision. ### Follow-up Questions - Time spent per user rises after a new short-video feature launches, but the share of users who post anything falls. Is that a win? - How would you test whether User B's pattern is driven by notifications rather than by the user's own pull toward the app? - If you had to simplify the app by removing or merging one existing feature, which would it be, and how would you check the impact?