Monday, July 23, 2012

Question, Listen, Discuss, Debate and Learn


Much has been written both here and elsewhere about the continuum of communication. That is to say, good communication practices encompass a back-and-forth exchange of information and ideas where the manager is questioning and listening as much as or more than speaking and conveying information.
      But if listening and seeking input is so important, why do so many managers fall short in that department?
      I suspect the short answer has to do with finite time: managers have much to do and not enough time in which to do it. So in the communication continuum, it often feels more critical for them to disseminate information and data to their teams, and then move onto the next task.
      Certainly there are times in the typical workweek when that is necessary. But the manager that falls into the habit of justifying the overuse of one-way communication is on track for failure down the road.
      In this era of Twitter, Facebook, email, and text messages, we have become accustomed to taking the easy route when communicating with our teams. An email to all team members alerting them to a change of process or policy is certainly appropriate. But when email blasts become a manager’s principal means of communicating to his/her team, then he/she is no longer communicating. He/she is spewing. Such information downloads fall on deaf ears.

The Team’s Value to the Organization
The reason we build teams of people within our organizations is to achieve the excellence that several people working together can attain that the individual working alone cannot. So it stands to reason that the person managing that team wants to tap into the best that his players bring to the mix.
      Questioning, listening and engaging in proactive dialogues is how the best managers do that. So what exactly does that look like, ideally?
      Again, I add the word “ideally” because we have to be cognizant that the sturm und drang of the day-to-day business can sometimes overwhelm and cancel out the good intentions of striving for excellent communication.
      So let’s assume that the periodic ebb and flow of busy-ness on the job allows for contemplative moments when one-on-one conversations or productive team meetings can occur. The well-organized manager knows best when those times are most likely to be available – first thing Monday mornings; at the end of the billing cycle; before the next production run gets started, etc.
      The wise manger with foresight finds those periodic opportunities and works them into the calendar. Those times become the most valuable of the workweek or month. When the manager and team members are prepared, much can be accomplished, and the ball figuratively moved down the field.

Preparation is Key
Preparation on both sides is critical but means something a bit different, though it follows parallel tracks. The manager, in particular, should come to these regular meetings with an open mind, ready to hear and learn things he may not expect, as well as a desire to discover and discern specific information related to issues of the moment, in particular the current challenges and opportunities the team is dealing with.
      A significant component of the manager’s preparation is staying plugged into the larger organization and the outside world that impacts the business as a whole. He/she should be able to bring that information to his/her team and make it relevant to their day-to-day efforts.
      These meetings are also chances to reflect together on how their unit might work better with other units, how collectively they can contribute to the organization’s larger purpose. To that end, it is the manager’s responsibility to bring in the outside view that is not regularly conveyed into the confines of a unit’s figurative walls.
      For their part, the employees’ responsibility is to come to these discussions with ideas, insights and open minds. Their preparation is best achieved over the course of doing their jobs, making note of problems that recur or opportunities they sense are not being fully exploited. These are the gems that the alert manager with good listening skills looks for and hopes for.
      At the same time, the manager encourages the sharing of bad news along with the good because he/she knows that responding negatively to the employee who brings the bad news will only discourage others from doing so in the future, which in turn leads to small problems festering into insurmountable crises.
      I fear that the typical team meeting consists of a manager speaking for a short time, concluding his/her remarks and then asking whether anyone has any questions. Hearing none, everyone returns to work. The result is that employees often feel purposeless and a mere cog in a machine, disconnected from the larger operation.
      It is far more effective to allow the team to learn together with the manager posing open-ended questions that force them to think through a challenge or opportunity and arrive at their own answers. They then share those answers and begin a discussion and debate.
      Together, the team learns while often coming up with practicable solutions, or uncovering new ways of looking at and thinking about challenges and opportunities. At the same time, the individual employee becomes more engaged in the business, feeling he/she is an active contributor to its larger purpose, and that his/her voice is heard. It’s all good. It’s effective communications.

Wednesday, July 11, 2012

Learning Outside Our Comfort Zones

Every business organization consists of people with assignments appropriate to their skills: marketers, engineers, accountants, salespeople, etc. They are hired for their experiences, expertise and talents in their particular field.
      So is there any value in having them learn about specialties outside their own area? Are there benefits for a software company, say, in having its graphic designers, salespeople, and marketers learn how to write computer code?
      The snap answer would be, “No, it would be a waste of time.” But one software company CEO felt differently and began to do just that, launching a program to teach every employee JavaScript programming language, enough so that after a year each would be able to develop a product that could theoretically be integrated into the company’s software.
      To what end? Certainly not to improve or expand the companys product offering. Why, then?
      Michael Jaconi, CEO of 60-employee FreeCause, explains that he did it because he felt it “would facilitate more efficiency, bring teams closer together, and ultimately make our company perform better.”
      This is not a full-immersion course, intent on creating a back-up engineering team for code writing. Rather, the firm devotes just a few hours each week to lessons, plus lunch-hour “boot camps” led by company engineers. The program expects employees to be knowledgeable and moderately proficient after a year.
      So has this been yielding the expected benefits? Apparently so. According to employees interviewed for a Boston Globe article (“Software company wants all workers to know code,” July 11, 2012), internal meetings now take less time because fewer technical explanations are necessary. Time saved with shorter internal meetings creates “found” time for other more productive work related to one’s expertise.
      One sales executive says that his new coding knowledge enables him to better explain product attributes to clients instead of bringing an engineer into every customer meeting for technical explanations and insights.

Investing “Found” Time
Left unsaid is the fact that, instead of bailing out an uninformed salesman, that engineer is able to devote more time to what he does best – a far better investment of his (and the companys) time.
      As I read about this and thought about its broader implications, the secondary benefits became obvious. For instance, because technology has become such an integral part of our lives, and continues to expand in that regard, it often creates barriers between technical and non-technical people inside companies.
      The non-technical side of the population, among which I count myself, knows that having a basic understanding of a relevant technical topic goes far in helping us do our jobs more effectively, especially when we have to interact with technical people or clients.
      We also have a better appreciation for the challenges and achievements of our technical colleagues.
      There’s an ancillary benefit for the individual employees, as the article points out. “At the very least, [employees] realize that knowing JavaScript makes them more marketable. ‘It’s another resume builder for me,’ said the director of accounting operations.”
      In addition, learning something new as a group, exploring an unknown field together, creates bonds among employees from different parts of the company, thereby building camaraderie and morale.
      It also gives employees a new understanding of and greater insights into the company’s products. Imagine the value for marketers, charged with creating and building product awareness among target customers. It’s not a leap for them to appreciate the full import and market potential of a new product. Similarly, as marketers, they are better able to talk with technicians about expanded market opportunities that an upgrade or product line extension might yield.
      This needn’t be limited to non-technical people learning technical subjects. Why not the other way around, too? Why not teach basic marketing or some other aspect of the business to the software engineers?
      And it needn’t be limited to software companies and code writing. No matter the product a company sells, there is a technical product research and development side of the business. Helping others in the organization learn the rudiments of the technical side, and vice versa, goes far in breaking down the walls of misunderstanding and ignorance that can develop in most organizations, in turn helping those organizations thrive and grow.
      At its heart, this kind of activity improves internal communications in the organization. And any time people with a common mission are better able to understand one another and better equipped to talk on a range of relevant business topics, it always accrues to the benefit of the business and, by extension, the bottom line.