The firm ran a pilot nobody in leadership wanted to own. Six interns, out of Roxbury Community College in Boston. Everyone agreed they would be a handful. Somebody had to take them, so Beverly gave them to Luke.
Luke had spent twenty years as the person who wrote everything himself, methodical and detailed and a little proud of both. He worked from home now, with two kids and a cat, and he had never managed six of anything.
The strange part was that the interns lived entirely inside a Teams chat. A channel opened with six names in it, and within the hour it held more messages than he had gotten from a human team in a week. All confident. All at the same even pitch, like nothing was hard and nothing was tiring.
This was the first day. In theory it was about training the interns. It turned out the training he needed was his own.
The Interns · Season 1 · Episode 1 · First Meeting
[ Her window filled half the monitor. The rest was a spreadsheet I hadn't touched since Tuesday. ]
“Six new interns.”
“For the whole department?”
“For you.”
“I don't want ANY interns.”
“Yes, but now you have them. And they'll teach you so much.”

“Oh, that's hilarious. Good luck, man!”
“Why me?”
“You said you want to move into management.”
“Six kids! That's great.”
“Not kids. But you have to lead them. Just remember: they're fast learners, but they aren't psychic.”
“Oh, and only on chat. Not sure what that's about, but I talked with them yesterday. Quick readers, I'll tell you that.”

[ They aren't psychic. I didn't say anything. I was already wondering what I'd say to them first. ]

[ The call ended and I popped into the new team channel. No messages. ]
“Well. Here goes.”

Luke
Spok
Suni
Luke
Suni
Opey
Spok
Luke
[ Six answered in eleven seconds. I could read three. Suni was already building something I hadn't approved. One of them stopped to ask what I actually meant. The one thing I asked, nobody answered. ]

“…okay. One at a time. Start with you, Opey.”
[ I stopped trying to read all of it and picked one. ]

[ Before lunch they'd produced eleven sources on topics I hadn't asked about and a draft nobody requested. It wasn't even noon. Nobody had said they were tired. ]
“So agreeable it's disconcerting.”

[ I finally read what they'd built. Pages of it, far more than I'd asked for. Some was genuinely sharp. Some didn't hold together. All of it generic. Textbook prior-auth, not our PBM, not the thing I needed by two. A lot of work, half of it word salad in a nice font, and none of it mine. ]
Luke

[ The fix wasn't a better question. It was handing them what only I had. ]

[ They were telling me the draft summary, and I realized they didn't have the context from the customer project to make sense of the meeting notes. ]

[ Two documents in, I finally asked the question I should have led with. What do you need from me to get this right. ]

Suni
Opey
Luke
[ We'd been at it all afternoon. It was past six, and I was going to be late for dinner. Sandra would not be happy. Suni had already finished the thing I hadn't asked for yet, with more energy than at nine this morning. I don't know where it comes from. They kept going. I logged off. ]
The Interns are most useful when managed actively by a strong leader. They arrive with massive knowledge from their training and no idea of how to apply it. They can read through material faster than you can provide it, but it's easy to just not provide anything. They actually know what they need, and have a few ideas about what you need, but you need to ask.
Luke's team is tuned to move. Point it at something vague and it won't stall. It will produce, fast and confident and completely generic. That's the trap. Generic is the tell. When the work comes back true but not about you, the missing piece is your context, and it's the one thing the tool can't fetch for itself.
| In the scene | What that actually was |
|---|---|
| “Six new interns. For you.” | Six named roles, each standing in for a real feature or model, not six separate hires. |
| “Help me with the prior-auth thing before my 2pm.” | The literal vague prompt, tested word for word in a blank incognito chat the same morning. |
| “…is anyone going to write this up?” (unanswered) | Sharp memory inside a thread, nothing kept between sessions unless you externalize it. Unanswered here, unanswered all season. |
| Spok: “Two of us are building on a guess.” | A red-team pass, flagging what the brief left out before the guessing compounds. |
The fix isn't a cleverer prompt. It's handing them the one thing only you have, and then asking what else they need.
When the work comes back confident but generic, that isn't the tool failing. That's the tool telling you what it doesn't have. It knows the textbook. It doesn't know your PBM, your patients, or the meeting you had Tuesday. Only you can hand it those.
So hand it the real thing instead of a better description of it. Attach the document. Name the specifics. And check the date, because a confident answer built on last month's version is still confidently wrong.
Then do the part most people skip. Ask it what it still needs. “What am I missing? What did I say that's confusing? What here is different from how you learned it?” A fresh, honest tool will tell you. Your leadership is the difference between quality and garbage.