Readwise Reader: put saved articles to use again
Readwise Reader is a reading tool for people who regularly work with web articles, PDFs, and newsletters. It connects saved material, annotations, and later review so readers can return to what mattered.
Form your own approach first, then explore the reasoning to check trade-offs and validation you may have missed. There is no single right answer.
Make the impact of clearing a reading queue clear
Design a cleanup flow for a hypothetical reading tool. Lin has finished article A, and two of its highlights have synced to a review library. Lin only wants A removed from the reading queue while keeping the highlights available for future review.
There are two existing operations: Archive retains the article and its highlights; Delete removes both the article and its highlights in the review library. You may change the entry points, prompts, and feedback, but not these data rules.
Submit a flow from “clear my reading queue” to completion, including key interface text. Explain how you would test whether Lin can correctly predict the impact of each operation. Add a second user who really wants all records deleted, and check whether that task remains easy to complete.
Explore the reasoning
-
Separate the user's goal from the data operation. Lin wants to organize a list, while the other user wants records removed. Compare the default entry point and action names against both scenarios; do not assume everyone should archive.
-
Map the affected objects: the reading queue, article, Reader highlights, and highlights in the review library. Explain what remains and what disappears instead of merely asking “Are you sure?” An Undo button needs a real recovery mechanism; the exercise does not promise one.
-
With a paper prototype, ask participants to predict the resulting state before acting. Observe whether they choose the intended action, notice the effect on the review library, and need extra steps to avoid mistakes. Correct clicks alone do not demonstrate understanding.
-
Compare the two goals. Making Archive prominent might reduce accidental deletion while making intentional deletion harder to find. Use task outcomes and state predictions to explain which design you would retain and what remains untested.