People, Training, and Adoption | Blane Canada

Question 1

Will AI replace our people?

Accepted Answer

AI changes where human value is created rather than eliminating it. As routine tasks are automated, employees have to contribute more judgment, context, creativity, institutional knowledge, and the ability to connect technology to business outcomes. Work is moving from task-based to decision-based.

One of the biggest mistakes a leader can make right now is looking at employees only through the lens of their current job functions and concluding those functions can be automated.

The function may well be open to automation. That does not mean the person is expendable. It means the company has to look harder at the human asset behind every business function. Can this person learn? Can they build relationships? Can they solve messy problems? Can they exercise judgment? Can they work across disciplines? Can they use AI to increase their own value?

People with those capabilities become more important in an AI-enabled company, not less.

Your workforce is not an expense line. It is your AI advantage. The advantage of the future will not come from replacing people as quickly as possible. It will come from building people who combine professional expertise, durable human skills, and real AI literacy. Companies that understand this will not just use AI better. They will build stronger, more adaptable businesses.

Question 2

Should we cut headcount now that AI can do some of the work?

Accepted Answer

The evidence says be careful. Several major companies have publicly reversed AI-driven job cuts after discovering the systems could not handle the exceptions. Ford, Commonwealth Bank of Australia, and IBM have each walked back or rebalanced staffing decisions made on the assumption that AI would absorb the work.

Action before thinking is a precarious position for an executive, and there is now a public record of what happens when this particular action comes first.

Ford has reportedly rehired experienced engineers to address quality issues that automated systems could not handle. Their vice president of vehicle hardware engineering put it plainly: artificial intelligence is a fantastic tool, but it is only as good as the information you use to train it.

Commonwealth Bank of Australia replaced more than 40 customer service staff with an AI voice system, found the system could not cope, saw call volume increase, and reversed the cuts. The bank acknowledged it had not adequately considered all relevant business factors and should have been more thorough in assessing which roles were required.

IBM moved a large share of routine HR requests to AI and handled the great majority of them successfully. The remainder, which included ethical judgment calls, it could not. The company subsequently announced plans to expand entry-level hiring, with its chief human resources officer noting that without continued investment in entry-level hires, the pipeline simply dries up in three to five years.

Survey work by the workforce analytics firm Orgvue and separate data from Robert Half both point the same direction: a substantial share of leaders who made AI-driven redundancies later concluded the decision was wrong, and a meaningful number rehired for the same or a similar role. The pattern behind those findings is consistent with what the named reversals show.

Where AI outputs are inconsistent or hard to apply, companies end up reintroducing human oversight, which duplicates effort and erases the productivity gain. Hollowing out the workforce, particularly at entry level, is a dangerous long-term strategy. AI augments the human. It does not eliminate the need for one.

Question 3

Which employee skills become more valuable because of AI?

Accepted Answer

Judgment, empathy, negotiation, leadership, adaptability, and creative problem solving. As AI absorbs specialized tasks, the durable human capabilities become the differentiator. The most valuable people combine deep expertise in a professional field with real AI literacy.

AI is already changing specialized tasks, and that makes human-centered capabilities more valuable rather than less. Relationship building, conflict resolution, negotiation, leadership, and creative problem solving, paired with technical expertise, are indispensable in an AI-enabled company.

But those skills do not appear by accident. They are developed through mentoring, client exposure, conference participation, business development, internal training, and being tested in real situations before the stakes are too high. That is the management responsibility too many companies have quietly abandoned.

Leaders who build teams blending cross-disciplinary experience with AI literacy are better equipped to pivot as the technology shifts. Looking at workers only through their current, narrowly defined functions creates real risk for the company, because it means losing sight of the actual asset, which is the person and their potential.

The successful companies of the next decade will demand both proficiency with AI and deep knowledge in a specific professional field. That combination is what lets a business apply the tools effectively while retaining the specialized judgment that makes its work worth buying.

Question 4

My team says they use AI every day and love it. How do I know if that is true?

