Tag Archives: Communication

We’re always selling

Walk into your next management meeting and tell your team that you think they need to learn to sell better, you’re likely to feel a chill enter the room. Sales has a tough reputation inside organizations. And yet, so many core skills from the art of selling apply perfectly to the interactions we engage in day to day.

This week on the show, Howard Teibel and Pete Wright discuss how we are always selling something, whether it’s a project idea, a need for partnerships among business units, or influencing a group to buy into a new direction. Selling is ultimately about listening, then conveying how your idea meets another’s need. It’s about great communication and negotiating skills, something all of us can continue to improve on.

Listen now…

Audio MP3

Subscribe to Navigating Change iTunes

 

Stop Doing and Start Helping!

There is nothing more arrogant than walking into an organization, assessing a people or process issue and believing you can single-handedly create a permanent solution.

The failure in most organizational projects is the presumption made about the giver and receiver relationship, the giver being those helping with the change and the receiver, those inheriting the change. The three most important presumptions are:

  1. The receiver is asking for the specific advice given
  2. The receiver is open to the advice, diagnosis or solution offered
  3. The giver understands enough of the problem to give this advice

These may seem like fair presumptions but more often than not, advice is given on incomplete information and both sides do not have a shared view of the problem. The problem doesn’t get fixed, the recipient doesn’t own the solution and the blame game for a less than satisfactory solution takes center stage. Sound familiar?

The Missing Piece

The first thing to recognize is the difference between advice and help.

When I consult with a surgeon, I’m looking for advice, a diagnosis and for that person to take care of the problem. Accountants, lawyers, doctors, architects – these roles are structured around evaluating a situation, applying expertise and doing the work. The person is the means to the solution.

Building a high-performing workforce is different. True success comes down to behavior change.  Positive attitude, teamwork, trust, practice – these skills are the cornerstones of an effective workforce. You can’t talk someone into having a good attitude, exhibiting teamwork or being willing to make mistakes as a way to develop skills – they must want it themselves and be willing to do what it takes to get there.

But it’s so much easier to just give advice and then walk away, you say.

Projects involving people that end up being perceived as unsuccessful stem from an overemphasis of trying to solve their “problem” versus looking for ways to help them help themselves.  At the heart of making positive change stick is asking this question:

“If diagnosing and advising only perpetuates a dependency and lack of self-reliance, how can you help the group take greater responsibility for their problems and solutions?” Focus on ways to get the groups to practice and immerse themselves in the behaviors that will build their confidence to do the work on their own.  Stop doing it for them.

Yes, being an expert is useful but don’t confuse expertise with being helpful. Expertise doesn’t changes behavior. To get people acclimated to a new way of doing something, you must ask deeper questions about how they learn, retain information and are able to repeat this behavior on their own. Whether you’re the sponsor, manager, consultant or colleague, step back and find ways to allow individuals and groups to do for themselves, versus being so quick to solve their problem. Only then will they be able to run with the ball in a self-reliant way.

A great book that deconstructs the “helping relationship” is Edgar Schein’s book “Process Consultation Revisited – Building the Helping Relationship”. This book single-handedly helped me reshape how to think about consulting and make sure the responsibility for change lies with those needing to live with the change.

Stop calling it collaboration!

If you’re helping a group work together, collaboration is not what you’re looking for.  It’s the behaviors that make up collaboration you want to focus on, most noticeably – coordination. 

Coordination can be measured and quantified (who does what, by when and how the work is performed), while collaboration is the spirit these behaviors.  It’s the difference between a vision and a goal.   A vision is where you want to end up while a goal is how you get there.   When someone spouts “let’s collaborate”, trust your instinct and ask them “what do you mean by this?”  You’ll quickly discover there is another layer of meaning that gets to the behaviors you’re trying to influence.

There’s nothing wrong with terms not used in everyday language (otherwise called jargon), except when no one, even the speaker knows what they mean.   Point out these elephants in the room.  It will help everyone get to the intent behind the words spoken.

Raising the Bar on Buy-In!

Asking for “buy-in” to your latest initiative will get you passive indifference at best.  Maybe indifference is what you’re looking for – light years improvement from outward dissatisfaction or hostility.  But if what you really want is to motivate stakeholders (senior management, administrators, researchers, faculty or staff) to your idea, buy-in often only produces a willingness to not go against the initiative. 

Most likely you’re looking for champions or enthusiastic support.  Saying to a group “we’re looking for your buy-in” communicates you want to inform, not involve. The way to get enthusiastic support is if you bring them into the circle by asking for help, feedback, ideas and participation.  Yes, some stakeholders may ask difficult questions.  But don’t fool yourself into thinking that by keeping them at arm’s length with periodic updates that you’ve got their support. 

Too often the bar is set too low around what we can ask or expect of others. For a group to be jazzed about an idea, you’ve got to get them involved in the change, not just inform them what’s coming.

To learn more about how to do this, feel free to contact me.  I’ll be happy to share some of our strategies.
 
Howard Teibel
617 448-3634 mobile

If It’s Not Broke…

There is a certain relief in change, even though it be from bad to worse! As I have often found traveling in a stagecoach, that it is often a comfort to shift one’s position, and be bruised in a new place. ~Washington Irving

As part of a larger strategic effort to improve operational performance across your organization, centralizing business functions can be a very useful change. The rationale behind these projects is that by reducing redundancy, the quality of the work can be improved, processes can be made more efficient and cost savings can be realized.

If only it be this easy. Like many initiatives that include structural and people change, solving one problem creates another. Imagine an army of people sitting in their metaphorical chairs for years at a time, comfortable with what they know and their position in the organization. Centralizing work changes all the rules.

Three guiding principles will help when embarking on centralizing work projects:

1. Getting management on the same page

The best way to create positive momentum on these projects is to have leadership speaking with one voice. Once new roles are defined and the model is tested (ex: a Business Center becomes operational) it is critical for staff to know that management will hold people accountable to their new roles. Without a consistent voice from management and regular reminders of people’s roles, staff will push on the boundaries of their shifting responsibilities, making it much more difficult for everyone to adjust to the new model.

2. Building trust by being inclusive

The process your staff will go through getting accustomed to new roles and responsibilities takes time and requires patience from everyone involved. Management should set up check points where people can weigh in how the new process is working. Asking for feedback and genuinely listening to their ideas and concerns will go a long way to helping build trust. The more people feel they have a voice, the more they will take ownership in the change.

3. Attitude is everything

Two primary groups are affected by this change – those who will be inheriting the work of others and those giving up pieces of their job. Although this can be stressful, at some point people need to make a choice – they’re either part of the solution or part of the problem. This doesn’t mean accepting an unworkable process, rather for all players to ask themselves what they can do to help the new process succeed.

By applying these three principles – Leadership speaking with one voice, management listening to staff ideas and concerns and most importantly everyone asking themselves how they can be part of the solution – this is how you get through initiatives that involve changing roles, responsibilities and reporting lines.

Communicating Bad News

Breaking down communication barriers is no easy task, and it opens the classic question of what comes first, the chicken or the egg? Management is waiting to hear what’s really going on while staff is waiting to hear it’s ok to communicate breakdowns or bad news. (This, by the way, is not the same as complaining, which is communicating bad news with no commitment to action.)

Organizations are often left with the “blame game” being played out over every missed deadline or poorly rolled out deliverable.  Here’s what management needs to realize – your staff will not take the step of communicating bad news unless you explicitly demand it of them. For staff – you may never get explicit permission from management to stop filtering bad news.  The good and bad news?   Regardless of your role, the ball is in your court.

BPMA Write-up

I spoke at the Boston Product Management Association meeting when this note popped up in my Google alerts: BPMA Meeting Roundup for April-June.

The central idea of the talk is pretty simple: miscommunication untreated fosters mistrust. I think of it as an illness; one that starts as a cold, but transforms over time into a cancer. It’s much easier to treat when addressed quickly and openly.

These meetings are usually stocked with great speakers. I’m thrilled to be included in this list. If you’re a BPMA member, make sure to look for the presentation itself in the discussion forums on the BPMA website. Next time, I’ll make sure the notification is up before I actually do the talk!

Welcome to The Trust Blog

As a function of the teibelinc.com redesign, I struggled mightily with a few things.

  1. How to characterize change as both a constant struggle to overcome organizational adversity, and at the same time to communicate that I am a great optimist and advocate that such obstacles can be overcome.
  2. How to show that I believe strongly that the best change projects are not always just about incorporating the new, but putting the same old pieces of the organization together in new, innovative ways.
  3. Should I put a blog on the site?
I think we answered the first two questions. The third will have to come in partnership with you. 

 

