Consulting Essentials: 101

Imagine walking into a client meeting with a perfectly good solution.

You've done the research, analysed the data, understood the problem and spent hours putting together a recommendation. The solution makes business sense, the numbers support it, and technically, everything checks out.

You present it to the client. And then comes the response.

"We don't think this will work for us."

Now what?

You could explain your analysis again. You could present another set of numbers. You could even argue that your recommendation is the most logical one. But none of that necessarily means the client will agree, let alone act on it.

And that's something interesting about consulting. Having the right answer is only one part of the job. Getting people to understand it, trust it and eventually act on it is an entirely different challenge.

Consulting is often associated with solving complex business problems, developing strategies, implementing technology and delivering measurable outcomes. And rightly so. But it is also, at its core, the art of influencing people at their request.

As consultants, our job is to help clients achieve their business goals using our knowledge and expertise. But we aren't simply delivering technology or ticking off requirements. We are engaging with people, understanding their challenges, navigating their organisational structures and cultures, and building partnerships that allow us to solve problems together.

Think about it. A technically brilliant solution that nobody adopts isn't particularly useful. A well-researched recommendation that doesn't account for the client's business realities is unlikely to get very far. And a project that delivers exactly what was requested but fails to address what the client actually needed? Well, that's a different problem altogether.

The work doesn't happen in isolation. Every conversation, every meeting, every update and every decision is an opportunity to practise consulting.

How we prepare for meetings, how we communicate with clients, how we support our teammates, whether we proactively raise concerns or wait to be asked, and how we respond when things don't go as planned — all of these shape the client experience.

And if there's one thing that ties all of this together, it is the ability to work with people.

Let's start with something we do every single day: communication.

---

01. Communication: It's not about what you say, but what people understand.

We've all been in meetings where someone explains something for fifteen minutes, everyone nods, and then someone asks a question that makes it painfully obvious that nobody was on the same page.

The explanation might have been technically correct. The information might have been complete. But was the communication effective?

Not necessarily.

How well we communicate is determined not by how well we say things, but by how well we are understood.

This distinction matters, particularly in consulting, where we are constantly communicating with people who have different levels of technical knowledge, different priorities and different expectations.

Consider a simple example.

A development team identifies a technical dependency that could delay a project by two weeks. The team discusses it internally, understands the implications and updates the project documentation.

But the client isn't informed until the next status meeting, by which point the delay has already affected their planning.

The team may have done its technical work correctly. But the communication failed.

Could the risk have been raised earlier? Could the impact have been explained more clearly? Could the client have been given enough information to make an informed decision?

Probably.

Effective communication isn't just about sharing information. It is about making sure the right people understand what is happening, why it matters and what needs to happen next.

It starts with listening.

We often think of communication as the ability to articulate our thoughts, present ideas or explain things convincingly. But some of the most important communication happens before we even say anything.

Active listening means giving someone your full attention instead of mentally preparing your response while they're still speaking.

It means being open to perspectives that might differ from yours, asking questions instead of jumping to conclusions, and making a genuine effort to understand where the other person is coming from.

Four behaviours make a significant difference:

• Active listening: Focus on what is being said without planning your reply. Pay attention to non-verbal cues and avoid distractions.
• Open-mindedness: Suspend judgement. Don't assume you already understand the situation.
• Empathy: Try to understand the context, concerns and emotions behind what someone is communicating.
• A positive mindset: Assume good intentions. Not every disagreement is an attack, and not every question is a challenge to your competence.

For instance, a client repeatedly questions a proposed technical approach. It is easy to interpret this as resistance or a lack of trust in the team.

But perhaps they've had a failed implementation before. Perhaps they are worried about operational disruption. Or perhaps they have information about the business that the team hasn't considered.

The response shouldn't automatically be to defend the recommendation. Sometimes, it should simply be to ask another question.

The 7 Cs of effective communication

There is also a simple framework that helps us evaluate how we communicate: the 7 Cs.

Principle	What it means
Clear	State your message and objectives directly. Avoid ambiguity and unnecessary jargon.
Concise	Stick to the point. Respect your audience's time and eliminate filler.
Concrete	Support your claims with specific facts, data and real-world examples.
Correct	Verify your facts, figures and language. Accuracy matters.
Coherent	Maintain a logical structure and ensure your points flow naturally.
Complete	Provide the necessary context: what, who, when, where and why.
Courteous	Be respectful, open and considerate of the other person's perspective.

