If a picture (wireframe) is more than 1,000 words, a prototype is more than 10,000 words! Prototype is a wonderful technique to engage stakeholders in the development process and to validate requirements. Many organizations and business analysts shy away from prototyping for reasons such as ‘I don’t have time’ or ‘there is no budget’. Of course prototype doesn’t come free. It has a cost associated with it. But by not doing prototyping, I will end up spending lots of time, money and resources to rectify misunderstood and wrong requirements after implementation. As business analysts, You and I are good in building a castle out of thin air (abstract thinking)! But not our stakeholders. Our stakeholders are relatively concrete people, meaning if you allow them to play with a software or a machine, they will come out with lots of improvement suggestions. That’s what we want to replicate by doing prototyping at the upfront of developmental process.