The problem statement is the best technique to solve a problem. There are a couple of ways to solve a problem but what I like is just filling the table for your design or project. I know you are thinking that this is an easy technique. I totally agree with it but trust me it's still very powerful to make sure that all of the users of your project or a product working for the same goal not different.
It takes time to get to results and make sure good results to gain agreement on the problem is solving may seem like a normal step. For example, let us say one of our clients, a product manufacturer, wants an upgrade in Its system, which helps him to provide the financial reporting among the company and its dealers. They want to improve their communication with dealers.
An operation in reaching a consensus on the problem being solved enlight. The development
team–defined solution visualize a powerful new system that provided better financial reporting,
improved invoice and statement formats. One more thing, the team finally expected to
provide the capacity for automatic funds transfer between the
company and their dealers.
Now let's recap it.
During the problem statement exercise, company executives had
the opportunity to provide information. Management's vision was considerably different. The primary goal of the new system was to provide automated funds transfer that would improve the cash flow
of the company. After a loud discussion, it grew clear that the first problem to be addressed by the new system was electronic funds transfer; e-mail and other dealer communication features were thought simply. Unnecessary to say that, there was much adjustment of the objectives of the new
system. This orientation also triggered the development of a different system design and architecture than had been focused on, complete with the security capability consonant with the risks implicit in automatic banking.
0 Comments