These principles are particularly useful when communicating project updates, presenting recommendations, documenting decisions or raising risks.

And there is a simple way to check whether your communication has actually worked.

Does the audience understand the message? Has the intended outcome been achieved? Do they know what needs to happen next? Is there alignment on the way forward?

If not, perhaps the conversation isn't finished.

Because communication isn't complete just because the meeting has ended or the email has been sent.

It is complete when people understand what was discussed and know what to do with that information.

And that brings us to another important part of consulting: understanding the people we're communicating with in the first place.

02. Stakeholder Management: Understand the people behind the project.

Imagine working on a project where you have four key stakeholders.

The business sponsor wants the product launched as soon as possible. The technical lead is concerned about scalability. The finance team wants to keep costs under control. And the operations team is worried about how the new system will affect its existing processes.

Everyone wants the project to succeed. But ask each of them what success looks like, and you'll probably get four different answers.

This is where stakeholder management becomes important.

Stakeholder management is the ability to identify, analyse, plan and implement actions that engage people, build relationships and sustain them through effective expectation management, enabling each party to reach their goals.

Notice that this goes beyond simply identifying who the stakeholders are or scheduling regular status meetings with them.

It is about understanding what matters to different people and finding ways to align their expectations.

First, understand your stakeholders.

Before trying to influence someone, understand what drives their decisions.

There are four areas worth exploring:

1. Goals and priorities

• What outcomes are they trying to achieve?
• What does success look like to them?
• What are their expectations from the project?

2. Motivations

• What matters most to them?
• What challenges are they concerned about?
• What keeps them up at night?

3. Relationships

• Who influences their thinking?
• What is our existing relationship with them?
• If trust is low, what can we do to strengthen it?

4. Communication

• What information do they need?
• How frequently do they expect updates?
• What is their preferred communication channel?

These might seem like straightforward questions, but they can change how you approach an entire engagement.

For example, a finance stakeholder may not be particularly interested in the technical details of a proposed architecture. They want to understand the cost implications, return on investment and financial risks.

The technical lead, on the other hand, might want to understand the architecture, integration challenges and long-term maintainability.

Communicating the same information in exactly the same way to both stakeholders isn't necessarily effective.

The message, level of detail and context need to be relevant to the person receiving it.

And most importantly, there needs to be alignment. Have everyone agreed on the goals, scope, priorities and measures of success? Or are we assuming that everyone is working towards the same outcome?

Building trust: The TRUST framework.

Understanding stakeholders is one thing. Building a relationship where they trust your judgement is another.

You can have the best analysis, the most convincing presentation and the most technically sound recommendation. But if the client doesn't trust you, getting them to act on it becomes considerably harder.

This is where the TRUST framework comes in.

T — Build Trust

People are more likely to follow someone they trust. Trust develops through consistency, transparency, reliability and following through on commitments.

R — Relate to Their Priorities

People support what matters to them. Understand their goals and connect your recommendations to the outcomes they care about.

U — Understand Before Advocating

Influencing begins with genuine curiosity. Understand their concerns, constraints and perspectives before trying to convince them of something.

S — Share Evidence

Use facts, examples and business impact to support your recommendations. An opinion might start a conversation, but evidence helps people make informed decisions.

T — Together, Create a Path Forward

Involve stakeholders in developing solutions. People are more likely to support a direction when they feel they have contributed to shaping it.

One thing worth emphasising here is that building trust isn't something we do only when we need the client to agree with us.

It is built through everyday interactions. Keeping commitments, raising concerns early, being honest about what we know and don't know, and making sure there are no unpleasant surprises.

And when presenting a solution, always give the client a choice.

Instead of walking into a meeting with one recommendation and expecting everyone to agree, present alternatives wherever appropriate. Explain the benefits, limitations, costs and trade-offs of each option.

The client should have enough information to make an informed decision.

Don't try to change the client. Influence their way of working.

Influencing without authority.

Now, here's something particularly interesting about consulting.

You might be responsible for delivering a project, advising a team or recommending a change, but that doesn't necessarily mean you have the authority to make decisions for the people involved.

You may not manage the client's employees. You may not own their processes. You may not even have the final say on whether your recommendation gets implemented.

