Re: User friendly is what you get used to

[jimmy -at- breck-mckye -dot- com]

Sure it is. And yes, internal users can't reject your product for lack 
of ease-of-use. Just a few questions, though.

1. How long is the boss willing to endure errors whilst the users 'get 
used to things'? How much of the company's budget is that going to cost? 
What are the financial, opportunity and personnel costs of those 
mistakes?

2. How much goodwill of his or her colleagues is your boss willing to 
sacrifice? How much resistance will a poor product create to other 
procedural changes, or other attempts to improve process with new 
software?

3. If upper management request changes to the application, how much is 
your boss' project plan going to be disrupted by having to factor in new 
development time? Given that post-release changes are more expensive 
than alpha-stage improvements by a large factor, how happy will the 
organization be if these changes cause the project to go over-budget?

If your boss is willing to endure these costs, or the nature of the 
organization is such that any of these costs would just be accepted with 
a shrug, my fourth question is: Are you going to stand for this?


On 2012-12-21 18:38, Kat Kuvinka wrote: