AI Gave You a Great Plan. You Forgot to Tell It Why the Plan Won't Work.

You bring the plan to the floor. Someone glances at it for ten seconds and says the thing that kills it.

“Can't do that Tuesday, we've got two people out for cross-training.” Or, “That line's on lockout till Thursday, maintenance told us last week.”

You knew that. Everyone on the floor knew that. You just never thought to say it out loud, because it wasn't a secret. It was just Tuesday.

AI Doesn't Know What “Just Tuesday” Means

The constraint that broke your plan wasn't hidden from you. It was so obvious to everyone on your team that nobody thought it needed saying.

That's the whole problem. AI only knows what's in the room with it. If a constraint lives entirely in your head, or in a conversation from last week's shift huddle, AI has no way to know it exists, let alone factor it in.

Why the Obvious Thing Never Gets Said

Researchers call this the curse of knowledge. Once you know something, it's hard to imagine someone else not knowing it. Your team knows Tuesday's staffing pattern. The tool doesn't. It can't read a huddle from last week. The original research

You didn't forget to mention the cross-training gap because you were careless. You forgot because it's been true so long it stopped registering as information worth passing along. It just became part of how Tuesday works.

The fix starts with a strange question: what does your team know so well that nobody says it anymore? Ask it before you hand the plan to AI. The answer might be a qualification gap, a maintenance window, or the forklift that needs three tries to start. Nobody put that in the staffing spreadsheet.

This Has a Name Too, and a Real Cost

Some of this is tribal knowledge: the useful detail that travels between experienced people but never reaches the plan, SOP, or system. That does not make every workaround a good idea. It means a clean schedule can miss the way the job gets done.

It includes:

•      The shortcuts and workarounds nobody wrote down.

•      The sensory calls, “that sounds off,” that only come from years on the line.

•      The context behind why a rule exists, not just the rule itself.

When the one person who knows the fixture, the handoff, or the unwritten delay is out, the plan loses that context. AI can surface questions about it. A person still has to check the answers on the floor.

The Four Constraints That Go Missing Most Often

Start with four places where an innocent-looking assumption can wreck the shift. Your operation may have others.

•      Cross-training deficits: only one or two people can run a given station, no matter what the org chart implies.

•      Maintenance lockouts: equipment that's technically on the floor but not available.

•      Tooling changeover delays: the real time a swap takes, not the number on a spec sheet.

•      Dock bottlenecks: a receiving or shipping dock that can only move so much regardless of what the rest of the plan assumes.

Any one of these can quietly sink an otherwise solid plan. None of them show up unless somebody says them out loud.

The Prompt: Force It to Ask What You Forgot

Open Claude, ChatGPT, or a similar tool. Gather the draft plan, your shift roster, current equipment status, and the constraints you already know. Leave sensitive company details out of a public tool unless your employer has approved their use. Then adapt this prompt to your situation.

1. Set the Role

•      Ask it to act as a skeptical operations reviewer. Its first job is to challenge feasibility, not polish the wording.

•      Tell it to flag what it cannot verify from the information supplied.

2. Hand It the Data

•      Paste the full plan and its stated assumptions. Include the shift, line, target, timing, and any dependencies you already listed.

•      Add the current roster, equipment availability, and material or dock limits you are allowed to share.

3. Set the Constraints

•      Ask: “What missing constraint could make this plan impossible or much harder to run as written?”

•      Have it check at least three relevant categories, such as qualifications, lockouts, tooling, materials, and dock capacity.

•      Tell it not to assume full staffing, working equipment, or open capacity without evidence.

4. Define the Output

•      Return the plan with its assumptions stated plainly.

•      List the categories that need a floor check. Mark unknowns as unknown.

•      Write one direct question per category that the right person can answer on shift.

Take the questions to the people who know the work. Feed the answers back to the tool. Ask it to show exactly what changed in the plan. If a safety or quality rule is involved, follow your approval process before changing the work.

What Comes Back on a Real Plan

Ask it to build a plan moving two people from Line 1 to Line 3 for a rush order.

The plan

