A first research round often changes the next useful question. Once people can find an account setting, the team may discover that they still misunderstand what changing it will do. Iterative research makes room for that progression by alternating investigation with changes to the design or the research itself.
It can involve successive prototype tests, interviews whose questions develop as new issues emerge, or concepts revised in response to feedback. Repeating the same exercise without using its findings is repeated measurement, but it does not capture the full purpose of iteration.
Give each round something to build on
Start with a question and enough context to interpret the answer. After the round, record the observations, the changes they support, and the uncertainty left behind. The next study should be able to examine that uncertainty rather than simply producing another set of comments.
In an illustrative permissions project, the first round might reveal that “Owner” is understood as the person responsible for a document rather than the person allowed to delete it. The team changes the label and explanation, then tests whether new participants can predict who has that power. This makes the reason for the revision explicit and gives the next round a clear purpose.
The government’s guidance on planning user research recommends making each round’s questions and contribution to decisions clear. That record becomes especially useful when several designs and study versions are in circulation.
Adapt carefully when comparisons matter
New participants can help reveal whether a revision works without the benefit of earlier exposure. Returning participants may be appropriate when the question concerns learning or change over time, but familiarity then becomes part of the interpretation.
Keep relevant tasks and recruitment criteria reasonably consistent when comparing versions, and document any differences. If one round includes first-time users and the next includes experienced administrators, improved performance cannot simply be attributed to the design.
Small qualitative rounds can support focused problem finding. They do not provide a universal sample prescription, and a problem’s absence in the next few sessions is not proof that it has disappeared. Measurement across versions may need a larger study, defined UX metrics, and an analysis plan suited to comparison.
Allow the question to get bigger
Iteration can make an experience easier while leaving its underlying purpose unexamined. If participants repeatedly question why they must grant a permission at all, another wording change may offer diminishing value.
Reserve time to reconsider the wider problem when the evidence points there. That might mean exploratory research into how responsibility is shared, or a different service design altogether. The strength of an iterative approach is its ability to change the next move, including when that move is more substantial than another version of the same screen.