#2 Documants needed

[Matt B]

In order to know the way to progress it would be best to know the target.

Speaking as a systems analyst for a moment I would like to know

-Who will use the system?
-What do they use now?
-What is good about what they use?
-What is weak about what the use?
-What are the primary needs of the future users (why do they use what they use now)?
-What is the nature of communication betweem users of the current system (document flow)?
-What are the limits and redundencies of the current system?
-What is the format of the current system (how should the new UI be designed)?
-What are the main strengths of the current format (what should the UI keep)?
-What are the weakness of the format *what does UI need to improve on)?
-How does the current system meet the needs of the users?
-How can it be improved?
-What is the level of skill expirence of the users?
-When do the users need the new system?
-Where is the future of the users? What areas are they most likely to need to scale, expand or extend in the future?
-Why would the users need a new system? What new benifits can we add?
-What are the targets that when met will show that the project cycle is done (When do we stop).
-If we have done this before what was good, bad or indifferent aboutt hat prior project?

Having answered these questions: (now I'm being a product developer)

-What other projects answer the needs we have identified?
-How well do they meet the need?
-What are they not doing that we can?
-What are they doing that we should not?
-What will our USP be? (Unique Selling Point).
-What can we do to be better, smarter, faster and more "wantable" (yes it is a silly word) then the other projects?
-How will we ensure that we scale better than any other?

Once we have compiled the answers to these questions (some of these questions could take upwards of 3000 words to answer fully) we have a full map to follow and have removed almost totally the chances of purpose drift and reduced the chances of feature bloat and the unending BETA.