Accepted Answer

Daily use is not competence. Ask what their repeatable process is for getting good output. In workshop after workshop, every executive in the room has used an AI tool and almost none can describe a framework for prompting one. Usage tells you nothing about capability.

At a training workshop in New Mexico, we had exactly this experience. A seasoned executive was a self-proclaimed AI advocate, using it daily and promoting its value to colleagues. He tried the tool we recommended and fifteen minutes later he was frustrated. His complaint: "It keeps waffling. When I point out an omission, it says, good catch, I had not factored that in."

Ashley Canada reviewed his conversation and the problem was immediately obvious. His original prompt asked the tool to compare five competitor websites to his company's site. That was it. No context. No instructions. Just compare.

Ashley rewrote it, defining the tool's role, the task, and the goal, then instructed it to ask clarifying questions until it was confident it understood the assignment. More than twenty questions followed. He answered every one. The output was unrecognizable: a structured analysis with logical sections, benchmarked strengths and weaknesses, and a summary table that brought everything into focus immediately. He stared at the screen and said one word. "Oh."

Widespread use does not mean literacy. A company can have universal adoption and near-zero competence at the same time, and no usage dashboard will tell you which one you have.

Question 5

Why does our team not get better results from AI when everyone is already using it?

Accepted Answer

Because almost nobody has a prompting framework. Ask a room of professionals what their repeatable process is for getting good output and the room usually goes quiet. Without a reference point for what good output looks like, a fast plausible answer just feels like magic.

I have run this test in a lot of rooms now, across more than 13,000 executives trained over the years, and the result is remarkably consistent. Everyone has used a language model. Almost no one can describe how they get a good result on purpose.

The root cause is not laziness. It is that people are using a tool without knowing what it does. In a workshop with 45 executives, I asked whether anyone knew how a large language model works, and one replied by asking what an LLM was. He had used ChatGPT. He just did not know that was what it was.

Every participant was a user with no understanding of the tool in their hands. They did not realize the model produces answers by predicting each word based on probability and pattern drawn from its training data. That is math, not comprehension. Without that insight, nobody can tailor a request to get better results, because they do not know what the machine is doing with what they typed.

Once you grasp that these are probability engines, you can improve your odds dramatically by giving a clear task, a role, and context. Details matter.

The honest executive question here is not whether your team is using AI. It is whether your leadership team is truly AI-literate or just AI-curious.

Question 6

How do I write a prompt that gets a usable answer?

Accepted Answer

Give it a task, a role, and context. Then add background, tell it what to exclude, evaluate what comes back, and iterate. The single most effective addition is instructing the tool to ask you clarifying questions until it is confident it understands the assignment.

Prompting is not a trick. It is the on-ramp to everything else, and it is the one skill that travels with you across platforms, tools, and whatever replaces them.

The framework we teach has seven elements. Task: what you want done, stated specifically. Role: who the tool should be while doing it. Context: the situation, the audience, the constraints. Background: the material it needs to work from. Exclusions: what to leave out, which is more powerful than most people expect. Evaluate: read the output against what you actually needed rather than against how impressive it sounds. Iterate: refine and run it again.

Most people do the first element and stop. That is why their results feel random.

The technique that produces the largest single improvement is telling the tool to ask you questions before it answers. Instruct it to keep asking until it is roughly 95 percent confident it understands what you want. You will answer twenty questions. What comes back afterward will not resemble what you were getting before.

Almost every disappointing result starts the same way. Compare these companies. Write a report. Analyze this. The tool then has to guess what you consider important, and it guesses wrong in a fluent and convincing way. What is worth knowing is that this skill transfers. The specific techniques will keep changing, but thinking clearly about what you need before you ask for it is durable, and it works on whatever platform your company standardizes on next.

One more thing worth understanding. Because these systems predict rather than retrieve, the same question can produce a different answer twice. That is not a malfunction. It is a reason to constrain the request rather than to distrust the tool.

Question 7

