While there was a time when this was a prefered method, in an agile workflow there should be many iterations between design, business stakeholder validation, and development. These are living, iterative documents that should be treated as current or historical versions. It is best practice to avoid adding a suffix of ‘final’ to any of these designs.
When creating High-Fidelity Designs, the problem you are trying to solve, and who will be viewing it, will help define how you will create these designs.
- Components - Depending on the scale of the project, there will be items that make sense to group together in terms of visual style or intended use. These are usually components. They can be global items like navigation, and headers and footers, but can also be forms or input types. They are commonly reusable items that users become accustomed to and developers reuse in code. They can be created as reusable symbols in design creation tools such as Sketch.
- Single screen - If you need to see how a component fits into a page flow, or show the experience of an entire screen, you can bring together individual components into a larger flow. Depending on what this page is built for, it may be tell a complete story of how a user would use a product, or show how an application could look in a given state.
- Flow of experience - Depending on the complexity of the feature or problem, you may need many different pages to visually represent the solution to the problem. These pages may be put together in a document for a stakeholder or moved to a clickable prototype to test in context with users