Mandates from leadership to adopt AI tools don’t speed up judgment. They flatten the autonomy that forces people to build judgment in the first place, and that flattened autonomy is harder to rebuild than any model.
Product teams hear the order and start routing every decision through the model. The stated goal is consistency and speed. The actual result is that no one practices the hard calls anymore, so the model has nothing reliable left to learn from.
This pattern shows up when the people closest to the work lose permission to refuse or reshape the tool. Once that permission disappears, the output quality stops mattering because the flattened autonomy has already done its damage upstream.
How a Mandate Produces Flattened Autonomy
John Wesley’s three rules offer a way to see the damage clearly. Do no harm. Do good. Stay in love with God. Applied to product work, the rules function as a test for whether an AI mandate preserves or destroys the conditions for sound decisions.
The first rule exposes the Meta failure. When leadership required every team to integrate large models into core workflows, the immediate effect was that engineers stopped questioning whether a generated suggestion actually fit the user context. Harm appeared as quiet degradation: models trained on past bad patterns kept surfacing them faster. Teams could no longer pause the loop because the mandate treated refusal as resistance rather than stewardship.
The second rule shows what doing good requires instead. Good in this setting means the tool must leave the person using it more capable of independent judgment after the session ends. Meta’s rollout measured adoption and token spend. It never measured whether product managers could still articulate why a feature should not ship. The rule forces that second measurement. Without it, the mandate produces volume that looks like progress while judgment atrophies.
The third rule asks whether the process keeps people connected to what actually matters. In Meta’s case the model became the intermediary for almost every review. Engineers lost direct contact with the original problem statements. The connection that should have been protected was the one between the person and the real user outcome. Once that link runs through an always-on model, the work stops forming people who can make hard calls without it.
Ministry and product teams repeat the pattern when they treat AI adoption as a compliance exercise. A children’s ministry platform once required every curriculum writer to run drafts through the model before human review. Volunteer completion rates dropped because the generated language no longer matched the seven-minute attention window the actual users had. The mandate protected the appearance of modern tooling while removing the writers’ ability to test language against real classrooms.
Another team at a large resource site mandated that all search-ranking experiments begin with model-generated hypotheses. The first three months produced statistically significant lifts on paper. The lifts disappeared once the team could no longer explain why a particular ranking change served the reader who opened the app on Sunday morning. The rule set had been inverted: the model came first, and human judgment became the optional check rather than the protected core.
Reversing Flattened Autonomy Before the Model Ships
What changes when autonomy is protected before the model ships is that the three rules regain their force. Teams keep explicit veto rights over any generated output that cannot be defended in plain language. They measure whether the tool leaves the user faster at the next unassisted decision. They refuse rollouts that insert the model between the worker and the person they ultimately serve.
The shift is small in process terms and large in outcome. A team that resists flattened autonomy by keeping veto rights will reject more suggestions early. That same team will also surface higher-quality uses of the model because the people making the calls still practice the judgment the model is meant to support.
Your Turn: Apply This Today
- Write the exact refusal script your team will use when a generated suggestion fails the three-rule test, then test it on the next three model outputs this week.
- Remove the model from the first draft stage of one workflow and require the human author to produce the initial version before any AI assistance is allowed.
- Track whether each team member can still explain the user problem in their own words after a full day of model-assisted work; log the explanations for two weeks.
- Set a hard limit of two model calls per decision until the person can state the downside of following the model’s recommendation without looking at it.
- Schedule a weekly 30-minute review where the only allowed topic is which recent model use reduced someone’s ability to decide without the tool, and remove that use from the workflow.
- Assign one person on each product squad the standing authority to block a mandated AI step if it cannot be defended against all three rules in a single sentence.
The same tension between top-down mandates and preserved judgment appears in The Mandate That Arrived Before the Workflow Existed and The Token Budget That Never Tied Back to Sunday.
I consult with product leaders and ministry technology teams on protecting team judgment during AI rollouts and measuring whether tools increase or decrease decision quality over time. Let’s talk.