Stop Waiting for Permission to Use AI

Stop Waiting for Permission to Use AI

BackerLeader 40 209 347
calendar_today agoschedule3 min read

A recent survey from ResumeNow found that 41% of workers say their employer gives them zero guidance on using AI. Only 19% say they got real training, with dedicated time and resources behind it. Nearly a third say they got no training at all.

Meanwhile, the same companies are telling employees to "use AI more." That's like handing someone a new car with no keys and asking why they're not driving it.

Here's the thing. You don't need your employer's permission to start learning. You don't need a training program, a budget line, or a kickoff meeting. You need a few minutes of curiosity and a willingness to play around.

I started using AI for personal projects back in November 2021. Not because anyone at work told me to. I was just curious. Four and a half years later, AI touches almost everything I do, at home and at work. And the path that got me there didn't start with a business problem. It started with fun.

The $100 Vegas Challenge

A few years ago, I gave myself a simple goal: make $100 last as long as possible at video poker in Las Vegas. Instead of guessing at strategy, I used Claude to run real-time statistical analysis on the hands I was playing. Four or five hours later, I'd learned more about probability, pattern recognition, and decision-making under uncertainty than I'd expected from a casino floor -- and I still had some of my $100.

That's not a business case study. It's just a guy having fun with a new tool. But the skill underneath it, using AI to make sense of data in real time, is exactly what shows up later in enterprise work.

The 45-Page Manual

Another time, my wife had just bought a food steamer with a manual that ran 45 pages. She wanted me to help her cook a roast. Instead of reading the whole thing, I had AI break it down into the steps that actually mattered for what she was making. My wife was pleased with the outcome. More importantly, I walked away with a clear example of something AI does well: take something dense and confusing and turn it into something usable.

That's the same skill that matters when you're trying to explain a technical process to a non-technical audience, or when you're untangling a vendor's documentation for your team.

Why Personal Use Comes First

Personal experiments work because the stakes are low. If you ask AI for help with a recipe and it gets something wrong, nobody's job is on the line. That low-risk environment is exactly where you build the instincts you'll need later: how to phrase a request, how to spot a wrong answer, how much context the AI actually needs before it can help you.

I call this giving AI context, not just typing a question and hoping for the best. The more clearly you describe what you're trying to do and who it's for, the better the result. That's true whether you're asking for poker strategy or asking for a content plan for a Fortune 500 client.

Once you've built that instinct on your own time, it transfers. I've used the same approach to help simplify a six-petabyte intranet migration, redesign chatbot conversation flows for a healthcare client, and support a retail bank's effort to cut a 20-minute manual review down to about a minute with an AI agent. None of that started with a strategy deck. It started with a willingness to experiment somewhere low-stakes first.

A Realistic Way to Start

You don't need a six-week roadmap. You need a sequence that looks something like this:

Week 1: Try AI on something personal. A hobby, a household project, a question you'd normally Google.

Weeks 2-3: Bring one small work task to it. Something low-risk, where a wrong answer doesn't cost much.

Weeks 4-6: Apply what's working to a bigger project, once you trust your own judgment about when AI helps and when it doesn't.

Week 7 and beyond: Share what you've learned with your team. This is where individual habits start becoming team capability.

That progression matters more than any formal training program, because it builds judgment, not just familiarity with a tool. A training session can show you what buttons to click. It can't teach you when to trust the output and when to push back on it. Only practice does that.

The Real Gap

Companies asking employees to "use AI more" without giving them time or guidance to learn are setting people up to improvise. Improvising isn't a strategy. But individuals don't have to wait for their employer to fix that gap. You can close it yourself, starting with something as low-stakes as a video poker session or a recipe you're trying to get right.

So here's the actual question worth asking: what's your first AI adventure going to be? It doesn't need to be impressive. It just needs to be yours.

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

Helping Clients Move from Pilot to Production: The Agentic AI Governance Playbook

Tom Smithverified - Jun 8

AI Agents Don't Have Identities. That's Everyone's Problem.

Tom Smithverified - Mar 13

From Prompts to Goals: The Rise of Outcome-Driven Development

Tom Smithverified - Apr 11

The Sovereign Vault — A Comprehensive Guide to Protocol-Driven AI

Ken W. Algerverified - Jun 4

Your App Feels Smart, So Why Do Users Still Leave?

kajolshah - Feb 2
chevron_left
14.6k Points596 Badges
177Posts
109Comments
63Connections
LLM Training & Evaluation Specialist with hands-on experience building major AI models. As one of th... Show more

Related Jobs

View all jobs →

Commenters (This Week)

5 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!