A new coworker submits a polished proposal. It is clear, thorough, and confidently written. Then a senior colleague asks why the recommendation fits this customer, why one exception was made, or who owns the risk.

The work begins to collapse. Its author can repeat the answer but cannot explain the reasoning. The senior colleague checks the assumptions, reconstructs the missing company context, and rebuilds the decision.

On paper, AI accelerated the new hire. In practice, it transferred the unfinished thinking to the reviewer.

Productivity did not disappear. It changed owners.

We call this the rework tax: experienced-team time spent checking assumptions, locating missing context, and redoing the thinking behind polished but unowned output.

The tax is difficult to see in conventional productivity measures. The draft arrived quickly. The task was marked complete. The hidden cost appears in review cycles, quiet rewrites, extra meetings, and the attention of people whose time is already scarce.

The first draft got faster. The organization did not.

Repeated rework becomes contribution doubt

One weak draft is ordinary. A repeated pattern changes how the team sees the person. Colleagues begin to wonder what value the new coworker is actually adding. Managers hesitate to delegate consequential work. Trust narrows before the joiner has had a fair chance to demonstrate their strengths.

That doubt is real, but it is not necessarily evidence of a bad hire. Often the person has genuine domain ability. What they lack is the company-specific context needed to apply it: the history behind a constraint, the unwritten standard, the decision boundary, or the person whose judgment matters.

Generic AI conceals that gap because it can produce the form of competent work without access to the company reasoning underneath it.

Owned work can be tested

The answer is not to ban AI or demand that every draft begin from an empty page. It is to ask whether the person can exercise judgment through the tool.

Judgment-led work passes a simple test. The person can explain the reasoning and relevant context, adapt it when circumstances change, and defend or challenge the resulting decision.

That test changes onboarding from a race toward output into the development of grounded contributors—people who use AI while continuing to build judgment, relationships, and responsibility.