Why does our AI training not stick?

Accepted Answer

Because most training is built for the trainer. If a session ends with applause but no change in behavior, you hosted a performance. Training has to be built around practice with real tasks, not presentation. The goal is habits, not enthusiasm.

I have sat through sessions on using AI in business that were essentially a stage act. Slick slides, simple prompts producing instant responses, entertaining stories, and a speaker who clearly enjoyed the sound of his own voice. The topic was important. The delivery taught nobody anything they could use on Monday.

We take a different approach, and the difference starts with explaining how the tool actually works. When people understand that a language model is not comprehending their text but predicting the next word based on pattern, the entire conversation changes. It turns a flashy moment into a useful one, because now they know how to engage the tool rather than being impressed by it.

The rest is practice. Prompting, interpreting, applying, with hands on real work. Until your team gets their hands dirty, nothing sticks. Stop investing in inspiration and start investing in internal capability.

Measure it accordingly, and be careful about what you measure. Counting prompts or documents produced tells you almost nothing, because activity is not value. What is worth tracking during a training rollout is narrower: how often people reach for the tool relative to the occasions where it would have helped, whether it gets built into a workflow rather than used once and abandoned, and whether the people using it say it was worth their time. Those are adoption signals, and adoption is the precondition for any business result later. They are not the business result itself, and they should not be reported as one.

Question 8

Should AI training be limited to our technical team?

Accepted Answer

No, and the reason is not fairness. It is that your technical team does not know where the operational pain is. The people running the messiest workflows do, because they are the ones losing the hours. Restricting training to IT cuts you off from the only group that can tell you what is worth automating.

Here is a finding that shows up in audit after audit. Ask a leadership team where the company loses time and you get a thoughtful, confident answer. Ask the people doing the work and you get a different one, with specifics attached. The second answer is usually the accurate one, and it is unavailable to you if those people were never trained well enough to recognize what a tool could take off their plate.

Inclusive training does more than build skill. It builds morale and engagement, and it produces a pipeline of ideas that no leadership team could generate on its own. One approach worth copying: require every person who completes training to submit at least one idea for where AI could help in their own work. Review, refine, prioritize, and implement. Then repeat.

There is a second reason to widen the circle. When training lives only in IT, AI itself stays in IT, and you cannot build an AI-capable business that way. It has to reach HR, finance, the shop floor, and the boardroom. People develop judgment about a tool by using it on their own work, and judgment is what separates a company with subscriptions from a company with capability.

Question 9

How do we handle employees who are afraid AI will replace them?

Accepted Answer

Address the fear directly rather than working around it. Most resistance is fear of replacement, fear of irrelevance, or fear of the unknown. Run an honest pulse check on sentiment, communicate a clear position on augmentation, and create a space where people can experiment without risk.

Success with AI is not just about technology. Your team is either your greatest asset or your biggest blocker, and change management is not optional.

Start by finding out what people actually think. Are they fearful, excited, or confused? Most leadership teams guess at this and guess wrong. Then communicate a clear position on where the company is going and what it means for roles. Vague reassurance produces more anxiety than a specific answer, even a hard one.

Be honest that some roles will evolve, and name how. Moving from doing a task to supervising a process is a real change, and people handle it far better when it is described in advance than when it happens to them.

Be careful with the word resistance, because it can become a convenient explanation for a poor implementation. Sometimes people push back because the new system genuinely makes their work harder, or because the workflow was designed without them, or because they were never trained, or because the tool produces worse results than what they had been using. Resistance contains information. Ask what changed, watch the workflow, and find the specific friction. Occasionally you will discover the employees were right and the system is not better.

Then create a safe space to experiment where people can test tools without fear of failure or retribution. A culture that invites experimentation, encourages feedback, and invests in learning will get value out of AI. One that brushes off concerns or excludes staff from the process gets resentment and a stalled initiative.

