Twitter (X) Privacy Control: Choose the Problem, Design the Feature, Set Metrics

You are a product manager at Twitter (now X). Choose one privacy feature you would add to the product and make the case for it: which users it serves, what privacy problem it solves for them, how it would work, and how you would know it was worth building. ```hint Respect the public default Twitter is valuable because most posts are public, searchable and quotable. Look for a privacy problem that public-by-default posting creates for ordinary users, and a fix that does not make the whole network less public. ``` ### Clarifying Questions - Does "privacy" here mean control over what other people can see and find, control over how Twitter and advertisers use personal data, or both? - Should the feature target a particular group, such as people with small followings, people who read but rarely post, or people facing harassment? - Is the aim mainly to get more people posting, to keep at-risk users safe, or to meet regulatory expectations? - Can the feature change who sees posts by default, or must posts stay public unless the author acts? ### What a Strong Answer Covers - A stated choice between social privacy and data privacy, with a goal that ties the feature to posting and retention. - A segmentation of Twitter users by privacy need and a reasoned choice of one segment. - Concrete pain points for that segment and a single feature, specified down to its defaults and to what happens to replies, quote posts, search and embeds. - Success metrics that test whether behavior changes, with guardrails on public conversation and misuse. - Risks and trade-offs such as accountability for public figures, a false sense of security, and settings complexity. ### Follow-up Questions - If your feature makes some posts harder to see, should it work differently for government officials and other public figures? Why? - The feature is opt-in. How would you measure its effect without simply comparing the privacy-minded users who turn it on against everyone else? - How would you explain the limits of a privacy feature to users when screenshots and outside archives can copy anything that was ever public?