Ethan Mollick has been arguing that the way capable people relate to powerful AI is quietly flipping. His framing: the human role is shifting from wizard to patron. A wizard knows the spells — the right prompts, the right sequence of steps, the clever workarounds — and steers the machine through the process. A patron does something older and simpler: commissions a work, describes what is wanted, and judges what comes back. With strong models like Fable, Mollick's claim is that the patron role is now enough.

In plain terms, the shift is from managing the how to owning the what and the whether. Instead of walking an assistant through a task step by step — draft this, now fix the second paragraph, now reformat it — you describe the outcome you want, let the system find its own path, and spend your effort where it counts: deciding whether the result is actually good. The skill that matters moves from prompt technique to judgment.

This idea is aimed squarely at non-technical users, and it matters to them for a specific reason. Much of the early advice about using AI well was essentially wizard training: learn the incantations, structure your prompts carefully, intervene constantly. That advice made interacting with AI feel like a job skill you had to acquire before you could benefit from it. The patron framing lowers that barrier. If the models are good enough to navigate the process themselves, then the entry requirement is something most people already have from ordinary life and work — knowing what you want and recognizing quality when you see it. You do not need to understand how the assistant produced a budget summary or a trip itinerary; you need to know whether the numbers make sense and whether the itinerary fits your constraints.

There is a real trade-off worth naming, because a vendor of powerful AI would not emphasize it. The patron model only works if your judgment is actually up to the task. A patron who cannot tell a good result from a plausible bad one is not commissioning work — they are rubber-stamping it. When an assistant handles the whole process invisibly, errors can be harder to spot than when you walked through each step yourself, because you never saw the intermediate reasoning. The shift Mollick describes does not remove effort; it relocates it. You still have to check the output, and for anything consequential — money, legal language, health decisions, facts you plan to repeat — that checking is the job, not a formality.

There is also an unresolved question underneath the claim: judging results is itself a skill, and it is easier in domains where you already have expertise. Commissioning a legal clause or a financial model is riskier than commissioning a dinner-party menu, precisely because your ability to evaluate the answer is weaker.

As for whether this is usable today: it is not a feature you turn on or a product to adopt. It is a description of how to work with the capable assistants that already exist, and in that sense it is applicable now — Mollick presents it as an observation about current tools, not a prediction about future ones. The practical consequence, if you accept the argument, is permission to stop micromanaging. If you find yourself dictating every step to an assistant, you may be doing the model's job for it. Describe the destination clearly, give it room to get there, and put your energy into the part no assistant can do for you: deciding whether what came back is what you actually wanted.