Creating low-fidelity prototype designs that are for user testing and customer buy-in
Create paper prototypes in conjunction with user and project owner
Paper prototyping is an effective, inexpensive, and quick way to begin the design process. Designers may misunderstand the verbal descriptions given by owners, users, and other stakeholders. When designers create hand-drawn interpretations of the gathered requirements, users and stakeholders are able to see what the designer is envisioning. They are also given the opportunity to confirm or reject the design decisions. Paper prototyping allows your team to "fail fast and fail cheap" by highlighting what needs have not been met in the early stages of the design—and because it is easier to abandon the paper iteration and try again. Stakeholders enjoy paper prototyping because it allows them to see that their input is valued.
Test paper prototypes with users and adjust as needed
Users are able to understand the flow of an app with paper representations of screens. It doesn't take long for problems to be identified. A tangible representation of the workflow and design makes it easy for users to spot the things that confuse or frustrate them. They are usually happy to explain what doesn't work for them and why. This early-stage feedback can be used to revise the designs before engineers start to work.
Once the needs and wishes of the users have been consulted it is important to get the engineers' feedback on the design on whether it is feasible and how long it will take to build.
Present recommendations to project owner for approval or rejection
Ideally, the Domain Team will recognize the value of user feedback (gathered via thorough research and testing) and accept the design that incorporates that feedback. Ultimately, the project owner is responsible for signing off on the design points. Formally acknowledging their right to do so helps with keeping projects on time, within scope, and on budget. In the Agile process, the project owner must be available to make these types of final decisions on a regular basis
Repeat as needed
Remember, the key is to make hand-drawn screens that represent the workflow of the app. It may take creating several versions of the paper prototype to discover what works best, but that time is well spent if it prevents future expensive changes and/or design failures. User feedback should convince the project owner to approve design decisions based on data, not a "gut" feeling.