December 4, 2016
Raw nerve
Yesterday’s email with the Seinfeld clip of the indecisive carpenter really touched a nerve.
In case you missed that message, here’s the bottom line:
Developers should not ask clients for their input on implementation details.
Here are some questions I got back:
- “So, clients should not be involved?”
- “I just do my job without asking do they like or not?”
- “But what if I do a scope of work for 3 days and then they say: ’I don’t like it, change it’?”
- “When the carpenter went off and made all the decisions himself, it turned out to be way too much.”
- “I’ve had quite a few clients come back and say ’I want this button to be red’, or ’I want this button to be bigger’. Should I just do as they say or try to push back?”
I completely understand where these questions are coming from. I’ve been there.
And it was hell.
I’m in a new world now and I want you to join me. It’ll be better for you and it’ll be better for your clients. You’ll both profit more from working together.
The mind shift that I’m suggesting here is huge. It’s a fundamental change in perspective.
For the next few days, I’ll do my best to articulate the mechanics of what I’m getting at here.
Understanding this concept is at the root of making the shift from selling your hands to selling your head.
If what I say is confusing, seems crazy, or angers you, please reply with questions and I’ll do my best to clarify.
Yours,
—J