Throwing requirement documents and wireframes "over the wall" often fails when it comes to even fairly complex product and service production. See how you can use prototypes to fill the void.
- Modern businesses use a variety of strategies…to bring great products to market quickly.…To do this, many of them leverage outside help…from design consultancies…and use near or offshore development.…Some use in-house strategies like remote production teams…and separate engineering groups.…So they'll often hand over to another team…the requirements that inform the design…along with detailed design documentation.…These are created in an effort to ensure success…by defining as much as they can…and writing an illustration before something is produced.…
Unfortunately,…handing over design documents to another team,…even detailed designs like annotated wire frames…frequently fail to convey the idea in design intent.…Even when they produce what was intended,…they're committing several weeks,…if not months to developing it…and given that those ideas…and documentation are likely completely untested,…they may not provide an adequate solution…or fail all together.…Prototypes can convey the entire breadth of a design…including the concept, interaction model,…
Released
9/26/2016- The four categories of prototyping
- Choosing the right approach
- Deciding what to prototype
- Generating ideas rapidly
- Documenting and conveying
- Using simulations
- Creating objects
- Making a prototype
Share this video
Embed this video
Video: Convey: When requirement docs and wireframes fall short