# Design reviews: ten questions worth asking

> The useful question in a design review is the one the author has stopped seeing. Ten questions about failure, data, operations and change, and how to ask them without stalling the review.

Source: https://hintvo.com/blog/design-review-questions-worth-asking | Last updated: November 20, 2026 | Reviewed: 2026-11-20

A design review earns its hour when someone asks the question the author has stopped seeing. The best questions come from how the current code already behaves: what happens twice, what happens when it fails, and who else depends on it.

## Failure

1. **What happens if this runs twice?** Retries, double clicks and duplicate messages all cause it. Payments and emails are where it hurts.
2. **What happens when the dependency is slow, not down?** Slow is harder than down. Ask where the timeout is.
3. **What does the user see when it fails?** If nobody knows, the design is not finished.

## Data

1. **Where is the source of truth, and what happens when the copies disagree?**
2. **What happens to the rows that already exist?** New designs are drawn for new data. Old data ships too.
3. **How large can this get?** A list that grows without a limit is a future incident.

## Running it

1. **How will we know it is broken?** Name the log line, the metric or the alert.
2. **Who gets paged, and what do they do first?**

## Change

1. **What is the smallest version we could ship first?**
2. **How do we turn it off?** A flag or a rollback path, decided before launch.

## Ask without stalling the review

- Ask about behavior, not taste. Taste belongs in a comment on the document.
- Point at the code: "The current consumer has no retry. Does the new design add one, and where?"
- One question at a time, and let the author finish.
- If it cannot be answered in two minutes, write it down as an open question with an owner and move on.

> **Where Hintvo fits:** during a call, Hintvo can suggest a question worth raising from your own code (the Ask this card), such as a missing idempotency key before retries are added. You can watch that exact moment in the sample meeting on the [home page](https://hintvo.com/#replay).

## Related

- [AI meeting assistant for developers, with answers from your code](https://hintvo.com/meeting-assistant-for-developers.md): How does Hintvo AI help in sprint planning, design reviews and incident calls?
- [Sprint planning: estimate from what the change touches](https://hintvo.com/blog/sprint-planning-estimates-from-the-code.md): How do I give a realistic estimate in sprint planning for code I have not read?
- [How to explain a technical term in plain words](https://hintvo.com/blog/explain-technical-terms-in-plain-words.md): How do I explain a technical term to people who are not engineers?
