Every deliverable is a take-home test now

My kids are in school here in South Carolina. So when I started hearing what AI is doing inside classrooms, I didn't get to think about it as a consultant. I had to think about it as a dad.

The first thing I did was go looking at how schools are supposed to be handling this, and the short answer is that most are on their own. By one national tracker's count, twenty-eight states have published statewide frameworks for how K-12 schools should handle AI. South Carolina is not one of them. Some districts, like Charleston County, wrote their own classroom AI policy this year rather than keep waiting; private schools like my kids' were never going to be covered by a state plan in the first place. Which means that in most classrooms in my state, public or private, the front line of this whole question is one teacher, improvising.

Invisible ink and blue books

And you should see what the improvising looks like.

Teachers have started hiding instructions in their assignments in white, invisible text: something like "use this specific word in a way that makes no sense." A student who reads the assignment never sees it. A student who pastes the assignment into a chatbot hands the trap straight to the machine, and the essay comes back wearing it. When teachers share the results, the catch rates are not a few bad apples. They're most of the class.

College professors are running the cleaner experiment. Give a take-home midterm, then announce the final will be in person, on paper, no laptop. Some of the class drops the course the day the format is announced. Much of what remains fails. And a small number of students post the same grade on both, including, in one story that has stuck with me, a kid who scored in the low 60s twice. Not a star. Just honest.

I think about that kid a lot. If I'm hiring, I want the one whose numbers match. I have reached the point where I would rather work with an honest B student than a counterfeit A. The counterfeit A is worse than nothing, because I'll build plans on top of what I think that person can do.

Would I have resisted it? No.

Here's the part I have to be honest about before I say anything else, because it's the part most adults skip.

If you handed sixteen-year-old me a machine that could do my homework in thirty seconds, in a house that also contained video games, would I have written the essay myself? I'd love to tell you yes. He would not have. Maybe I'd have kept my own words and let it fix the grammar. Maybe less. I don't get to be sure, and neither do you.

That's why "kids these days" is the wrong reading of every story above. The temptation isn't a character flaw. It's structural. We handed students a machine that produces passing work on demand, assigned them work that's graded on the output, and act surprised that the output is what they optimized. Nearly whole classes are taking the deal. Whole classes are not made of bad kids.

When the output can be faked, the formation quietly stops, and nothing on the report card shows it.

And formation is the actual stake. A kid who never writes a bad first draft never learns to write a good one. Voice, in writing and in thinking, is built in the reps: the clumsy attempt, the correction, the slightly better attempt. A student can now skip every rep and still pass. The grade survives. The person the grade was supposed to be building doesn't get built.

Your business is running the same exam

If you run a company, you don't get to watch this from the bleachers, because the same structure is already sitting in your shop.

Every deliverable an employee hands you is a take-home test now. The proposal, the estimate, the report, the code: all of it can be produced by someone who understands it, or by someone who prompted it, and the two look identical on the day they're turned in.

I learned this the embarrassing way, and I tell the story in my book. One of our developers started shipping at a pace that impressed me, and I praised it. Then a subtle bug surfaced and I asked him to walk me through his own code. Not the tool's answer, his thinking. He could explain some of it. Not all of it. The machine had been doing the reasoning while he did the typing and approving, and I had built a culture that celebrated the speed without ever asking what he understood. My fault as much as his.

The scary part is that nobody in that story felt anything slipping, and the research says that's normal. When METR ran a randomized study of experienced developers, the developers believed AI had made them about 20 percent faster while the clock showed them 19 percent slower. If perception can miss that badly on speed, it misses at least that badly on skill.

The line I draw

I sell AI adoption for a living, and I tell owners every week that there has rarely been a better time to hand their admin work to it. I stand by that. The line is not "AI bad." The line is this:

• Some work exists to produce a result. Invoicing, scheduling, formatting, the follow-up email, the first pass over a long document. Automate it freely and don't look back.
• Some work exists to produce a person. The first attempt. The diagnosis. Explaining a decision. The junior employee reading the fortieth messy document, because the fortieth is when they start seeing what the clean version leaves out. This looks like waste on a spreadsheet. It's your training pipeline, at home and at work.

A school can pass every student and still fail to produce writers. A business can complete every task on schedule and still fail to produce the person who can handle the next hard one. Same failure. Same reason.

What to do this week

One move for the parent, one for the owner. They're the same move.

1. At home: don't ban the tool; you'll lose, and the ban teaches nothing. Set the rule I'd set for an employee: use whatever you want, and be ready to walk me through every sentence with the screen off. Then actually ask for the walkthrough, kindly, at the dinner table. What they can explain, they own. What they can't is where the learning stopped.
2. At work: make "own the output" the house rule this month, out loud. Anything with your name on it, you can defend without the tool in the room. Ask a teammate for one walkthrough this week, before anything is broken, so the question reads as culture and not as an accusation. If someone can't do it, that's not a firing conversation. It's a sign the work needs redesigning so the thinking stays with the human.

The schools will eventually publish their frameworks. Your business doesn't get to wait for one. Think first, AI second: at the office, and at the kitchen table.