Re: Tempering Client Expectations (OT)

2010-04-12 Thread Mark Lawrence
[Big snip] Heh, my wife and I joke that in those "can this marriage be saved" newspaper columns, every answer boils down to "communication is key". Keep the customer tightly in the loop with regular communication -- frequent feedback regarding progress, costs, and whether your shared underst

Re: Tempering Client Expectations (OT)

2010-04-12 Thread Victor Subervi
On Mon, Apr 12, 2010 at 10:29 AM, Tim Chase wrote: > your own inaccurate assumptions and answer those, please. >> > > > Heh, my wife and I joke that in those "can this marriage be saved" > newspaper columns, every answer boils down to "communication is key". Keep > the customer tightly in the loo

Re: Tempering Client Expectations (OT)

2010-04-12 Thread Tim Chase
On 04/12/2010 06:37 AM, Victor Subervi wrote: On Sat, Apr 10, 2010 at 3:14 PM, Tim Chase wrote: 1) Preeminently, address second-order ignorance. [elided kvetch] "second-order ignorance" is a technical term (not intended so much as a slur) for "not knowing what you don't know". If you google

Re: Tempering Client Expectations (OT)

2010-04-12 Thread Victor Subervi
On Sat, Apr 10, 2010 at 3:14 PM, Tim Chase wrote: > 1) Preeminently, address second-order ignorance. Tim, throughout this post, you're way out of line. The s/w I have already built for this client works just fine. It's not a matter or not having the tools or not knowing how to use them. Pay atte

Re: Tempering Client Expectations (OT)

2010-04-10 Thread Tim Chase
On 04/10/2010 11:10 AM, Victor Subervi wrote: Hi; I'm working with my first client where I've developed a custom script. I way underbid the project and I ate that as part of my learning experience. We outlined as precisely as I knew how what functionality was needed. Then he went to input data an

Tempering Client Expectations (OT)

2010-04-10 Thread Victor Subervi
Hi; I'm working with my first client where I've developed a custom script. I way underbid the project and I ate that as part of my learning experience. We outlined as precisely as I knew how what functionality was needed. Then he went to input data and lo and behold he needed more functionality. I