The Talent Is Already in the Building. You Just Haven't Looked.

Leadership Series, Article 2 of 3

You already know this person.

You've probably sat across from them in a meeting where they were the only one who actually understood the problem. You've forwarded their email to someone else because they explained something complicated in a way that finally made sense. You've heard their name come up when something important needed to get done and nobody was sure who to trust with it.

You may have even lost one of them to a competitor and spent three months trying to backfill what left when they walked out the door.

That person — the one you just thought of — is your AI lead.

They just don't have the title yet.

The Profile Nobody's Writing Job Descriptions For

Leadership teams searching for AI talent tend to look in one direction: outward. New hire. External candidate. Someone who arrives with a credential that signals they know what they're doing.

The problem is that credential doesn't exist in a meaningful way yet. We covered that in the last article.

What does exist — right now, on your payroll — is a specific type of person. They show up in a handful of roles more often than others, but the role isn't really the point. The point is how they think.

Here's who you're looking for.

The Project Manager who treats every broken process like a personal insult. They're the one who doesn't just flag that something is inefficient — they show up to the next meeting with a proposed fix. They think in workflows. They can map how work actually moves through your organization versus how the org chart says it should. They know where the bodies are buried and which handoffs never work the way anyone planned.

They've been managing around your broken tools for years because nobody gave them the authority to fix them. Give them AI and a mandate and watch what happens.

The Product Manager who can't stop asking why. Not the why that's looking for someone to blame — the why that's trying to understand the system. Why does this step exist? Why does the customer drop off here? Why does this report take three days to produce when the data is sitting right there?

They already think in terms of user experience, outcomes, and iteration. That's most of what you need to deploy AI effectively. The rest is learnable.

The Platform Subject Matter Expert who knows the systems better than IT does. Every organization has at least one. They're the person everyone calls before they call the help desk because the help desk will just open a ticket and the SME will actually solve it. They know which fields in the system are reliable and which ones nobody updates. They know the workaround that's been in place since the 2018 migration that nobody ever documented.

That institutional knowledge is the exact thing AI needs to be useful in your specific environment. Without it, AI is just a smart tool asking dumb questions.

The Business Analyst who can trace a problem to its source before anyone else finishes complaining about it. They think in data and process simultaneously, which is rare. They can sit in a room full of people describing a symptom and identify the actual cause. They already speak the language of measurement — they know what a baseline is, what a meaningful change looks like, and how to tell the difference between a trend and a coincidence.

That's exactly the skillset that determines whether an AI deployment generates real results or just generates activity.

The Signals to Look For

You're not going to find these people by sorting resumes. The signals that matter don't show up on a resume. They show up in behavior.

They're already experimenting on their own time. Not because anyone told them to. Because they couldn't help themselves. They've been using AI tools on personal projects, side work, or just to solve problems that annoyed them. They talk about what they tried and what didn't work. They've formed opinions. They have questions that go beyond the surface level.

This is the most reliable signal. Curiosity that doesn't require a budget or a permission slip is the thing you cannot manufacture through training.

They get frustrated by friction. Not in a complaining way — in a problem-solving way. When a process has twelve steps and four of them are pointless, they feel it. They can't stop noticing it. That low tolerance for unnecessary friction is exactly the instinct that finds the right AI applications. Nobody builds a useful automation out of a process they've stopped noticing.

They explain things simply. The ability to take something complex and make it clear is underrated in almost every organization. It is not underrated when you're deploying AI. These tools require clear instructions. Vague input produces vague output. The person who can precisely describe what they need — in plain language, without ambiguity — has a foundational skill that most AI certifications don't teach.

They care about whether it actually worked. This is rarer than it sounds. A lot of people in organizations care about whether the project launched on time and on budget. Fewer care about whether the thing they launched produced the outcome it was supposed to produce. The people who track back to the result — who are genuinely bothered when the outcome doesn't match the intention — are the ones who will build AI solutions that actually stick.

They want to understand how things work, not just how to use them. There's a difference between someone who wants to learn the tool and someone who wants to understand what the tool is doing and why. The second person is who you want. They're the one who asks what happens under the hood, who reads past the tutorial, who isn't satisfied with "just click this button."

In the context of AI, this maps directly to the desire to learn how software is built and how systems are structured. They don't need to become engineers. But they need to be curious enough to want to understand the process — how a system gets built, how it gets tested, how it gets improved. That curiosity is what separates the person who uses AI from the person who deploys it effectively.

The Objection You're Already Forming

Here's what's going to come up in the leadership conversation when you propose this.

"But they don't know AI. We need someone with real technical expertise."

Fair. Let's look at what that actually means.

Your business has specific processes. Specific data. Specific constraints. Specific customers. Specific ways that value moves through the organization and specific places where it gets stuck.

That knowledge took years to develop. It lives inside the people who have been working in your environment and learning how your business actually operates. You cannot download it. You cannot hire it from the outside. You can only grow it over time — or find someone who already has it.

Now here's the other side of the equation.

The AI tools themselves are more accessible than they've ever been. Interfaces are cleaner. Documentation is better. The learning curve, for someone with strong problem-solving instincts and genuine curiosity, is measured in weeks to months — not years.

Business fluency is hard to acquire. It takes time, exposure, and a specific type of attention that not everyone has.

AI fluency, for the right person, is learnable fast.

So the question you're actually asking is: do you want someone who knows your business and can learn the tools, or someone who knows the tools and has to learn your business?

One of those has a twelve-month orientation period baked in. The other can start being useful in weeks.

The Clock You're Not Watching

Here's what makes this urgent in a way that most leadership teams aren't accounting for.

The people described in this article — the ones already on your payroll with exactly the instincts and knowledge you need — are already paying attention to AI on their own time.

Some of them are already building things. Experimenting with tools. Reading. Watching. Quietly developing skills that nobody at your organization knows they have.

In twelve months, those skills are going to be visible somewhere. The question is whether it's inside your organization or on someone else's org chart.

The window to develop this talent, retain it, and point it at your actual business problems is open right now. It will not stay open indefinitely.

These people are not waiting for your AI strategy to get finalized. They're moving. The only question is whether they're moving toward your organization or away from it.

What to Do Right Now

Before the next leadership meeting, do this.

Think about the five people in your organization who best fit the profile described here — across your project managers, product managers, platform SMEs, and business analysts. Don't filter on technical background. Filter on the behavioral signals: curiosity, frustration with friction, outcome obsession, the ability to explain things simply, the desire to understand how things actually work.

Write their names down.

That's your shortlist. That's who you're building the bootcamp around.

In the next article, we'll talk about what that bootcamp actually looks like — how to give these people the framework, the tools, and the guardrails to start building AI capability inside your organization. Not in theory. Starting this month.

Next in the Leadership Series: Building the Bootcamp — how to turn your internal talent into a real AI capability without a six-figure consulting engagement or an eighteen-month implementation timeline.

2weekAI delivers fixed-bid AI assessments and deployments in two weeks. If you want help identifying your internal AI candidates and building the framework around them, that's exactly the kind of engagement we're built for. Book a discovery call →