Comment It could be your attitude or it could be... (Score 1) 361
I've been a developer for over 10 years and I can say that in most environments, there is a divide between tech and the rest of the company in almost every situation.
If you're struggling to communicate with other devs or your supervisor, that's a different issue.
First, an agile process, where you define user stories and commit to work in sprints, is a great communication method that integrates with your work flow. From a top level, you define the business need, then breaking it down with tasks being more technically oriented. This adds a great deal of transparency and gives the business side something written in their language that they can review and track.
I've found that my personal communication issues stem from getting too caught up in substantiating everything. As a developer, there is a highly technical, logical discourse that can be had about anything you work on. Knowing how to communicate this simply, for non-technical employees, goes a long way, but can be a challenge. When I see someone getting lost in my words, I take a step back and give that individual control of the conversation. Then, I work with that person to help them understand the topic at-hand in a more constructive way.
The other thing is, remember to listen... take notes during conversations and don't just wait for your chance to speak. Communication is really about simply finding a shared perspective to explore.
The golden rule is that technology supports the business, not the other way around.