Pretend you are the intern so vague task lists and hallway ownership fail before the next start date turns them into wasted weeks.
Optimistic managers optimize for the help they wish they had. The intern seat does the opposite. It asks which owner lives only in a chat thread, which doc is stale, which tool access arrives late, and which first-week win is impossible without context nobody wrote down. A polished task board is not evidence that a careful person can contribute without guessing.
This is one of the useful moves in a hiring or ops war game: after you describe the intern plan, seat a careful intern perspective and make it try to stall. The output you want is not theater. It is a short list of material gaps, the exhibits each needs, and the edits that would survive a real first month.
How to cast the seat
Name a real mandate: finish a defined first deliverable without heroics, protect production while learning, or underwrite a small customer handoff. Give constraints: the level you hired for, the evidence standard for "ready," and the residual risk you will not invent away. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in week one.
Write the seat into the prompt as a named role with a mandate. Example: "Intern: list the top reasons this plan would fail in your first thirty days, the claim with the weakest owner, the access or context gap that worries you most, and the ten diligence questions you would send your manager after day three. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons the task list would confuse or delay a careful intern.
- The claim that looks strongest and is least evidenced in the pack.
- The access, owner, or context gap that would worry you most.
- What would make you trust the plan enough to start without quiet workarounds.
- The ten hardest questions you would send in writing after day three.
Run that brief in Pingpong against the real onboarding doc, org chart, and access checklist. Follow with a home-team response pass so you leave with edits and named owners, not only fear. When the intern sits near customers or production, run this seat after manager and security attacks so it can use earlier objections as ammunition.
When the plan leans on a single buddy, a single wiki page, or a single chat channel, force the seat to price concentration risk in writing. Ask what happens if that buddy is out, if the wiki is stale, or if production access arrives after the first customer call. Concentration that only appears in an appendix still counts.
Pair with pretend you are the new hire, war-game a hiring plan, war-game a delegation framework, pretend you are the COO, and the war-game decisions hub. See how to run a Pingpong.