Too many software projects fail because the people who will use that software had very little input into its design. For some things this is unavoidable and often unfeasible, but for smaller, niche systems it is simply overlooked. When user feedback is overlooked, the end product may end up failing to achieve all of its objectives and its effectiveness diminished.
Getting users involved at a very early stage helps steer a new system in the right direction.
If the software project is to replace an existing system, getting the feedback on what users do and don’t like about that existing system is vital. This information can help shape the requirements and allow the new system to make a positive improvement in vital areas.
One of the best ways to get users involved is to create interactive prototypes of new systems, well ahead of build time. Let the users try them out for size. Collect their feedback. Use that to shape revisions of prototypes and repeat the process. After a few iterations, and with some care and stakeholder commitment, you’ll end up with a more viable design and (crucially) you’ll have better user buy-in, as they’ll feel that you’ve listened to them and involved them in the design of what will be their system.
