Hiring Someone to Change a Team That Didn’t Ask

A client told me they wanted a transformational leader. I asked what needed transforming.

It took about twenty minutes to get to an answer.

That pause isn’t a criticism of the client. It’s the most common thing I run into when a company has decided something has to change.

The wanting arrives first. The defining arrives much later, and sometimes it arrives after the hire does.

The Word I Had to Define Before We Could Start

“Transformational” turns up in job postings far more often than a defined problem does.

It’s a word that describes an ambition, not a job. Two companies can both want a transformational leader and mean completely different things, and the candidate has no way to tell which from the outside.

So I ask a version of the same question every time. What will be different in eighteen months that isn’t true today?

The answers that come back quickly are usually good ones. Standards have drifted. The same mistake keeps reaching the shop floor. Nobody can tell you who owns a decision.

The answers that take twenty minutes are usually a feeling that something isn’t right, which is a legitimate starting point and a terrible job description.

A feeling is worth taking seriously. It often means someone competent has noticed a pattern before they can name it. The work is turning it into something a candidate can be measured against.

What “Meaningful Change” Looks Like on a Drafting Floor

The concrete version is less dramatic than the word suggests, and that matters for who you hire.

On the Design and Drafting search I’m running, the change is specific:

• Drafting standards that drifted. Not absent, just applied differently by different people over several years.
• Two CAD platforms used inconsistently. SolidWorks and Inventor both in play, with no agreed rule about which does what.
• Process that lives in people’s heads. It works, right up until the person holding it is away or leaves.

The CAD one is worth dwelling on, because it looks like a tooling question and isn’t.

Two platforms used without a rule means every file handoff carries a small negotiation. Which format goes to the fabricator, who converts it, and what gets lost when somebody does. Multiply that by a year of drawings and it stops being small.

None of that is a crisis. All of it is the slow kind of problem that compounds quietly and gets harder to fix the longer it sits.

That shape of change is contested rather than urgent, which is exactly what makes it difficult. Nobody fights a fire. People absolutely fight a new drawing standard.

The Hardest Audience Is the Experienced One

Here is the part that decides whether the hire works.

You are asking someone to change how a group of experienced people do their jobs. Those people were there before the new manager arrived and will have opinions about why things are the way they are.

They are usually right about the history. They know which previous standard failed and why. They know the workaround exists because the official process didn’t account for something real.

They have also watched initiatives arrive and leave. Someone came in with a plan, the plan lasted eight months, and then it quietly stopped being mentioned. That memory is the thing a new leader is actually up against.

The posting asks for three things in a specific order: earn the trust of experienced employees, bring people along through change, establish accountability. That order is not decoration. Accountability imposed before trust exists is just a new rule that people route around.

In practice, earning it looks dull. You ask before you change. You find out why the workaround exists before you remove it. You let the first proposed standard get argued down in a room where the people who have to use it are present.

The managers who struggle are rarely the ones who move too slowly. They are the ones who arrive with the answer already written.

Technical depth alone doesn’t get someone through that, which is a point I’ve made before in why technical expertise alone isn’t enough.

Why Technical Credibility Isn’t Optional in This One

Plenty of change roles can be done by a capable manager from outside the discipline. This isn’t one of them.

The posting asks for an engineering background, preferably Mechanical, with industrial manufacturing or fabrication experience and exposure to engineered equipment and mechanical design.

The reason is simple. You cannot tell a designer with twenty years in the seat that their approach is wrong unless you can read the drawing well enough to know that it is.

Without that, every disagreement becomes a question of authority rather than a question of engineering. Authority arguments are the ones that produce compliance and quiet resentment, which looks like success for about a quarter.

The balance between leading and staying hands-on is its own subject, and I’ve gone through it in the leadership roles that keep you technical. This post is about what happens when you add a change mandate on top of that balance.

What Employers Get Wrong Scoping a Change Mandate

Four errors, and I see them in roughly this order of frequency:

• Not telling candidates the team is resistant. The posting describes an opportunity to shape how the team works. It doesn’t mention that two senior people think the current way is fine. The hire finds out in week three.
• Writing “transformation” with no named problem. If you can’t finish the sentence “we need someone to fix the fact that …”, you’re not ready to post the role.
• Hiring a change agent and then protecting the status quo. The first time an experienced employee complains to a director, the new manager finds out whether the mandate was real.
• Giving the mandate without the authority. Asking someone to set standards while the final call on standards sits two levels up produces a very frustrated hire.

The fourth is the one that ends placements. A mandate without authority isn’t a leadership role, it’s a suggestion with a title attached.

I have had candidates turn down good money over exactly this, and they were right to.

Vague postings have a wider cost than this one role, which is a case I’ve made in why clear job titles attract top talent. And once the mandate is clear, hiring strategies for hard-to-fill roles covers how to actually run the search.

Ten People, and the Range Is the Job

The team on this search is roughly ten design and drafting professionals with a wide span of experience.

That span is the mandate, not a detail about it.

Developing a junior designer and persuading a twenty-year veteran are opposite management problems. One needs structure, feedback and patience. The other needs respect, evidence and a genuine willingness to be argued with.

Most people are naturally good at one of those and have to work at the other. The ones who are honest about which is which tend to do well.

Team size matters more than people expect here too. Ten is large enough that the manager cannot personally review everything, which means the standards have to live in the team rather than in one person’s head. That’s the real deliverable, and it’s slower than it sounds.

The two halves also feed each other, which is the part worth noticing. Written standards are what a junior designer learns from, so the work of pinning them down serves the development half directly.

A team where the standard exists only in the senior people’s judgement is a team where juniors learn by being corrected, which is slow and faintly demoralising.

What to Ask Before You Take One of These

If you’re weighing a role like this, three questions will tell you most of what you need.

• What specifically needs to change, and who decided that? A named problem and a named owner. If the answer is a mood, the mandate will shift under you.
• Does the team know this is coming? There is an enormous difference between a team that asked for change and a team that’s about to be told. Both are workable. Only one is workable without warning.
• What happened to the last person who tried? If there was one, this is the most useful answer you’ll get all interview. If there wasn’t, ask why now.

Vague answers aren’t automatically a reason to walk away. They are a reason to negotiate the mandate before you accept rather than after, because afterwards you’re negotiating from inside the problem.

The wider version of this due diligence sits in how to know if a company is worth joining, and it applies here with more force than usual.

Define It Before You Post It

If you’re writing a leadership posting with the word transformational in it, try finishing this sentence first: in eighteen months, the thing that will be different is ___.

If that takes twenty minutes, the search isn’t ready yet, and twenty minutes now is considerably cheaper than finding out in month four.

If you’re on the other side of it and trying to work out whether a change mandate is real before you commit to it, that’s worth a conversation. I’d be happy to have it confidentially, whether or not there’s a live role involved.

Change Leadership FAQs