There is a structural reason this matters more than it looks. DHR Global's 2026 Workforce Trends Report, based on a survey of 1,500 knowledge workers across North America, Europe, and Asia, found the share describing themselves as very or extremely engaged fell from 88 percent in 2025 to 64 percent in 2026, with the steepest reductions among entry-level employees and associates rather than among C-suite leaders. That is not a drift. In a single year, roughly a quarter of the engaged workforce quietly stepped back. AI does not only change productivity. It changes identity. People built a sense of themselves around being the sharp analyst or the fast writer. When a tool does the visible part of that in seconds, the destabilizing question is not whether they will lose the job. It is who they are here. Leaders who understand this redesign roles so AI absorbs the rote part and people get more of the work that requires judgment, taste, and relationship.

Question 10

Should we invest in AI tools or in training our people?

Accepted Answer

Training, first and by a wide margin. Organizations are not struggling because AI is not powerful. They are struggling because their people have not been given the structure, literacy, and confidence to use it well. The next advantage will not come from access to tools.

The technology is advancing far faster than human capability is absorbing it, and that gap is where today's frustration lives. Buying another tool widens the gap. Building capability closes it.

There is also a practical argument about durability. A tool decision has a shelf life measured in months right now. Prompting competency, judgment about when to trust output, and the ability to define a problem clearly enough for a machine to help with it travel across platforms, tools, and whatever comes next. That is the asset worth building.

Knowing AI is one thing. Knowing how to use it competently is another. The hardest thing to teach, and the thing that changes everything, is how to think about it: when to reach for it, when not to, what its answer is actually worth, and what question you should have asked instead.

The next competitive advantage will come from upskilling leaders and staff to think differently about work, decision-making, and problem solving. Not from a subscription.

Question 11

How do we develop young talent when AI is doing the entry-level work?

Accepted Answer

Deliberately, because it will not happen on its own anymore. Institutional knowledge and judgment develop over time through exposure. If you eliminate the people who are learning the business today, you will not have experienced managers and decision-makers in five years.

This is the quiet strategic risk inside the workforce conversation, and almost nobody is pricing it.

The path to senior capability has always run through entry-level work. Not because the tasks themselves were valuable, but because doing them was how someone absorbed how the business actually operates, who the customers are, where things go wrong, and what a good decision looks like under pressure. Automate the tasks and the learning path they carried disappears with them unless someone rebuilds it on purpose.

The management role that has been ignored is talent development. Professional judgment is not intuitive and it is not evenly distributed. There is an essential role for mentorship, where senior people consciously work with younger professionals to develop the durable skills. Putting young employees in meetings with clients, at conferences, and inside business development builds cross-functional capability that no training module produces.

Paired with genuine AI skill built through internal training, that combination is what takes a company to the next level. Companies cannot eliminate the people who are learning the business today and still expect to have experienced leaders tomorrow.

Question 12

Why do our best people resist moving to the company-standard AI platform?

Accepted Answer

Because they built something. Your most capable AI users spent months training a tool to match their work style, standards, and responsibilities. Their resistance is not change aversion. It is personal investment in something that works, and they know it works.

Not everyone resisting your platform transition is a weak user hiding behind a familiar tool. Some of your most competent people have done the opposite. They mastered prompting and then went further, spending months teaching their preferred tool how to behave, shaping its output to match how they work.

The customizations sound small individually. Someone may have trained their tool never to use certain punctuation, or to always structure a response a particular way, or to know the standing context of their role. Multiply that across a year of daily use and hundreds of deliberate choices, and you have a highly tuned workflow running quietly in the background every time they open the tool.

Those people need something different from standard training. Training assumes a skill gap and they do not have one. What they need is help deconstructing what they built in the old platform and reconstructing something equivalent in the new one. That is different work and it takes time.

Organizations serious about a successful transition give these individuals reduced responsibilities during the migration, or pair them with someone experienced at moving between platforms. Without that support, you will either lose the productivity of your most capable users or lose the people themselves.

