I remember sitting in a boardroom, listening to a pitch from a startup that was going to "revolutionize" an industry with AI. They threw around all the right buzzwords: "neural networks," "large language models," "deep learning." I’m an investor in Anthropic, OpenAI, and Scale AI, so I know the jargon. But as they talked, I realized they couldn't answer one simple question: "What problem are you actually solving?"
They were a solution in search of a problem. And I see this happen all the time. Companies get so caught up in the AI hype that they forget why they’re using it in the first place.
Feeling lost in the AI hype? You're not alone. Here's a practical, no-BS guide for non-technical leaders to successfully navigate an AI transformation.
You Don't Need to Be a Coder to Lead the Charge
Let's get one thing straight: you don't need a PhD in machine learning to lead an AI transformation. In fact, some of the most successful AI-driven companies I’ve seen were led by people who couldn't write a line of code.
Why? Because they understood a fundamental truth: AI is a tool, not a magic wand. And like any tool, it's only as good as the person wielding it. Your job as a leader isn't to build the AI, it's to point it at the right problems.
Stop Chasing Shiny Objects. Start Solving Real Problems.
I’ve made over 200 angel investments. I’ve seen hundreds, maybe thousands, of pitches. The ones that get my money are the ones that are obsessed with a problem, not a technology. They start with a real, painful need from a customer and then figure out how to solve it. Sometimes the answer is AI. Sometimes it’s a simpler, dumber solution. And that’s okay.
At RemoteTeam, which was acquired by Gusto, we didn't start by saying, "Let's build an AI company." We started by noticing how painful it was for companies to manage a global workforce. The compliance, the payroll, the paperwork—it was a mess. We used technology, including automation and smart systems, to solve that specific problem. The tech was in service to the solution, not the other way around.
Your first job as a leader in an AI transformation is to be the Chief Problem Officer. Forget the tech demos for a second. Go talk to your customers. Talk to your frontline employees. What are the biggest points of friction in your business? Where are you wasting time and money? What are the dumb, repetitive tasks that are burning out your best people?
Make a list. A long one. Then, and only then, should you start asking, "Could AI help with this?"
Here’s a simple framework:
- Identify the Pain: Find a real, measurable problem. If you can't put a number on it (hours wasted, dollars lost, customer churn), it's not a good candidate.
- Brainstorm Solutions (AI and Non-AI): Think about all the ways you could solve the problem. Don't jump straight to the most complex AI solution. Would a better process work? A simple checklist? A different software tool?
- Run a Small Experiment: Once you have a promising idea, test it on a small scale. Don't try to boil the ocean. A pilot project with a clear goal is your best friend.
You're a Leader, Not a Babysitter: How to Manage an AI Team
Okay, so you’ve identified a real problem and you’re ready to build a team to solve it. How do you hire and manage a bunch of people who speak a language you don’t understand?
First, stop thinking of them as a mystical tribe of AI wizards. They're engineers. They're problem-solvers. And they need the same things any other high-performing team needs: a clear mission, the right resources, and the autonomy to do their best work.
When I was building the team at MovieLaLa (which we sold to Gfycat), I didn't look for the engineers with the most publications or the fanciest degrees. I looked for people who were obsessed with movies and understood how people discovered them. The tech was important, but the passion for the problem was everything.
Here’s how to manage a team of AI experts when you’re not one:
- Hire for Problem-Solving, Not for Buzzwords: Ask candidates to describe a time they solved a complex problem. It doesn't even have to be an AI problem. You're looking for a thought process, not a list of credentials. A great engineer can learn a new framework. A curious, tenacious mind is much harder to find.
- Set the 'What,' Not the 'How': Your job is to define the destination, not to draw the map. Give your team a clear, measurable goal. For example, "Reduce customer support tickets by 30% by automating responses to common questions." Then get out of their way and let them figure out the best way to get there. Micromanaging a team of experts is the fastest way to kill morale and innovation.
- Insist on Simple Explanations: Don't let your team hide behind jargon. If they can't explain what they're doing and why it matters in plain English, they probably don't understand it as well as they think they do. This isn't about dumbing things down; it's about ensuring everyone is aligned and focused on the business outcome.
- Create a Culture of Experimentation: AI is not a predictable field. Some things will work, and a lot of things won't. You have to create a safe environment for your team to fail. Celebrate the learnings, not just the wins. The only true failure is not trying something new.
The Real Work: A Step-by-Step Guide
This all sounds good in theory, but what does it actually look like in practice? Here’s a simple, step-by-step guide to get you started.
The 30-Day Listening Tour: For the first month, do nothing but listen. Talk to at least 20 people across your organization—from the C-suite to the interns. Ask them: "What is the dumbest, most repetitive, most soul-crushing part of your job?" You’ll be amazed at what you uncover. These are your starting points.
The One-Pager: For each promising problem you identify, write a one-page summary. No fancy slide decks. Just one page with these sections:
- The Problem: In one sentence, what is the pain point?
- The Impact: How much is this costing you? (e.g., "We spend 500 hours a month manually categorizing support tickets.")
- The Proposed Solution: A brief, non-technical description of how you might solve it.
- The Success Metric: How will you know if you’ve won? (e.g., "Reduce manual categorization time by 80%.")
The Pilot Project: Pick one—just one—of your one-pagers and run a 90-day pilot. Assemble a small, scrappy team. Give them a clear goal and a modest budget. The point here is not to build a perfect, scalable solution. The point is to learn. At the end of 90 days, you should have a clear answer to one question: "Is this idea worth pursuing further?"
The Go/No-Go Decision: After the pilot, make a decision. Is this working? Is it delivering real value? If yes, double down. Give the team more resources and a mandate to scale the solution. If no, kill it. Don’t let it become a zombie project that shuffles along for years, consuming resources and morale. Killing a project that isn’t working is not a failure; it’s a success. It means you’ve learned something valuable and can now redeploy those resources to a more promising idea.
This iterative, experimental approach is how you build a culture of innovation. It’s how you de-risk big bets. And it’s how you ensure that your AI initiatives are grounded in real business value, not just hype.
Measuring What Matters: The ROI of AI
How do you know if any of this is actually working? The CFO is going to want to see a return on investment. But the ROI of AI isn't always a simple dollar figure. Yes, cost savings and revenue growth are the holy grail. But don't underestimate the value of things that are harder to measure.
- Time Savings: How many hours are you giving back to your employees? What could they do with that time? Innovate? Talk to customers? Take a well-deserved break? At RemoteTeam, automating compliance paperwork didn't just save us money; it freed up our team to build better features.
- Employee Happiness: Are you eliminating the boring, repetitive tasks that nobody wants to do? A happier, more engaged team is a more productive and innovative team. This is a real, tangible benefit, even if it doesn't show up on a spreadsheet.
- Customer Satisfaction: Are you using AI to provide faster, more personalized service? A higher Net Promoter Score (NPS) is a leading indicator of future growth.
- Speed of Innovation: Is AI allowing you to test new ideas faster? To get products to market quicker? The ability to out-learn and out-iterate your competition is the ultimate competitive advantage.
Don't get trapped in a narrow view of ROI. Think bigger. Think about the second-order effects. The real magic of AI isn't just about optimizing the present; it's about unlocking a completely different future.
The Future is Built, Not Predicted
Look, nobody knows exactly what the future of AI holds. And anyone who tells you they do is selling something. But I can tell you this: the winners won't be the companies with the fanciest algorithms or the biggest data sets. The winners will be the ones who are most obsessed with solving real problems for real people.
Your job as a leader is to be the voice of the customer in the room. It’s to constantly ask, "Is this actually making someone's life better?" It’s to clear the path for your team to do their best work. And it’s to have the courage to kill the projects that aren’t working, no matter how much you’ve invested in them.
Don't be intimidated by the technology. Be obsessed with the problem. That’s how you lead an AI transformation. That’s how you build something that lasts.
Frequently Asked Questions
What are the most common mistakes when leading an ai transformation (even if you don't understand the tech)?
The biggest mistake I see is overcomplicating things early on. Start with the simplest version that works, get real feedback, and iterate from there. Another common trap is copying what worked for someone else without understanding the context behind their decisions.
How long does it take to lead an ai transformation (even if you don't understand the tech)?
The timeline varies depending on your starting point and resources. For most founders, expect 2-4 weeks for initial setup and 2-3 months to see meaningful results. I've seen teams move faster when they focus on one thing at a time rather than trying to do everything at once.
How do I measure success with this approach?
Pick one or two metrics that directly tie to your goal and track them weekly. Vanity metrics like page views or follower counts rarely matter. Focus on metrics that reflect real engagement or revenue impact.
Do I need technical skills to lead an ai transformation (even if you don't understand the tech)?
Not necessarily. While technical understanding helps, the most important skills are clear thinking and the ability to break problems into smaller pieces. Many successful founders I've invested in started with zero technical background and either learned enough to be dangerous or found the right technical partner.