Michelle bristled as she looked across the conference room table at Chris. The client presentation was going well. That wasn’t the issue. Chris sat across from Michelle staring into his phone, typing messages and smiling on occasion.
Chris was in his first year of consulting. Michelle had spoken to him several times about using his phone in meetings. This time was different. There were clients present.
She was tempted to ask Chris a question about the presentation to humiliate him, but that would just make the firm look bad. Instead, she waited until later that morning when they were back in their own building and she called Chris into her office.
“What did you think of our presentation today, Chris?” She asked.
“Uh…I thought it went well,” Chris replied without much enthusiasm.
“Were you listening? Because I couldn’t help but notice that you were using your phone throughout most of the meeting.”
“Oh,” Chris replied sheepishly. “That was just a quick text conversation I was having. But I was listening to the presentation.”
“It wasn’t all that quick from my observation. And regardless of how long it was, or whether you were listening, it wasn’t the best impression we could have given the client. You can’t do that stuff in front of clients.”
“I’m sorry.” Chris said quietly.
“Chris,” Michelle said as she leaned in to him, “we’ve talked about this before. If you can’t control yourself with your phone, you may have to turn it off for meetings or leave it in your car.”
“Okay,” said Chris. “I won’t do it anymore.”
Michelle looked him straight in the eye, “I hope so Chris, because this is the last time I’m going to warn you.”
Success in just about any business requires good communication skills. It’s even more important in the consulting industry. Consultants have to have stellar communications skills to communicate with each other and with their clients.
There are many aspects of communication that a consultant must consider.
Pay attention. Unlike Chris, in the example above, it is professional and common courtesy to put electronics, and anything else that may distract you from the conversation, out of the way. Meetings take the collective time of everyone in attendance. Don’t be rude and waste everyone’s time by distracting yourself from the discussion.
Have an agenda. If you are in charge of running the meeting, you should prepare an agenda and share it in advance with all invited participants. This gives them advanced notice of the meeting’s purpose, and the topics you plan to discuss. It will let them know if they need to prepare anything for the meeting. If someone else is in charge of the meeting, ask them if they have an agenda. It might prompt them to prepare one.
Stay to the agenda. Whether you run the meeting or not, it is professional courtesy to stay on topic with the agenda. If you – or anyone else – want to discuss something off topic, suggest that it be put on a parking lot to discuss in case there is time at the end of the meeting, or to schedule another meeting for it.
Email is probably the most common form of communication used in the business world. It is also one of the biggest time wasters. People spend a lot of time during each day sorting through emails, reading them, responding to them, and taking action based on the messages received.
One of the great advantages of email is that you can type it up, review it, and reword or correct what is incorrect before you send it to the intended recipient.
Few people go to that rigor. Most people type from a stream of consciousness and click the send key without much thought. The result is vague subject lines that don’t provide any information about the content of the email. Content can be so brief that the recipient has to spend time trying to figure out the request, or they have to reply back asking for more information.
On the other side of the spectrum, people will send a long, wordy email that causes the recipient to read through it and formulate a response.
Emails should be short, but provide enough information to get a point across. Subject lines should provide the reader with the topic, the main subject of why you are sending the email.
Always address the recipient by name. There may be others copied who don’t realize that the email may be intended for someone else and you are just keeping them informed. If possible, put your content into easy to read short paragraphs or bullets so the reader can scan it easily.
Get to the point and say what you need to without extensive and irrelevant information. If it requires a lot of content, it may be better to have a personal conversation.
Finally, proofread your email. Consider what familiarity the recipient has of the topic. Are you being too vague? Are you being too verbose, providing details that the person already knows? Make sure there are no misspellings and grammatical errors. It will distract the reader and reflect badly on you.
Most people, in an effort to be more productive, try to go through emails quickly. By following these steps for emails, you can help them be more productive, be more productive yourself, and communicate more clearly and succinctly.
Former Tonight Show host Johnny Carson used to cite a very simple approach to public speaking. “Tell them what you’re going to do. Do it. Tell them when you’re done.” It is a simple approach that can be applied to many other things including consulting communication. It is a simple way of keeping people informed along the way.
One of the best ways to communicate clearly is to communicate to people what they can expect and then live up to those expectations. People often have the best laid plans. They know exactly what they want to do and are certain that it will work perfectly.
But when it comes to executing those plans and nobody on their team has any idea what is going on, it can fall flat on its face. Plans are almost certain to fail when the rest of the team doesn’t know what to expect.
Communicate the plan. Consulting is often project based. As a result, there is usually a project plan that maps out what needs to be accomplished on the project. This can be as detailed as a thousand-line Microsoft Project plan, or a list of milestones that will be met. Letting all project participants know what the plan includes allows them to set reasonable expectations for the project.
Team member assignments. When team members are working on a project, they need to know what is expected of them. They should be informed of the tasks they will work on, when they are supposed to be completed and the level of quality expected. When the task is done, the team member should know how that completion is to be communicated.
Business stakeholders. At the beginning of a project, a project charter explains at a high level, what the project hopes to accomplish. This is the first step in letting the business know what to expect.
On a periodic basis, project status should be communicated to the business. This allows the business stakeholders to know how far the project has come, and what has yet to be completed. Daily communications such as emails and face-to-face communications should be clear and concise helping the business stakeholder to know what to expect from the remainder of the project.
There is the old adage that human beings have two ears and one mouth, so they should spend twice as much time listening as speaking. I’ve met few consultants that actually practice that. Many in consulting feel they need to justify their existence by spouting out on all that they know.
In reality, consulting should be a conversation. A doctor wouldn’t treat a patient based strictly on what his specialty or interest is. A good doctor listens to the patient’s symptoms, asks questions and listens to the patient’s answers.
A consultant should work in the same way. Many consultants have expertise in certain areas and try to cram a predefined solution down the throat of the client. This approach can create the wrong solution to the wrong problem.
Listening to the client’s issues allows the consultant to understand the problem before they begin to solve it. It also makes the client a partner in the solution.
The consultant is not expected to know everything. But when consultants act like they do, it can stifle listening and lead to a solution that doesn’t match the problem.
It’s the famous kindergarten grading system: Doesn’t work well with others. Few consultants can be successful if they can’t work with other people. Communication is essentially about one’s ability to collaborate.
Advisor, not a salesperson. Consultants often go into clients with the expectation that they are the expert. They go into sales mode and try to convince the client to implement a certain solution. Instead, they should assume the role of an advisor. Learn the client’s business, find out more about their problem, and work with them to solve it.
Leaders as team players. Many associate leadership with barking out orders and punishing anyone who disobeys or disagrees. Managers shout out orders, leaders get things done. A leader isn’t afraid to roll up her sleeves and pitch in to get a job done. A leader facilitates a solution, getting ideas from the entire team and coming up with a plan that everyone can get behind.
The ability to work with others to solve problems together is collaboration. It is how people solve problems better. It involves communicating clearly, listening, and utilizing every team member’s skills to get to an optimum solution.
Consultants are challenged to succeed if they have poor communications skills. At its very essence, consulting is about communication. Consulting is about problem solving. Few business problems are so simple that one person can solve them in a vacuum. If a consultant does not communicate clearly to her team and to her clients, she can’t solve complex problems and won’t bring value to a client.
How well do you communicate as a consultant?
As always, I welcome your comments and criticisms.
If you would like to learn more about working in consulting, get Lew’s book Consulting 101: 101 Tips for Success in Consulting at Amazon.com
Images courtesy of stockimages and David Castillo Dominici, at FreeDigitalPhotos.net.