•      Reassign two operators from Line 1 to Line 3 for the shift, covering the rush order's staffing gap.

Constraint check

•      Cross-training: are both operators qualified to run Line 3's equipment, or only one of them?

•      Maintenance: is Line 3 fully operational right now, or is any part of it under a lockout?

•      Dock: can receiving keep pace with Line 3's faster cycle time, or does this just move the bottleneck downstream?

Three questions, all answerable on the floor in under a minute, all invisible to a tool that only ever saw the plan and not the reasons it might not work.

A Second Example: The Changeover That Wasn't in the Spec

Ask it to schedule three product changeovers into one shift instead of the usual two.

The plan

•      Sequence three changeovers across the shift, spaced evenly to keep the line moving.

Constraint check

•      Tooling: does the spec sheet's changeover time match what this specific line has really run recently, or is it the manual's optimistic number?

•      Cross-training: is the operator running the third changeover the same one who's been doing all the fast ones, or someone still learning the sequence?

•      Dock: will three changeovers in one shift trigger three separate material pulls, and can the dock keep pace with that?

Same shape as the first example, completely different plan. The pattern holds because the pattern was never about the plan. It was about which ordinary fact never made it into the room.

The Floor Check Comes Before the New Plan

Suppose the tool asks whether both operators can run Line 3. The roster says yes. You ask the lead and learn one operator last ran it six months ago. That is a staffing decision, not a prompt-writing problem.

Now check the schedule against the people and equipment that will carry it out. A fast pass takes three conversations: the lead who owns the assignment, maintenance if availability is uncertain, and the team that receives the extra output. You do not need a committee meeting. You need the three answers the plan depends on.

If one answer is no, put it back into the plan as a hard constraint. “Only one operator can run Line 3 without a refresher” is useful. “Staffing may be an issue” gives the model room to invent its way around the problem.

Ask for two options: a plan that works with today’s crew, and a plan that works only if training or maintenance clears the constraint. Label the condition beside the second option. That keeps a conditional plan from sneaking onto the floor as if someone had already approved it.

Before you use either option, check the handoff. Who will tell the next shift what changed? Where will you record the constraint so you do not rediscover it tomorrow? The aim is not to make AI sound cautious. It is to stop wasting a shift on a plan that only worked in a chat window.

Why This Beats Just Explaining Everything Upfront

Trying to list every possible constraint before asking for a plan is exhausting. You'll still forget something, because the curse of knowledge doesn't turn off just because you're trying harder.

Ask AI which categories need checking. Then ask the people who work the line for the facts. The tool can name a likely blind spot. It cannot tell you that Maria is the only person certified for a Tuesday changeover unless you give it that information.

Build a Running List Instead of Starting Over Each Time

A constraint check makes the missing information easier to spot. It does not certify the plan. If the answers change tomorrow, the check has to change too.

Keep a short, living list of your floor's standing constraints, who's really cross-trained on what, which equipment has a recurring maintenance pattern, where the dock tends to bottleneck during a rush. Update it when something changes, not on a schedule nobody keeps.

Hand that list to AI alongside the plan next time. Some of the next check becomes confirmation instead of starting from zero. Keep the list short enough to update. An old staffing roster makes a lovely document and a terrible plan.

Where This Connects

If the tool keeps guessing at your baseline, start with Your AI Doesn’t Know Your Operation. Stop Letting It Guess. It shows how to keep the standing facts in a short shift binder instead of retyping them every time.

For the related problem of a documented process that no longer matches the floor, read AI Read Your SOP. Too Bad Your Floor Doesn’t Follow It. A plan cannot use the right constraints when the process description itself is wrong.

Before Any Plan Leaves the Room

Run the constraint check before the plan goes anywhere near the floor, not after someone points out the obvious thing you forgot.

Want more prompts built for a real shift? Subscribe to The Daily Constraint and get the free “24 AI Prompts That Survive Contact with Your Floor” Field Guide. The next time AI hands you a polished plan, run the floor check before anyone changes an assignment.

What “everybody knows” fact has killed a plan on your floor? Tell me the one that should have been in the first draft.