Product design question

Should Twitter build Stories?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Strategic product judgment: deciding whether to build a competitor feature based on user need and company fit, not just copying.

Clarify the specific job Stories would do for Twitter users versus what Fleets or the timeline already do.
Identify the target segment: casual posters intimidated by permanent public tweets.
Weigh evidence: Twitter's earlier Fleets attempt was discontinued due to low usage, which is relevant context.
Decide based on whether ephemeral content fits Twitter's real time, public conversation identity.
If building, propose a narrow test rather than a full rollout, given the prior failed attempt.
Define success with a clear bar, such as daily story creators as a percent of daily active users.

Uses the known fact that Twitter already tried and shut down Fleets as key evidence in the recommendation.
Makes an actual recommendation, not just listing pros and cons with no conclusion.
Sets a specific bar for success, like 5 percent of daily actives creating a story weekly, to judge if it should continue.
Considers whether Stories fits Twitter's identity as public, permanent conversation rather than ephemeral sharing.

Why do you think Fleets failed where Instagram Stories succeeded?
What would you change about the format to avoid repeating that failure?
How would you measure this differently from Instagram given Twitter's public nature?