A conversation can contain useful information in the form of examples, frustrations and repeated questions. I look for the needs behind those observations before turning them into interface or visual decisions. The first phrasing is not always the underlying requirement.
A short written summary helps check the interpretation. It can distinguish confirmed constraints from ideas that still need discussion. This gives the next design step a shared basis without pretending that every informal comment has become an agreed specification.