Templates encode the designer’s task assumptions and actively mislead when those do not match real work

What it is

The designer thinks “handle a customer complaint” is apologize, compensate, close the ticket, and builds a template. The real frontline flow is: first decide whether this is a regulated complaint, then decide whether an apology is even allowed. Someone taps the template; the artifact walks the wrong flow and still looks professional. A designer-task assumption means a template is not a neutral empty frame. It writes one reading of the task as the default path. When the reading is wrong, the template actively leads people off, more harmful than an empty box — the empty box at least does not pretend to know the process.

A slot roster shaving expression is the right task with fewer dimensions said. A wrong assumption is the task itself swapped for another.

Why it happens

Templates come from that one “typical user, typical flow” in design research. Typical is a mean; real tasks sit on the tails: different countries, different regulators, different customer tiers. The most visible template on the entry is read as “this is how our company handles complaints,” and the assumption turns from description into norm. Once applied, later generation, QA, even a report to a manager walk the wrong norm, and the cost of correction is higher than having faced an empty box at the start.

A wrong frame also has a credible appearance. Complete structure, professional columns, fluent samples — exactly what “this looks like a serious handling form” asks for — so the error is harder for anyone outside the work to see. A messy draft from an empty box is easier to flag as “this isn’t right.”

Studying it

First, a task analysis uncontaminated by the template, with real branches drawn (regulated / not). Then give people who do the work a template that covers only the trunk and erases a critical branch. Code: whether they notice the missing branch, whether they still treat the artifact as sendable, whether on noticing they edit the template or look for another path. Independent variables: whether the template claims to be “the standard flow,” novice versus practiced at this task, distance between wrong frame and real flow (a missing optional step versus a missing legal gate). Dependent variables: uptake of the wrong frame, outbound-risk rating, rounds until the wrong frame is noticed.

Do not use the design team as participants. They will recognize their own assumption. Participants must do this job daily and must not have built the template.

Where it stops holding

When the task is highly standardized and locked by the same regulator (a specific filing), designer assumption and real task coincide, and the claim fails. If the template is explicitly “one way of writing, not your process,” normative force drops. Practiced people will swear at the missing branch on sight; novices and people covering a shift from another desk are the ones led off. This entry does not treat leftover dummy values — that is pollution at the value layer, not a swapped process.

Applying it

• Every outward template should name the situations it covers and the branches it explicitly does not. Uncovered branches must be tappable, leading to an empty box or another template, not to a forced fill.
• Review templates against real cases — including failures and regulated ones — not against the designer’s happy path.
• Frames the frontline has already edited must be able to flow back as official variants, or the assumption freezes at first ship.
• Check: give the template to frontline people who did not design it, with a real but “atypical” case. If the artifact omits a gate they would never omit (a regulation flag, an escalation path) and they still feel it can go out, the template is already actively misleading. Put that check on the template release list; do not only test the happy path.

Related

• Same group: L2.03.1 Templates lower the cost of getting started · L2.03.2 Templates constrain the range of what users will express · L2.03.3 Templates must be editable, not only fillable · L2.03.4 Templates turn open input back into structured blanks, at the cost of openness · L2.03.5 Placeholder content in templates is kept verbatim; empty slots must be unskippable · L2.03.7 A template that can only be applied whole, with its structure invisible, teaches nothing
• Nearby: L2.15 Ambiguity and Clarifying Follow-ups · L4.14 Plan Visibility and Revision for Multi-step Tasks · L1.02 Expressing Capability Boundaries
• Search terms: designer-task assumption · mismatched task template · wrong scaffold