In the last 12 years that I have been developing software probably the most frequently articulated criticisms I have heard are:
“Software developers don’t understand business” or
“Software developers can’t communicate effectively”
There may be some truth in that. I’d be the first to admit that if a software developer starts suggesting that we put our XML in the CRM so that the DTS can use the API - any sane business user would be lost.
However, for the last 12 months I have been running my own Microsoft Gold Partner software development consultancy .I've had to learn all sorts of new skills in sales, marketing, business development etc that any self respecting software developer would run a mile from.
That said, I am pleased to report that developers don’t have the monopoly on talking gobbledegook. Consider this piece of advice that I recently encountered in a Microsoft Solution Selling course that I should:
“Target the optimal opportunity entry point”(sounds painful!)
And utilise the
“Initial pain chain”
What’s more - I recently received an email from a “greatprojectmanagement.com” that advised me that I should:
· Establish a radar. Be aware of the ’states’ of others and mindful of what you may be assuming
· Use pacing. Mirroring others in breathing, body language and phraseology
· Adopt a neutral position (e.g. tempo) while calibrating others
· Match people’s interests. Personal, Professional and Project related
It’s no wonder so many software projects end in failure!
Excellent software is developed by teams who have great commutation, a common understanding and a shared purpose. That starts from dispensing with the “corporate speak” and building a foundation of open and honest communication.
We are all real people, with real lives, families and friends and problems. Simply treating our customers and fellow employees with honesty, integrity, respect and common courtesy would be a great start.