Yet you are expected to influence the direction of the engagement.

This is what influencing without authority is about.

It relies on credibility, trust, relationships and a shared commitment to achieving an outcome. You cannot force someone to agree with your recommendation simply because you have done the analysis. You have to make them understand why it matters. And sometimes, that means accepting that your first recommendation might not be the one that gets implemented.

A good consultant knows when to advocate, when to listen, when to challenge and when to find common ground.

Because ultimately, the objective isn't to prove that you're right. It is to help the client make the right decision.

But how do we arrive at that decision in the first place? That brings us to another fundamental consulting skill: structured problem-solving.

03. Problem Solving: Finding the right problem before finding the right solution.

A retail company approaches a consulting team because its revenue has been declining for the last two quarters. The leadership team believes the problem is marketing. Their immediate request is to develop a new marketing strategy and increase customer acquisition.

Sounds reasonable. But is marketing actually the problem?

Perhaps customers are visiting the website but not completing their purchases. Maybe products are frequently out of stock. Maybe the checkout process is unnecessarily complicated. Or perhaps existing customers are leaving faster than new ones are coming in.

Jumping straight into a marketing strategy might be solving the wrong problem entirely.

And that's where structured problem-solving comes in.

A useful way to approach a business problem is through four stages:

1. Define the problem.
2. Explore the root cause.
3. Generate options.
4. Make a recommendation.

Define the problem. Don't jump to solutions.

One of the easiest mistakes to make when solving a problem is accepting the first explanation presented to you.

A client says sales are declining, so we assume marketing is the issue. A team says productivity is low, so we assume they need better tools. A process takes too long, so we assume it needs automation.

But these are assumptions, not necessarily facts.

The first step is to define the problem clearly.

A useful technique here is the 5 Whys framework.

The idea is simple: keep asking why until you move beyond the immediate symptom and get closer to the underlying cause.

Let's return to our retail company.

• Why are sales declining? Because fewer customers are completing purchases.
• Why are fewer customers completing purchases? Because cart abandonment has increased.
• Why has cart abandonment increased? Because customers are dropping off during checkout.
• Why are they dropping off during checkout? Because unexpected delivery charges are being added.
• Why are delivery charges unexpected? Because they are only displayed at the final stage of checkout.

Now we have something much more specific to investigate.

Perhaps the issue isn't marketing at all. Perhaps it is the checkout experience.

Of course, the 5 Whys is a way to investigate, not a guarantee that every problem has one simple root cause. In complex situations, there may be multiple contributing factors that need to be explored.

The important thing is to avoid treating symptoms as the problem.

Explore the root cause.

Once the problem is defined, the next step is to investigate it.

Gather information. Ask questions. Look at the available data. Speak to people who understand the process. Identify patterns and validate your assumptions.

In our retail example, we could examine:

• Cart abandonment rates across different stages.
• Customer feedback and support tickets.
• Checkout completion rates across devices.
• Changes in delivery pricing.
• Differences across customer segments.

The objective is to understand what is actually happening before deciding what should be done about it.

Generate options. Don't settle for the first idea.

Once we understand the problem, it is tempting to jump straight to a solution.

But good problem-solving involves exploring the possibilities before committing to one.

For the checkout issue, possible solutions could include:

• Displaying delivery charges earlier in the customer journey.
• Offering free delivery above a certain order value.
• Introducing a simplified checkout process.
• Providing clearer delivery estimates.
• Offering different delivery options.

Each solution has its own benefits, costs and trade-offs.

For example, offering free delivery might improve conversion rates, but it could also reduce profit margins. Displaying delivery charges earlier might be relatively easy to implement, but it may not address every reason customers abandon their carts.

The point is to uncover the available options, evaluate them and understand their implications.

And this brings us to two important ways of thinking that go hand in hand in consulting: bottom-up thinking and top-down communication.

Bottom-up thinking vs. top-down communication.

When solving a problem, we often need to work through a large amount of information before arriving at a recommendation.

But when presenting that recommendation, the audience doesn't necessarily need to hear every step of our investigation.

This is where the distinction between bottom-up thinking and top-down communication becomes useful.

Bottom-up thinking: How we analyse and structure information.

1. Gather information.
2. Ask questions.
3. Build an issue tree.
4. Investigate root causes.
5. Generate options.
6. Prioritise.

