[IxDA Discuss] (no subject)

[pauric]

If you are looking to persuade management as to why they should properly
define users then maybe suggest some of the pitfalls of an undefined set of
requirements, such as scope creep.  Having focus will also aid
collaboration, through reducing the various debates that will inevitably
occur, as people put forward seemingly valid views on what their version of
the 'user'. User definition helps management evaluate feature priorities,
discounting some 'nice to have' options that are in fact not necessary and
generally keep resources allocated on core functionality.

It might be worthwhile citing gmail, google defined 6 types of mail user.
Their product is recognized as being best in class.  They released a focused
product and have built upon it since then in a calculated manner.  They did
not try a one size fits all on day one.

However, its important to remember that user definition does not mean the
end product will meet real user's needs.  Its important to start small &
focused and then build upon feedback after the product is released.