Tuesday, July 26, 2011

Communication Tips


I discovered some tips on relationship communication skills, some of which I think apply in the business world.  The article references active listening but I really found the section with 8 tips to encourage someone to say more; as a useful section.  You can see the site here.  The first three bullets points are useful to me.  It is important to let someone finish what they’re saying at work because you don’t want to say something prematurely and sound like the bad guy if you’re wrong or if you have misjudged.  I always feel like giving someone space and asking questions goes a long way, the tips say not to act as if you’re interviewing.  This is an excellent point because let’s face it, interviews are stressful to most people and ultimately the goal is to have a flowing conversation with information give and take; not a question and answer.

I find that the best way to get information at work is to ask for it then let the other person do the talking.  The tips I outlines from this article are for in-person conversations mostly in my opinion.  A lot of the more difficult information seeking I do is from in-person conversations.  I need to be able to communicate effectively, and if that means to get the other person talking by asking question then it is effective.  If I really focus on the conversation at hand and wait until he/she is completely finished before offering up my words then the whole situation is much better.  Even when I admit being wrong or confused, it usually makes the whole conversation more beneficial.

Tuesday, July 19, 2011

Statement to Staff

Staff,

Our workplace environment is constantly being bombarded with changes which ultimately affect our everyday work lives.  We must continue to satisfy our customer needs while keeping in mind that changes in the agricultural marketplace and sudden changes in interest rates weigh a heavy toll on our customers’ lives.

Our overall goal as a company is to move in a common direction towards the “top of the pyramid” by driving the value of our services and continued strong foundations in technology.  Becoming a strategic business partner with our customers will create the ultimate give and take relationship for growth and superiority in the market.

We need each individual to take ownership in their own careers.  Everyone here has been given full control to own something.

Every person here has been given full ownership of their own careers.  Own something by following an issue or enhancement from start to finish.  Lead a team or implement an improvement for our customers.  Change is not something to fear, it is part of our changing market and we need to keep up to reach the TOP.

Thanks.

Monday, July 11, 2011

The good and the bad communication


There have been quite a few organizational communication mishaps and victories at the place I work.  Depending on how you read my little story you might think there was a failure or something good happened.

A new-ish project manager recently had a very successful and well received (by the customer) deployment of some applet-type enhancements for a piece of my company’s software.  The CEO decided to ask the project manager to write up a brief 1 pager about the implementation, testing, overall strategy of the project.  This turned out to be a 4 page presentation, but anyway…a group of people including myself were called into a manager-type meeting to have an open discussion on the process.  The meeting was supposed to take 30 minutes, ended up about 70, and it included about 25 employees.

After some solid discussion (which included) bickering and yelling between the CEO and one of my fellow employees we finally came to a conclusion.  The CEO waved his hand and magically created two groups of people each with different tasks but with the goal of implementing “agile development” in my workplace.  Agile development was never mentioned or hinted at in the document written up by the project manager, but it was rather insinuated after our group discussion as a necessity for better deployments going forward.

This was bad because:  the meeting took longer than planned, people shut up after the CEO and one employee started yelling, two more tasks groups have been added to the countless other committees, groups, etc. of people trying to get work done.

This was good because: ultimately we have two groups of people who need to work towards implementing agile development.