An issue tree, for example, helps break a large problem into smaller, more manageable components. Instead of trying to understand declining revenue as one massive problem, we can examine customer acquisition, conversion, retention, pricing and other contributing factors.

This helps us investigate systematically without losing sight of the bigger picture.

Top-down communication: How we deliver our findings.

1. Start with the recommendation.
2. Explain the supporting arguments.
3. Present the supporting evidence.

Prioritisation and decision-making: Not everything deserves equal attention.

Now that we have identified the problem and generated possible solutions, how do we decide what to work on first? Because let's be honest. Most projects have more things that need to be done than the time and resources available to do them.

This is where the Impact vs. Effort Matrix becomes useful.

It helps us evaluate potential initiatives based on two dimensions:

• Impact: How much value will this create?
• Effort: How much time, money or resources will it require?

The matrix divides initiatives into four categories.

1. Quick Wins — High Impact, Low Effort

These are the initiatives that deliver significant value without requiring substantial resources. They should generally be prioritised for immediate action.

Example: Displaying delivery charges earlier in the checkout process might be a relatively simple change with a meaningful impact on conversion rates.

2. Major Projects — High Impact, High Effort

These are strategically important initiatives that require careful planning, resources and execution.

Example: Rebuilding the entire checkout infrastructure to support multiple payment options and a more personalised customer experience.

3. Fill-ins — Low Impact, Low Effort

These are smaller tasks that don't create significant value but are relatively easy to complete. They can often be delegated or automated.

Example: Making minor cosmetic changes to a low-traffic page.

4. Reevaluate — Low Impact, High Effort

These initiatives consume considerable resources without delivering proportional value. They may need to be postponed, reconsidered or dropped altogether.

Example: Building an elaborate custom reporting system when an existing dashboard already provides the information stakeholders need.

Of course, impact and effort are estimates, and priorities can change as new information becomes available. The matrix is a decision-making aid, not a substitute for judgement.

04. Managing Resistance and Conflict: The human side of change.

Imagine recommending that a company automate a manual process.

The business case looks promising. The technology is available. The expected benefits are clear, and the leadership team is convinced.

But the employees who currently manage that process aren't particularly enthusiastic.

They worry about losing control over their work. Some are concerned about additional responsibilities. Others have seen similar initiatives fail in the past.

The solution makes business sense. So why isn't everyone on board?

Because change isn't just about the process or technology being introduced. It affects people, their responsibilities, their routines and sometimes even their sense of security.

Why do people resist change?

Resistance is often treated as an obstacle that needs to be overcome. But before trying to address it, we need to understand where it comes from.

Some common reasons include:

• Fear of losing control: People are uncomfortable when familiar processes and responsibilities change.
• Increased workload: A new initiative may initially mean additional work, training or responsibilities.
• Competing priorities: People may already have too much on their plate to accommodate another change.
• Previous failed initiatives: Past experiences can make people sceptical about new proposals.
• Lack of trust: People may not trust the individuals driving the change or believe the promised outcomes.
• Lack of involvement: People are less likely to support decisions when they feel they had no say in making them.
• Unclear benefits: If people don't understand why a change is necessary or how it benefits them, they may have little reason to support it.

Resistance is a natural reaction to uncertainty.

And that changes how we approach it.

Instead of assuming that people are simply being difficult, we should try to understand what they're concerned about.

Sometimes, what looks like resistance to a solution is actually a request for more information, reassurance or involvement.

Which brings us to conflict.

Conflict isn't always a bad thing.

Conflict is essentially a tug of war between opposing thoughts, beliefs or situations.

It can arise because people have different priorities, different interpretations of a situation or different ideas about how something should be done.

But conflict doesn't automatically mean something has gone wrong.

In fact, healthy disagreement can challenge assumptions, encourage better discussions and lead to stronger decisions.

Consider a situation where a client wants to prioritise speed of delivery, while the engineering team is concerned about technical debt and long-term maintainability.

Both perspectives are valid. The client is concerned about business timelines, while the engineering team is trying to prevent future complications.

The objective shouldn't be to establish whose perspective wins. It should be to understand the trade-offs and arrive at a decision that works for the engagement.

But how do we decide how to respond when perspectives clash?

The Thomas-Kilmann model: Five ways to manage conflict.

