# 13B Writing a Useful Reproduction

A reproduction describes the steps that lead to a problem so that another person can observe the same behavior independently.
It should begin with the necessary starting conditions, such as the selected account, the current page, and any required saved data.
Then it lists the actions in the order they occurred, using precise verbs instead of broad instructions such as use the application.
For example, I can say that I opened the lesson, selected the topic menu, and waited for the options to load.
The description should separate the expected result from the actual result and note whether the problem occurs every time or only sometimes.
If the issue appeared while another operation was running, that background activity may matter and should be mentioned without assuming a connection.
I also record what changed recently, while keeping a recent change separate from a confirmed explanation of why the problem happened.
A good reproduction does not need every detail of the entire session; it needs the details that another person must repeat to see the issue.
Once the problem has been fixed, the same sequence becomes a practical way to check whether the original failure has really disappeared.
This turns a confusing experience into a small, repeatable example that supports both investigation and a clear explanation of the result.