User
Write something
Access to AI is not the same as using it
Half of US employees use AI at least a few times a year. Only 15% use it every day, according to Gallup. In my team it started the same way. AI was a question box on the side of the screen. People asked it something now and then and kept doing their work the old way. I kept pushing: use it on your real work and you will get something out of it. After a while people started to see what it saved them. Everyone had access from the start, so I tracked something else: how many people used AI on real work in a normal week. That number went up. I would ask a client for it before I talk about training or tools. If you walked into a client's team tomorrow, how would you find out that number?
0
0
Access to AI is not the same as using it
At a client, look for the one task that changed
The first thing I check in a team is one task where people now split the work with AI. For quotes that can look like this: AI writes the first draft and a colleague checks it before it goes to the customer. Before AI, one person wrote the quote from start to finish. A team can have licences for everyone and no task like that yet. That team is experimenting, and that is where your work starts. At a client or in your own company, which task would you ask about first?
0
0
At a client, look for the one task that changed
Starting with AI as a team costs time first
Starting with AI as a team costs time first, often a few months. After that it pays off. Drawn as a line it looks like a J. My current team is working out where AI fits in the whole process. We change tools and processes at the same time, and we have to agree on both. The business wants to see value, and right now we can show little. I look at how fast the team picks up something new and gets it all the way through the process. That speed is where the value comes from later. If you lead a team in its first months with AI, measure that speed now. Then you have a number to show while the business waits. Is your team still in those first months? What do you measure?
0
0
Starting with AI as a team costs time first
The #1 YouTube mistake killing your reach (plus a $250 creator challenge for real case studies)
If there is one common denominator among creators stuck under 10k views, it is treating YouTube like a guessing game instead of testing repeatable mechanics. Here are 3 rapid-fire lessons that save creators hundreds of hours: The First 30 Seconds: If retention dips sharply before the 0:30 mark, cut your backstory and immediately fulfill the promise shown in your thumbnail and title. Proof Over Theory: Videos focused on real experiments, data breakdowns, and specific case studies consistently outperform generic advice and opinion pieces. Systematized Workflow: Scaling requires standardizing your packaging (CTR), intro hook, and retention curve before increasing your upload frequency. Question for the group: What is one single lesson, mistake, or breakthrough from your YouTube experience that saved you the most time once you figured it out?
0
0
AI will lie to your face with total confidence. Here's how I stop it
A while back Claude handed me a block of code built around a library that does not exist. Forty clean, well structured lines, using functions from a package I could not find anywhere online. It never once hinted it was making it up. I lost an hour before I realised the whole thing was fiction. That was not a one off. I have had it give me a SQL job that reported a result while nothing actually ran underneath. I have had it cite sources that were not from where it claimed, or were not real at all. Every single time it sounded certain. That is the dangerous part. It is never unsure. Here is what is going on. When a model does not know something, it does not stop. It fills the gap with the most likely looking answer. A plausible function name. A plausible date. A plausible source. It is built to always produce something, and "something" wins over "I don't know" every time, even when the something is wrong. Here is a live one. I asked for the EU AI Act key dates two ways. Straight from memory it told me the Act was in full force on 1 January 2025, with bans from mid 2024. Confident. Wrong. Then I forced it to work from sources only and search first. It came back with: in force 1 August 2024, bans apply 2 February 2025, GPAI rules 2 August 2025, fully applicable 2 August 2026. Every date now had a link I could open and check. Correct. Same model. Same question. The only difference was whether I let it guess. Here is why I care, and why you should. Everything you send or publish on a model's word carries your name, not the model's. The wrong figure in a report. The fake reference in a proposal. The library that does not exist in code you shipped. Right now people forgive it because "the AI wrote it". In six to twelve months that excuse is gone, the same way "sorry, autocorrect" stopped working. What you send this year is what people remember. So here is how you stop it. 1. Make it search before it answers. Do not ask "what are the EU AI Act dates". Ask "search for the EU AI Act dates and answer only from what you find". No result, no answer.
0
0
AI will lie to your face with total confidence. Here's how I stop it
1-9 of 9
AI Survivors
skool.com/ai-survivors
Make companies AI-first. Get your first paying client in 90 days. Learn the method I use myself.
Powered by