I’d suggest that communication is just as important as technology skills. Most end users and people paying for the technology don’t naturally understand the problems and challenges. These things need to be be explained clearly, in a way they can understand.
One of my favorite quotes that illustrate that is from the movie Boiler Room.
“There is no such thing as a no sale call. A sale is made on every call you make. Either you sell the client some stock or he sells you a reason he can't. Either way a sale is made.”
Communication is often thought as a speaking skill I would add that listening is a skill as well —- equally as important, if not more, than speaking. I’ve see so many bad designs because the developer failed to listen to, and fully understand, what the users really wanted.
You are absolutely correct. Over the course of a few phone calls and some simple diagrams, my team managed to shrink what looked like 18 months of effort for 10 people, down to 2 simple, 3 week projects for 3 people. It wasn't wizardry...it was communication.
Your overall point may be valid, but I don't like your Boiler Room quote. If you call me to sell me some stock, and I don't want to buy it, no, I don't have to sell you a reason why I won't buy it. I'm not buying; I don't need to tell you why; and I'm done talking to you now. Click.
One of my favorite quotes that illustrate that is from the movie Boiler Room.
Communication is often thought as a speaking skill I would add that listening is a skill as well —- equally as important, if not more, than speaking. I’ve see so many bad designs because the developer failed to listen to, and fully understand, what the users really wanted.