The Thomas-Kilmann Conflict Mode Instrument (TKI) describes five approaches to handling conflict.

It looks at two dimensions:

• Assertiveness: How important is it that you get what you want?
• Cooperativeness: How important is it that the other person gets what they want?

Depending on these two dimensions, we can approach conflict in five different ways.

1. Competing

This approach prioritises getting your perspective accepted. It involves high assertiveness and low cooperativeness.

It can be appropriate when an immediate decision is required or when an important principle or non-negotiable requirement needs to be upheld.

2. Collaborating

This involves working together to develop a solution that addresses the concerns of everyone involved.

It requires both high assertiveness and high cooperativeness.

For example, the client wants a faster delivery timeline, while the engineering team wants to avoid compromising essential quality standards. Instead of choosing one over the other, both parties work together to identify a revised scope or phased delivery plan.

3. Compromising

This involves finding a middle ground that is acceptable to everyone, even if neither party gets everything they originally wanted.

For example, agreeing to deliver the most important features first while moving less critical features to a later release.

4. Avoiding

Sometimes, stepping away from a conflict is the most appropriate response.

This might be useful when the issue is relatively insignificant, when emotions are running high or when more information is needed before having the discussion.

However, avoiding an issue indefinitely doesn't make it disappear.

5. Accommodating

This involves prioritising the other person's perspective over your own.

It can be useful when the issue matters significantly more to the other party, when preserving the relationship is important or when you recognise that their perspective is better suited to the situation.

The interesting thing about this model is that no single approach is always right.

A consultant who collaborates on every single decision might spend unnecessary time trying to reach consensus. Someone who competes in every disagreement might damage relationships and lose stakeholder trust.

The skill is recognising the situation and making an intentional choice rather than reacting emotionally.

Difficult conversations: The CARE framework.

Understanding conflict is one thing. Actually navigating a difficult conversation is another.

Imagine a client repeatedly misses their responsibilities, causing delays to the project. The team is frustrated, deadlines are slipping and the issue needs to be addressed.

You could approach the conversation by pointing out everything the client hasn't done.

But is that going to help?

Probably not.

A more constructive approach is to use the CARE framework.

C — Clarify your purpose

Before entering a difficult conversation, understand what you're trying to achieve.

• What outcome are you looking for?
• What problem are you trying to solve?
• What relationship do you want to have after the conversation?

The objective should be to address the issue, not to prove someone wrong.

A — Acknowledge their perspective

People are more willing to listen when they feel heard.

Understand the other person's constraints and concerns. Acknowledge their perspective without necessarily agreeing with it.

In our example, the client may be dealing with competing business priorities or resource constraints that the project team isn't aware of.

Acknowledging this doesn't mean ignoring the delays. It simply creates room for a more constructive discussion.

R — Raise the issue using facts

Separate observations from assumptions.

Instead of saying, "The client team is not cooperating," explain that three agreed deliverables have not been received, which has affected the project's timeline.

Focus on facts and business impact rather than blame.

E — Explore solutions and end with collaboration

Once the issue is understood, explore possible ways forward.

Can responsibilities be redistributed? Do timelines need to be revisited? Is additional support required? Can both teams agree on a more realistic plan?

The conversation should end with shared ownership and clarity on the next steps.

The goal isn't simply to have a difficult conversation and move on. It is to make sure something changes as a result of it.

And that is what makes the difference between managing conflict and actually resolving it.

---

05. Bringing it all together: Consulting is a people business.

Let's go back to where we started.

A client approaches a consulting team with a business problem. The team investigates, analyses the situation, develops recommendations and proposes a way forward.

But somewhere along the way, there are conversations that need to happen, expectations that need to be managed, disagreements that need to be resolved and decisions that need to be made.

The technical solution is only one part of the engagement.

We need to communicate in a way people understand. We need to understand stakeholders and build relationships with them. We need to break complex problems into manageable parts, evaluate alternatives and make informed recommendations. And when people disagree or resist change, we need to navigate those situations with empathy, clarity and intention.

None of these capabilities exist independently. They constantly overlap.

A good recommendation requires structured problem-solving, but getting it accepted requires trust and effective communication. Managing a difficult stakeholder requires empathy, but also the ability to raise uncomfortable issues using facts. Delivering a successful project requires technical expertise, but also the ability