The short answer
Tell your team yourself, before the consultant arrives, in person. Explain why you've brought in help in terms of the business's goals, what the consultant will do, how employees will be involved, and what you want from them — candor. Address the fear of job cuts honestly, invite questions, and brief your managers first so they can reinforce the message. The owner's framing sets the tone for the whole engagement.
- Managers first, then the whole team — before the consultant starts.
- Frame it around improving the business and making work easier.
- Be honest about job security; don't promise what you can't keep.
Employees notice everything. A stranger in the office, new questions about how jobs are done, the owner in closed-door meetings — within a day, people are speculating. If they hear the reason from you, clearly and early, most will be curious or even relieved. If they piece it together themselves, the story they tell each other is almost always worse than the truth.
Why the announcement matters so much
Much of a consultant's value comes from your team: what they reveal in interviews, how candidly they describe problems, and how willingly they adopt new routines. People who feel threatened give careful, defensive answers and resist change quietly. People who understand the purpose and feel involved tell the truth about what's broken — and often have the best ideas for fixing it. The few minutes you spend on the announcement shape the next several months.
Step 1: brief your managers first
Before telling the wider team, meet with your managers or key people. Explain the reasons, what the consultant will do and how you want them involved. Ask for their concerns and answer them. Managers who feel informed and included become allies; managers who learn at the same time as everyone else may feel undermined. Give them a role in the engagement from the start — they'll be central to implementation. See building a leadership team.
Step 2: tell the whole team, in person
Do it before the consultant starts, ideally in a short team meeting rather than an email. Keep it brief, direct and honest. Cover five things:
- Why: the business goal — for example, making the company stronger, reducing chaos, improving how jobs are planned and paid for.
- Who: the consultant's name and background, briefly.
- What they'll do: spend time learning how the business works, talk with people, look at the numbers, then help put improvements in place.
- How employees are involved: they may be asked about their work; their knowledge is valuable.
- What you want: honesty about what's working and what isn't.
A sample script
Adapt this to your own voice:
"We've grown a lot, and some of the ways we do things haven't kept up — you feel that every day with the scheduling, the rework and the scrambling. I've brought in [name], an experienced business consultant, to help us fix that. Over the next few weeks [he or she] will spend time learning how we work — riding along, sitting in the office, talking with many of you. I want you to be completely honest about what gets in your way. You know this business better than anyone. This is about making the company stronger and your work easier. If you have questions, ask me directly, any time."
Step 3: address job security honestly
Some employees will worry about their jobs, whether or not they say so. Address it directly, but never promise what you can't keep. If the engagement is about growth, efficiency and profitability, and you have no plan to cut staff, you can say so. If you're in financial difficulty and can't rule anything out, don't make promises you might have to break; instead, explain that the goal is to make the business strong and secure, and that you'll communicate openly as decisions are made. A broken promise does far more damage than an honest uncertainty.
What not to say
- "There's nothing to worry about" — if said dismissively, it increases worry.
- "The consultant will tell us who's not pulling their weight" — guaranteed to shut down candor.
- "This is confidential" about the engagement itself — secrecy fuels rumors.
- Vague corporate language — "optimizing synergies" sounds like cuts to most people.
Step 4: introduce the consultant
On the consultant's first day, introduce them personally, ideally in a short team huddle. A good consultant will explain in plain language what they'll be doing and emphasize that they're there to learn from the people who do the work. How the consultant behaves in the first week — listening more than talking, asking genuine questions, respecting people's expertise — does more to build trust than any announcement.
Step 5: keep communicating
Don't make one announcement and go silent. As findings emerge and changes begin, share what's happening and why. Celebrate early wins publicly — faster invoicing, a smoother schedule, less rework. Involve people in designing changes to their own work. When employees see improvements that make their days easier, skepticism turns into support. We cover what to do if it doesn't in what if your employees resist the consultant?
Questions employees will ask — and good answers
Prepare for a handful of predictable questions. "Are you selling the business?" If not, say so plainly. If you're preparing for a future sale, you don't need to announce it, but don't deny something that's true. "Is my job safe?" Answer as honestly as you can, as described above. "Why do we need an outsider?" Because an outside view sees what insiders have stopped noticing, and because you want help putting improvements in place without pulling people off their work. "What will change for me?" You don't know yet — and that's the point of involving them; changes to their work will be designed with them.
Special situations
Very small teams. With fewer than ten people, a formal meeting can feel heavy. A relaxed conversation over coffee works well, as long as everyone hears the same message at the same time. Family members in the business. Brief them before other employees, and make sure they understand and support the message; mixed signals from family are especially damaging. See consulting in a family business. Field crews and remote staff. People who are rarely in the office hear news last and least accurately. Tell them directly — at a morning huddle or by phone — rather than letting it filter through the grapevine. A recent difficult change. If the team has just been through layoffs or a failed initiative, acknowledge it. Explaining how this effort is different carries more weight than pretending the past didn't happen.
How consultants should behave with your team
The consultant's approach matters as much as your announcement. Our principles are simple: meet people where they are, listen before we prescribe — to you and to your team — and co-build solutions with your people so they survive after we leave. Interviews are conducted with respect and discretion, and what employees share is reported as themes rather than attributed complaints, so people can be candid. See how our engagements work and how confidentiality works with your staff.
Frequently asked questions
Should I tell employees I've hired a consultant at all?
Yes. They'll notice anyway, and secrecy breeds rumors. Telling them yourself, early, lets you frame the purpose and invites the candor the engagement depends on.
Should I announce it by email?
In person is far better for the main announcement, with a short written follow-up if helpful. Tone and the chance to ask questions matter.
What if employees ask whether there will be layoffs?
Answer honestly. If there's no plan to cut staff, say so. If you can't rule it out, explain the goal is a stronger, more secure business and promise to communicate openly — then keep that promise.
How much should I tell employees about the business's finances?
Share the goals and the general picture, not confidential details. Employees need to understand why change matters, not see the P&L.
Should the consultant attend the announcement?
It's usually better for the owner to announce alone, then introduce the consultant separately on their first day. It makes clear the decision and leadership are yours.
When is the best time to make the announcement?
A few days before the consultant starts, early in the week, when people have time to ask questions. Avoid announcing just before a weekend or holiday, when rumors have days to grow unanswered.
What if a manager is against bringing in a consultant?
Listen to the concern privately; it's often about feeling judged or bypassed. Involving them early and giving them a real role in the engagement usually turns resistance into ownership.
Where to start
If you're considering bringing in help and wondering how your team will react, we're happy to talk it through on the first call — it's free. Start the free assessment and you'll hear back within one business day. See our leadership and team development service for how managers are brought into the work.
