NT 4.0 Anticipate User Needs with the Solutions Design Model Research studies have shown that one of the key factors in designing a successful business solution is the consideration for, and involvement of, users throughout the design process. Unfortunately, user involvement in development projects can be difficult to manage. Users are resistant to change. They don't want the new technology and will not get involved in its design. Users have different opinions of what the new system should include and have different preferences for the color and layout of screens.
Users ask for a feature, but when it is delivered they want something different.
The project is almost complete, but it may create more workflow problems than it solves. The application specifications aren't changing, but the business is, and you can't track with it. The project solves a lot of your infrastructure problems, but people refuse to use it. The application is complete, but high help-desk costs make a full deployment doubtful. This model ties together the Microsoft Solutions Framework application, team, and process models, enabling information system staff to focus resources where they can produce the most value.