Start with the decisions
In 2024, I worked on a React profile editor where the role determined which categories the form needed to show. It also had a city field backed by an API. A request to move Current City above Username got me thinking about how field order, required fields and underlying rules fit together.
I now start by asking what a person needs to decide and which answers depend on earlier ones. If options come from a service, I also ask what the person can still do while the request is loading.
Walk through a change of mind
If someone changes their role after choosing a category, the interface needs a rule for that old selection. The same rule needs to make sense in the visible form, the validation message and the saved data. I use a short state table to work through those cases before implementation.
Review what survives a failed save
I walk through an ordinary save, then a few changes of mind. I switch a role, change a dependent field and check what the form keeps after a request fails. Those are the moments that tell me whether the design and the implementation agree.
