Some insights into implementation can be found by considering the procedures implemented by Edmark, an educational software company.  (Educational software provides the same function for children that a DSS does for managers.  Good educational software helps children discover opportunities to learn new concepts, identify how those new concepts are similar to what they have used in the past, determine what they need to know, discover how to apply that information and help them make appropriate decisions about how to move onto a new topic.  Hence, some of the same design principles can be applied to both kinds of effort.)

Of course, the programmers test the software to insure it works.  However, in addition, the son of the CEO and the CFO, as well as some of their friends, also test the software.  In fact the CEO’s son began testing the software when 5 years old.  These software “testers” represent the children who ultimately will be the users of the system.  If they cannot use the software, find errors in the functionality, or find the procedures kludgy, it is redesigned before it goes to market.

Similarly, the company employs mothers of young children to spend time in stores explaining its products to clerks and customers.  In this way, non-threatening facilitators can adapt the assistance and information they provide to users appropriately.  Since users better understand how to use the product, they are more satisfied in its use.