Agile + Iterative Prototyping
An iterative design process complements agile development, allowing both to evolve in accord.
Low-fidelity to explore solutions
These prototypes are typically static in nature, and allow us to address the entire design before we dive into granular functionality.
Hi-fidelity to solidify those solutions.
Ensure that what we build addresses every requirement and enhances the experience for all end-users.
Explore, Test, Code
Prototypes are tangible, living artifacts that facilitate succinct communication among all designers, developers, and stakeholders before the product is released to the wild.
Explore high-level concepts to champion legit formative design feedback.
When starting the design process, it is important to be open and exhaustive of all available options that best serve the design. This part of the process requires significant trial and error in validating ideas and ensuring the design captures the end to end requirements needed for a successful outcome. Low-fidelity prototypes fit well in this phase by allowing us to communicate about the design purpose at a high level before it becomes time to flesh out the detailed aspects required to make the design function.
These prototypes provide a means to explore nuanced design functionality.
Once our teams come to a consensus on the low-fidelity proposed ideas, we move into high-fidelity prototypes to begin plotting out the consistency of design standards and interactive elements required to make the design work. This also involves plotting out common user journeys the design accommodates, and ensuring that each user type is able to leverage the design to carry out their tasks.