Notes
Writing the decision before drawing the flow
Describe what a person decides and with which information before counting screens.
Not adding the empty state later
An empty state reveals first use, data model and next action at the same time.
Choosing the right prototype fidelity
If the question is about movement prioritise interaction; if it is about trust prioritise content.
Naming a component by its job
Names tied to shape age as systems change; functional names travel further across teams.
Levels of evidence in design critique
Label observation, assumption and preference separately so the team sees what needs testing or deciding.
A state matrix for developer handoff
Loading, limited permission, error and partial data belong in the same matrix as the happy path.