I realized that so much of what I do, so many of the stories of change that I come across each day, highlight the companies that are “doing things right” now. They’ve made a commitment to how they focus their people, process, and technology initiatives, and through wonderful feats of ingenuity they have managed great change while reducing the pain that can come with it. In large part, they have done so by increasing the levels of trust and communication between teams, across layers of management, and have delivered results thanks to their efforts.

 

These are stories that more people, more teams, and more businesses need to hear. 

 

And so, I welcome you to The Trust Blog. I’ll be posting my stories of trust, teams, and change, and posting links I believe are of value in your change initiatives. In return, I hope you’ll find this a space where you can share your own stories and interact with me, and your peers, through insightful and observant comments and trackbacks.

 

Thank you for your patience through our redesign efforts, and thanks in advance for your participation on the site. I look forward to hearing your stories of change management success!

Is anybody really listening?

…does anybody really care? Does this sound a little too close to lyrics from a 70′s song? But I digress.

Last month we focused on the risk factors that contribute to project success or failure; Vision & Goals, Planning & Preparation, Capacity & Personnel and Buy-In (www.teibelinc.com/newsletters/Volume5Number9.pdf).

This month we’ll look at the glue that keeps projects from falling apart. In the spirit of non-consultant speak, I’ll simply call this “really good communication”.

Communication is a funny thing. Looking back on most projects, you’ve either communicated too much, too little, but rarely just the right amount.

When you communicate something, three elements are present:

  1. What you intended to communicate
  2. What people heard as a result of what’s said
  3. The unintended consequence of what’s heard

A perfect example of “When good communication goes bad” is the following attempt to set a context for an organizational initiative:

As a result of this financial implementation, checks will go out quicker, better reports will be available to staff and most importantly, we’ll be able to simplify people’s work and minimize the use of other systems to keep track of departmental budgets.

The communication appears to convey great benefit to the institution, and ties it to genuine value for those working there. But what do the people who are affected by this change hear?

As a result of this financial implementation, we’ll be working twice as hard, will no longer have control over the information we’ve taken years to understand and some of us will be looking for work.

Oops!

Managing your listeners

What’s communicated is often misunderstood because the speaker perceives that what’s said is more important than what’s heard. This is the heart of communication breakdown. What people say is rarely what’s heard, even when you have the best communicator delivering the message.

Think of it this way. Everyone has a unique filter that allows certain ideas in and keeps others out.

If I say “you need to better manage your people.“, some hear this through a filter of “thanks for the feedback,” while others hear “my job’s in danger,” while others might think “you don’t know what you’re talking about.” One message, unlimited listening responses.

Consider expanding these listeners’ interpretations to 10, 100 or 500 people. The challenge then becomes compounded with the message going from listener to listener, versus from the speaker directly. These watered down communications have direct impact on the collaborative nature of project work, leading to the next problem.

The Blame Game

Projects fail, or are “discouraging successes,” because an unproductive cycle begins with the deliverer of the message blaming the listeners for “not getting it,” while listeners blame the speaker for being a “poor communicator”. This ping-pong match creates a “virus of discontent” across the organization.

For example, if I were to ask you: “Have your piece of the project ready to go in two weeks.“, you can blame me for not being clear what “ready to go” means and I can blame you for not following through on a simple request.

Taking Responsibility

What’s needed is a paradigm shift away from “who’s to blame” to each side taking responsibility for how one is heard and how one listens.

Management need to take greater responsibility for the unintended consequences of what people hear them say. For example, they may use the phrase “efficiency” while everyone hears “job loss”.

At the staff level, taking responsibility means validating assumptions about what was heard. The underlying dilemma for staff however is an absence of trust between them and management; that it’s REALLY about cleaning house disguised as “productivity improvement”.

If trust is a problem across your groups, consider addressing these issues first. Opening this can of worms may benefit from professional facilitation, a service that Teibel Inc. can help you address. (See Retreat Services www.teibelinc.com/images/organizational_retreats.pdf.)

Listening and Speaking Strategies

Assuming a basic level of trust and a simple need for better communication skills, consider this point of view:

The majority of the time, what you heard was not what was said or what you spoke was not heard by others accurately. If you come from this point of view, you’ll be way ahead of others who are more interested in playing the blame game.

Strategy for someone making requests:

Ask your listener(s):

  1. “What did you hear me say? OR
  2. “What are you going to do?”

Most importantly, don’t assume listeners got the message.

Strategy for the listener:

Tell the speaker one of the following three things, even if unprompted:

  1. “What I’m going to do is…”
  2. “What I heard was…”
  3. “What I didn’t hear or what I am not going to do is…”

