Defining Software and UI Requirements Is a Broken Telephone Game

November 29, 2012 Business Processes, General

Defining Software and UI Requirements Is a Broken Telephone Game

By Julia Salem

November 29, 2012

UX Magazine has recently pointed out the fact that defining software and UI requirements has become a lot like the broken telephone game we used to play as kids. “One person whispers a message to another, which is passed through a line of people until the last player announces the message to the entire group. Errors typically accumulate in the retellings, so the statement announced by the last player differs significantly, and often amusingly, from the one uttered by the first.” In organizations, this happens when requirements are passed from customers, to business analysts, to UI/UX designers, and so on.  Find out how we can reduce the broken telephone effect by reading the full article on UX Magazine.

Repost this on Twitter.

Has your organization ever experience the broken telephone effect? Let us know on Twitter @OxfordTech and on Facebook.