Prototypes are questions. Ask lots of them.
The best way to have a good idea is to have lots of ideas.
Linus Pauling
List the problems with current solutions and how your version will address them.
Remove friction
If a user is filling out forms on mobile make it easier to do with less friction. Have 1 question per screen instead of a scrolling form of all the questions / answers. Have the answers be large and easy to click.
When the user selects their answer dont make them also tap a ‘next button’. Have the form instead move to the next question. You can provide a back button at the top so the user can fix mistakes.
The user is unlikely to make many mistakes and wont use the back button much. Every single answer requires moving to the next screen, so remove that friction of the extra tap.
No matter how cool your interface is, less of it would be better
A key path is the pathway through the interface that the persona takes with the greatest frequency.
Obey standards unless you have a damn good reason not to.
Identify and Catalog Requirements
Requirements consist of objects, actions, and contexts. Example:
Call (action) a person (object) directly from an appointment (context).
When Jobs started talking about the iPhone on Jan. 9, 2007, he regaled the audience with myriad tales about why consumers hated their cellphones. Then he solved all their problems - definitively.
The New York Times