People don't always know what they are talking about.

Managers don't always know the actual detailed behavior of workers.

Future work with new technology can't be completely mapped out in detail.

Some requirements are impractical, and are only recognized as such when they are fleshed out in detail.

The project team becomes "too" familiar with details. They lose vision of the basic project success.

The project team loses or never had the perspective of typical workers or customers.

Strong project leadership that always bangs the drum for simplicity.

Awareness that over-complication kills projects, wastes resources, and reduces technology effectiveness and usefulness.

"User" contacts and management that are disciplined and focused.

A shared and simple vision of success in terms of customer actions and worker productivity.

For very large projects, planned implementation of several small phases. Avoid one giant implementation.

A foundation in reality -- Actual observation of typical customers or workers early in the scope phase.

Reality check -- Early feedback from users on design prototypes before coding starts.

Reality check -- Usability testing with actual users before implementation.