In a slightly 'other view' opinion: As a technical person in a certain field, one shouldn't expect clients to know half of these things, or even to take account of them (even though in most fields, if you change your mind about you want, the result is likely to take longer).

Thus, in your first contact with a new client/customer, these things should be laid out in the original contract, or whatever it is. Even with less formal, 'internal' clients, effort should be made to make sure these things are clear. Write them down, hang them on your door, whereever. Thus, when such a problem comes up, you can point to that document, and say 'yes, sure we can do that, but, it will take longer..'.

Another item:

C.

In reply to Re: OT: Project clients by castaway
in thread OT: Project clients by simon.proctor

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.