When You Suspect the Customer Might Be Wrong

0 Votes

When You Suspect the Customer Might Be Wrong

I recently worked in a project where the requirement came from a client who wasn't very knowledgable about technology. The initial requirements were vague and contrary to subsequent, ever escalating requirements after a quote was made and work was well underway.

For example, intially a client insisted there was to be no multi-document interface and no tool strips or buttons, as they were far too complicated, against my advice. During development, he changed his mind and insisted on them.

My question is, when you receive requirents that you don't think the client really wants/ needs, how do you tell him he is wrong, or how else do you handle it.