I am an advisor, so what I am about to say may be questionable from a business development perspective.

Sometimes you do not need an advisor.

There. I said it.

And yes, I know. Advisor. Consultant. Fractional executive. Strategist. We have developed an impressive number of titles for people you bring in because they know something you need to know.

Call us whatever you like.

The more important question is whether you need one of us in the first place.

There are absolutely times when outside expertise can help an organization move faster, avoid expensive mistakes, challenge its thinking, or solve a problem it does not have the experience or capacity to tackle internally.

There are also times when the answer is already sitting inside the organization.

The trick is knowing the difference.

Because bringing in an advisor simply because something is difficult is not necessarily the answer. Neither is asking an already overwhelmed internal team to figure out something they have never done before because “we have smart people.”

You probably do have smart people.

That does not automatically mean they have the time, experience, perspective, or political freedom to solve every problem you hand them.

So before bringing in outside help, there are a few questions worth asking.

Do We Have the Expertise?

Start with the obvious one.

Has someone inside the organization actually done this before?

Not participated in it. Not sat in three meetings about it. Done it.

There is a difference.

If you are implementing a new workforce technology, redesigning a contingent labor program, evaluating an MSP strategy, or changing your talent acquisition operating model, experience matters.

Could a smart internal leader figure it out? Probably.

But there is value in having someone involved who knows where these initiatives tend to go wrong, which decisions matter most, and which seemingly urgent issues are mostly noise.

That pattern recognition can save a tremendous amount of time. And occasionally a tremendous amount of money.

Do We Have the Capacity?

This is the question organizations sometimes skip.

They identify someone internally who absolutely could lead the initiative. Excellent.

What are we taking off their plate?

Silence.

This is how many strategic initiatives begin their slow journey toward becoming something everyone discusses at quarterly meetings but nobody actually has time to do.

Capability and capacity are not the same thing.

Your Head of Talent Acquisition may be perfectly capable of redesigning your recruiting model. She may also be running recruiting.

Your procurement leader may understand the contingent workforce program better than anyone in the company. He may also have 14 other priorities.

Sometimes outside support is not about bringing expertise the company does not have.

It is about creating enough capacity to actually use the expertise it already has.

Do We Need an Outside Perspective?

Every organization develops its own truths.

“We tried that before.” “Leadership will never approve it.” “That supplier has to stay.” “Our managers won’t do that.” “This is how our industry works.”

Some of those things may be completely true. Some may have been true five years ago. And some may have simply been repeated long enough that nobody asks anymore.

An outside advisor has the luxury of asking the annoying question:

Why?

They are not carrying the history, internal politics, or scar tissue behind the answer.

That does not automatically make their perspective right. It just makes it different.

Sometimes that is exactly what you need.

Is the Problem Really the Problem?

Organizations usually bring in advisors because they have identified a problem.

“Our MSP isn’t working.” “Our technology is outdated.” “Our suppliers aren’t performing.” “We need to reduce costs.” “Our recruiting model needs to change.”

Maybe.

But one of the most valuable things an experienced advisor can do is determine whether the problem you have identified is actually the problem you need to solve.

Poor supplier performance might really be a program governance problem. A technology issue might actually be a process issue. An MSP problem might be an expectations problem. A recruiting problem might be a workforce planning problem.

Buying a new solution for the wrong problem is an extremely efficient way to end up with a newer version of the same problem.

With better graphics.

Are We Looking for Validation or Advice?

This is an uncomfortable one.

Sometimes organizations bring in advisors because they want an independent perspective. Sometimes they bring them in because they want someone independent to agree with the decision they have already made.

Those are not the same assignment.

If leadership has already decided what the answer is and simply needs supporting analysis, be clear about that.

But do not ask an advisor for an objective assessment and then become annoyed when the assessment does not validate the original plan.

You are paying for perspective. You should probably let them have one.

And if you are only looking for someone to tell you that you were right all along, there are cheaper ways to accomplish that.

Ask your mother.

When You Probably Do Not Need an Advisor

There are situations where I would keep the work inside.

If your team has done this successfully before, has the capacity to lead it, has access to the information it needs, and has the organizational support to make decisions, you may not need outside help.

You may just need to let your people do their jobs.

Similarly, if the problem is relatively small, low risk, and easily reversible, there may not be much reason to build an elaborate advisory engagement around it.

Try something. See what happens. Adjust.

Not every business decision requires a steering committee, an advisor, and a 73-slide deck.

I realize I may now be banned from advisory conferences.

When Outside Expertise Earns Its Keep

On the other hand, there are situations where bringing in the right outside expertise can materially change the outcome.

I tend to think advisory support is most valuable when:

• The organization has not solved this type of problem before.
• The stakes are high.
• The decision will be difficult or expensive to reverse.
• The internal team does not have the capacity to lead the work.
• The issue crosses multiple functions or areas of expertise.
• Internal politics make an objective assessment difficult.
• The organization needs market perspective it cannot easily develop internally.
• Speed matters enough that learning everything the hard way is a bad strategy.

In those situations, experience can shorten the learning curve.

The right advisor has seen enough to know where organizations tend to get stuck, which questions need to be answered early, and which decisions are likely to have consequences six months from now.

That does not mean the advisor makes the decisions.

It means the organization can make those decisions with better information and fewer surprises.

That is where outside expertise earns its keep.

The Best Advisory Engagements Have an Ending

This is something I feel pretty strongly about.

An advisory engagement should have a reason to exist. It should also have a point at which it no longer needs to exist.

That does not mean every engagement is short. Some transformations take time. Some companies benefit from ongoing strategic advisory support because their needs continue to evolve.

But the objective should never be dependence.

A good advisor should help solve the problem, strengthen the internal team, transfer knowledge, and eventually become less necessary.

At some point, the advisor should be able to leave. And the wheels should remain attached to the vehicle.

If the solution only works while the advisor is standing next to it, I am not sure we have actually solved the problem.

So, Do You Really Need an Advisor?

Maybe.

I realize that is not the world’s most satisfying answer.

But it is probably the right one.

At Workforce Strategy Advisors, we spend a lot of time thinking about the expertise required to solve a particular workforce challenge.

Sometimes that means one advisor. Sometimes a challenge crosses several disciplines and it makes sense to bring together specialists from our Consulting Consortium. And sometimes the right answer may be that the organization already has what it needs internally.

That should be an acceptable answer too.

The goal is not to find a reason to use outside expertise. The goal is to solve the problem.

So before you bring in an advisor, ask yourself:

Do we lack expertise? Do we lack capacity? Would an outside perspective help us see something differently? Are the stakes high enough that experience could materially improve the outcome?

And perhaps most importantly: Are we willing to hear an answer we were not expecting?

If those answers point toward outside expertise, bring it in. If they don’t, don’t.

Good advisors should be comfortable telling you both.