For everyone else in the migration, three things reduce the friction substantially. Explain the business reason for standardizing, because security, cost, support, and governance are legitimate reasons and people accept legitimate reasons. Train on real work rather than generic demonstrations, and teach the underlying skill rather than the specific product. And allow for exceptions where a specialized use case genuinely justifies one. The objective is not identical behavior across the company. It is enough consistency to govern the environment without destroying productivity.

Identifying who falls into this category is the first step. Treating them differently from everyone else is the second.

Question 13

Why did our AI results get worse after we standardized on a new tool?

Accepted Answer

Because the old tool was compensating for weak prompting. When you use a system long enough it learns your patterns and quietly fills gaps in vague requests. A new tool does not know you yet, so it exposes prompting skill that was never actually there.

There are two different people inside this complaint and they need opposite responses. One built real skill and customized their old tool deliberately, and they need migration support rather than training. The other never learned to prompt at all and did not know it, because the old tool was covering for them. This answer is about the second one, and they are the larger group by a wide margin.

Here is how that trap works.

When you use an AI tool long enough, it picks up your patterns and compensates for incomplete prompts based on your history. The results feel good because the tool is doing work you do not realize it is doing for you.

Then your company standardizes. Everyone moves to a new platform. Suddenly your results feel flat, even broken. The new tool does not know you, and the conclusion is swift: the old tool was better.

That is rarely true. What the new tool has actually done is expose something the old one was hiding, which is your prompting skill.

The pattern plays out predictably. One person has used the same tool for two years and gets excellent output, and nobody knows exactly why. A colleague switches to the approved platform and gets mediocre results. Frustration sets in, the team concludes the standardized tool is inferior, and resistance spreads fast.

The real problem was never the tool. It was that nobody on the team was ever taught to prompt.

Question 14

Who inside my company is already using AI, and should I find them?

Accepted Answer

Yes, and they are easier to find than you think. Every company has people quietly using AI to improve their own work or experimenting in the margins. Pull them in, recognize them, and build them into your process. They are already doing the work of adoption for free.

Look sideways before you look outside. The gold is already on your payroll.

These are the people closest to the messiest workflows, which is exactly why they went looking for a better way. They know what is broken and what is repeatable. What they lack is authority, budget, and a channel to tell anyone what they have learned.

Bringing them in does three things at once. It gives you an accurate picture of what is actually in use in your building, which is almost never what leadership assumes. It gives you a starting list of use cases grounded in real operational pain rather than in a vendor's case study. And it converts the informal enthusiasm that was going to happen anyway into something the organization can see, evaluate, and build on.

Recognize the behavior openly. When someone takes initiative, experiments, or shares a prompt or a tool that works, say so publicly. That is how momentum builds, and it costs nothing.

Question 15

How do we avoid creating a two-tier AI workforce?

Accepted Answer

Give people role-appropriate literacy rather than concentrating capability in a small technical group. Not everyone needs the same depth. But everyone whose work is touched by an AI-enabled process should understand what is changing, which tools are approved, and what skills their role now requires.

This is a different problem from deciding who gets trained. It is what happens afterward, when the training was uneven and nobody planned for the consequence. One group pulls ahead. Everyone else keeps working the old way, and within a few months the gap is visible to the whole company, including to the people on the wrong side of it. What follows is not simply lost productivity. It is anxiety, resentment, and a quiet decision by capable people that this organization has already sorted them.

The fix is not universal advanced training, which would waste money and time. Training should match the role. Someone in accounts payable and someone in business development need genuinely different things. What they both need is to understand what is changing in their work, why, which tools are sanctioned, and what skills their job now asks for.

Managers are the group most often overlooked here, and they are the ones who will be redesigning work, evaluating performance under new conditions, and helping people adapt. Sending them into that without preparation is not a small oversight.

Restricting training to the technical team also cuts you off from your best source of implementation ideas. The people closest to the messiest workflows know exactly where the time goes, because they are the ones losing it.

Inclusive training is not an employee benefit. It is part of the implementation itself.