Choose the first Dropbox feature to build for distributed teams, and defend the pick

You are interviewing for a product manager role at Dropbox. The interviewer explains that Dropbox wants teams whose members work remotely to find it easier to collaborate, and asks: if you could build only one feature first toward that goal, what would it be, and why should it come before everything else? Walk through the users you would target, the collaboration problem you would solve for them, the alternatives you weighed, and how you would know after launch that the feature worked. ```hint Start from what Dropbox already holds Remote teams already have chat and video-call tools. Look for a collaboration moment that revolves around the files and folders a team keeps in Dropbox, where Dropbox has a natural advantage over those tools. ``` ### Clarifying Questions - Is the business goal to win new teams, to deepen use among existing team-plan customers, or to reduce churn among them? - Which remote teams should the feature serve first: small businesses and agencies, creative teams exchanging large media files, or departments inside large enterprises? - Does collaboration here include people outside the customer's account, such as clients and freelancers, or only colleagues on the same team plan? - Should the feature live inside Dropbox's own apps, or may it reach people through the chat and meeting tools the team already uses? ### What a Strong Answer Covers - A chosen segment of remote teams and one concrete collaboration workflow, justified by how often the pain occurs and how costly it is - Pain points rooted in remote work, such as asynchronous handoffs across time zones, scattered feedback and version confusion, rather than generic "communication" problems - Several candidate features compared on user impact, effort and Dropbox's right to win against chat, office-suite and meeting tools, ending in one clear first pick - Success metrics tied to the collaboration outcome, with adoption measures, a north-star metric and guardrails - Risks such as overlap with tools teams already use, notification overload and files shared with the wrong people ### Follow-up Questions - A competitor ships the same feature shortly after your launch. What keeps teams using the Dropbox version? - How would you test demand for this feature before committing an engineering team to it? - If adoption is strong among creative agencies but flat among every other kind of team, what do you do next?