For the second strategy, the goal is to help close the feedback loop so the speaker can evaluate in real-time whether what they intended to communicate was heard accurately.

The Bottom Line

Good communicators are primarily great listeners. Great listening takes the extra step of validating what was heard by others, or makes sure that what was spoken by someone else was heard the way it was intended.

Communication is not the message being spoken; it’s the act of two or more parties actively listening to the other for a mutually agreed upon outcome.

On Listening

June Rokoff, Senior VP at Lotus credits her success in turning around the company’s position to building a team that listens: she made listening the culture of her team.

— Glen Rifkin, New York Times

Productivity and Achieving Business Goals: They could be apples and oranges

I think most of us would all agree that if you’ve achieved your business mission or vision, you’ve probably produced a high-level of productivity. But is the opposite true? Does a high level of productivity automatically translate into business success? The simple answer is no.

What’s the difference and why is this a critical distinction for your organization’s success? This is the topic of this month’s newsletter.

Take this example from a Higher Education institution. Imagine a new and improved Grant Submission tool has been identified to help faculty secure research dollars. The current system is a conglomerate of Word, Excel, emails and faxes going back and forth between
administrative offices and departments.

The proposed technology appears to streamline the collection of data into one coherent set of screens and reports. The majority of faculty are loosely aware how the new system will work and have been given an overview of the benefits that this new system will bring. Ultimately the unspoken expectation by all is that it will support the institutions mission. The software gets installed and is ready to use.

The devil’s in the details

On paper, everything looks great. That is, until people actually start using it.

Unbeknownst to faculty, the data entry requirements are greater than expected and the majority of the work ends up falling on their research assistants. It doesn’t take long for a growing dissatisfaction to take hold.

What appeared to be a tool to help faculty meet the institutions mission of world-class research, has instead taken their key resources and turned them into data-entry clerks.

Sold a vision but delivered a tool

Software is all about productivity, i.e., simplifying, streamlining, or automating some series of tasks. Software can be a tremendous productivity solution, minus one small caveat — human involvement and the lack of understanding how it impacts people and processes.

Take email for example. The original promise of email was how we would be able to spend more time at home or on the beach, getting more done with less effort or time. (Can we all agree we’re not there?)

Software is a linear, problem-solving solution that leads to what we think we want, i.e. “productivity”. Unfortunately, productivity is not what we’re truly striving for. It’s achieving the mission or goals of the organization that is what we’re looking for. Achieving vision may involve software, but the real challenge is in understanding and asking broader, mission-driven questions.

Back to our story

Frustrated with the new grant submission tool, a senior faculty member complains directly to the president. What used to be a kluge yet workable set of tasks now has research assistants spending the majority of their time manipulating data-entry screens. To make matters worse, faculty are expected to learn the system themselves to get reports about their grants. This is not what they signed on for and a minor revolt ensues by a few influential teaching fellows.

The unintended consequence of this “improvement project” is that it unfolded as a linear, software solution, versus a means to genuinely support the mission of the institution. In their haste to streamline and simplify work (remember email), the sponsors of the project lost sight of the larger goal; to support faculty in publishing well respected research and attracting the best graduate students. Although well-intentioned, the tools actually caused a greater sense of lost productivity and increased frustration.

Don’t get me wrong

It’s not that these software tools are bad or don’t have a place in helping achieve organizational goals. It’s that we don’t evaluate them through the lens of meeting these larger questions.

More often than not, productivity projects lose their true value somewhere in the hundreds of pages of technical specs that drive these efforts.

What’s the alternative?

The alternative is to not underestimate how easy it is to lose sight of the vision while getting caught up in believing the software alone will solve the problem.

Starting from original conception, through vendor sales, design and finally execution, broader questions about people and processes will help uncover where the real opportunity and pitfalls lie.

Remember, as a pure technology project, the questions are primarily limited to:

  • Can the software perform the following function?
  • How much does it cost?

Focused on mission, the question is:

  • What does business success look like and how will technology help us to realize these goals?

Asking the latter question may yield a completely different set of choices. Your team may even discover that the full suite of “productivity” solutions (i.e. — the software you paid for but didn’t install yet) may inadvertently cause a greater sense of confusion and ineffectiveness.

Don’t assume technology will keep you moving in the right direction. You may just find yourself and your people working harder but further away from the real value you were looking for.

Achieving Vision

“Vision without action is a dream. Action without vision is simply passing the time. Action with vision is making a positive difference.”

— Joel Barker
Independent Scholar and Futurist