[iforgotmypass]

Or read about agile user story mapping, user personas, user stories and write your requirements that way. If that is not enough - get a UI/UX designer who'll translate your requirements into interactive prototypes which will somewhat serve as requirements for the developers.

[brittpart_]

Right now, we're moving into the second iteration because the first application was sooo hard to use lol that's on me.

This time, I'm starting with wireframes, then clickable prototype to show the show and then I'll write a spec sheet for like search and upload.

Do you think requirements can be written in plain sentences or should they go by component/user story/functionality/requirement in a spreadsheet?