When a fast path for experts removes the safety net a novice needs, something has to give

What it is

Accelerators and the base path can coexist because they're parallel routes to the same result, and neither blocks the other. But one kind of conflict can't be resolved by running things in parallel: at the same interaction point, making it faster for experts often means removing a safety net a novice needs (a confirmation dialog, a staged reveal, a delay before execution) — and that safety net's value comes precisely from sitting on the only path taken. Strip it out for speed, and it disappears for whoever takes that path, regardless of who they are.

Why it happens

Accelerators coexist peacefully with the base path because they form a parallel structure — which one a person picks doesn't affect whether the other remains available to someone else. The efficiency-versus-safety conflict happens at a single interaction point, which is a serial structure: that point either has the safety net or it doesn't, and there's no physical way to run "the expert version takes this path, the novice version takes that one" — because if the paths really were split apart, experts would soon end up on the no-safety-net path too, and (as the previous entry in this group establishes) an expert's automated behavior is exactly the condition under which this kind of error is most likely. Once that happens, the safety net stops working for anyone.

Where it stops holding

This conflict doesn't exist for every action. For a reversible, low-cost action, removing the confirmation step carries almost no added risk even for a novice, because the cost of a mistake is already low — there's no real tradeoff to make here, and the action can simply be optimized for speed. The conflict only arises for irreversible or high-cost actions, and it's only there that keeping or dropping the safety net is genuinely a decision worth weighing.

Applying it

• Base whether to keep a safety net on whether the action's consequence is reversible and how high its cost is — not on whether the user is experienced. Reversible, low-cost actions get an unconditional fast path for every user. Irreversible or high-cost actions unconditionally keep the safety net, even for the most senior users — an expert's proficiency doesn't lower the objective cost of this particular mistake, and it raises the odds of sliding into it.
• For irreversible, high-cost actions, don't resolve the conflict with an option like "experts can turn off the confirmation in settings" — that hands the decision of whether the safety net exists to the user's judgment in the moment, and this exact kind of error happens precisely when the user isn't exercising active judgment. The option itself won't help at that instant.
• Verification: list every action in the product that skips confirmation and executes directly, and check each one for whether its consequence is genuinely reversible and genuinely low-cost. Any action whose consequence is irreversible but skips the safety net because it's "aimed at expert users" has let efficiency wrongly override safety, and needs the safety net restored rather than keeping the skip option.

Related

• Same group: A11.04.2 Accelerators and the base path must coexist · A11.04.5 Expert automatization raises capture-error risk
• Adjacent: A10.08 Error tolerance and graceful degradation · A8.09 Speed–accuracy tradeoff
• Search: efficiency safety tradeoff · confirmation dialog debate · reversibility