Wordle · Product sense · Entry · 45 to 60 minutes

Decide how Wordle should support sharing

Wordle is a browser based daily word puzzle where players get six tries to guess a five letter word. Answer this product management case and get it graded line by line against a weighted rubric.

Product sense
User empathy
Prioritization
Metrics thinking
Tradeoff judgment

The situation

Josh Wardle has opened Wordle, a simple browser game he built for friends and family, to the public. The game has no app, no marketing team, and no monetization. Players solve one shared puzzle each day, and a small but growing set of users are already discussing their results in WhatsApp groups and on social platforms. Some are even making their own text or emoji summaries so they can compare performance without revealing the answer. Josh asks you for a recommendation on one question: should Wordle add a built in way to share results, and if so what should that experience look like? The choice matters now because sharing could help new people discover the game and strengthen the daily ritual, but it could also make the product feel spammy, spoil the puzzle, or push Wordle away from its simple, friendly purpose. Engineering time is tight, and any change that feels like a growth tactic could clash with the creator's values. Your job is to recommend a focused path that serves players first and is realistic for a very small product.

What to produce

Write a 1 page product recommendation memo.

Your answer must

State the user problem to solve and identify the main user groups affected, including current players and people who may see shared results.
Recommend whether Wordle should add a sharing feature now, and clearly describe the core user experience from puzzle completion to shared post.
Explain why your approach fits Wordle's daily shared puzzle format and how it could help engagement or discovery without spoiling the answer.
Define 3 to 5 success metrics and guardrail metrics you would use after launch.
Identify the biggest risks and tradeoffs, including spoilers, spam, and preserving product simplicity, and give a mitigation for each.
Call out what you would explicitly not build now.

Constraints

Wordle has one shared puzzle per day, and the answer must not be revealed to players who have not solved it yet.
The product is a lightweight web experience run by a single developer, so the solution should be simple to build and maintain.
Wordle does not use ads or personal data as part of its value proposition.
There is no native app, so your recommendation should work for a browser based product.

Format

Use short sections titled goal, users, recommendation, feature flow, metrics, risks, and not now.

How Wordle actually played it

Tells Wordle's backstory and rapid growth, arguing that scarcity and simplicity worked against typical growth tactics, and notes risks like copycats.

Constraints like one puzzle a day create anticipation
Simplicity helps sharing
Name risks to a viral hit

Built from Wordle is the Anti-Growth Hack by Aakash Gupta (Product Growth).