When a person says, “That was done by design,” the phrase means the result or arrangement was intentional rather than accidental. A good response checks what was intended, by whom, and for what purpose before treating the outcome as a mistake or accusing somebody of a bad motive. Try: “Do you mean this feature was planned? What was it meant to achieve, and is that purpose still being met?”
The practical repair is feature → intended function → evidence of intention → actual effect → next check. An intentional feature can work well, work poorly, or produce an unintended side effect. Equally, something that looks deliberate may be a mistake. Do not jump from the phrase to either “the designers were right” or “someone did this to hurt us.”
What ‘by design’ means, and what it does not say
Cambridge Dictionary describes by design as “intentionally”. It is commonly contrasted with by accident. The phrase can describe a planned room layout, a feature of a product, a teaching activity, an administrative procedure or a pattern someone says was deliberately created. In each case, the intended object or outcome needs to be named.
Compare three statements: “The instructions have no diagrams.” “The instructions have no diagrams by design.” “The writer removed the diagrams to confuse us.” The first reports a feature. The second claims an intention but does not tell us why. The third alleges a particular harmful motive and would need substantially more evidence. They are not interchangeable.
Did you know? Intention, success and fairness are three separate questions
A team may intentionally shorten a form to make it easier to complete. That does not prove the shorter form is understandable. A teacher may intentionally leave space for a student’s own answer. That does not prove every learner understands the purpose. And a person’s good intention does not automatically make an outcome fair to everyone affected. A careful conversation can acknowledge intention while still checking actual effects.
The opposite confusion also matters. If a document has an obvious error, it is tempting to say, “They designed it badly on purpose.” But a mistake, unclear wording or technical limitation may be sufficient to explain what happened. Good English lets us name what we know without inventing a private mental state.
The PURPOSE–PROOF–EFFECT–REPAIR method
Purpose: ask which feature or behaviour was intended
Begin with a narrow referent. “Was the quiet section intentionally placed away from the entrance?” is easier to answer than “Was this whole system designed like that?” If the speaker is describing a person, distinguish deliberate actions from accidental outcomes. “Did you intentionally leave this section blank?” is not the same as “Why did you sabotage it?”
Proof: check how the claim about intention is known
Sometimes the responsible designer can explain the rationale directly. Sometimes a published specification, classroom instruction or project record gives the intended purpose. Sometimes a colleague is merely guessing. “The organiser told us this was deliberate” and “I think it must have been deliberate” have different evidential status. Ask one source question without demanding sensitive private planning documents.
Effect: ask what happened in practice
A plan can have one stated goal and several observed effects. Separate the two: “The layout was meant to make discussion easier. Some participants still cannot see the display.” Neither observation automatically disproves the intention. If users report a barrier, attend to the problem even when the original design was well meant. Do not make people prove bad intent before they can request a reasonable change.
Repair: agree whether to explain, test or revise
Some confusion disappears when the purpose is explained. Other problems need an alternate format, a demonstration, a different workflow or a properly authorised review. Avoid claiming a change is approved just because someone agrees that the feature is inconvenient. Finish with an action and an owner: “We will ask the responsible teacher which response format is expected before rewriting the worksheet.”
Fictional classroom dialogue: a worksheet with empty boxes
Fictional demonstration. Student: “The teacher forgot to put examples in these boxes.” Classmate: “Maybe the boxes are empty by design.” Student: “How do we find out?” Classmate: “The instruction says we should draw our own examples. Let’s check one with the teacher rather than filling every box with copied notes.” Teacher: “Yes. The blank spaces are for your examples; one completed box will show whether you understood the task.”
The classmate offers a hypothesis and then finds relevant instructions instead of presenting a guess as confirmed teacher intention. A teacher could use this conversation to teach learners how to distinguish the materials provided from the work they are supposed to produce. It is not an account of a real classroom.
Fictional home dialogue: a simplified household plan
Fictional demonstration. Parent: “The weekend checklist doesn’t include every little chore. That’s by design.” Child: “Does that mean we’re not responsible for anything else?” Parent: “No. I intended it to show the three shared priorities, not every possible task.” Child: “Then could we write ‘three priorities’ at the top so nobody thinks it’s the complete list?” Parent: “Good idea. We can make the scope clearer.”
The design decision is explained, and the family discovers an ambiguity. The wording can be improved without accusing the parent of being dishonest. With younger children, the easiest question is often “What is this for?” rather than “What was the underlying design rationale?”
Fictional workplace dialogue: an interface that hides details
Fictional demonstration. Colleague A: “The screen hides the extra fields by design.” Colleague B: “So the fields aren’t missing? When should they appear?” A: “They appear after someone selects the relevant request type.” B: “Can we test that path and check whether new users can discover it?” A: “Yes. I know the intended behaviour, but we haven’t tested everyone’s experience.”
The conversation separates product intention from usability evidence. A statement about design does not promise that every user can find, understand or access a feature. If a privacy or security requirement is involved, the appropriate authorised owner should confirm the rule rather than relying on an improvised explanation.
Fictional team dialogue: an unexpected delay
Fictional demonstration. Team member: “The handover takes an extra day. Is that a mistake?” Coordinator: “The review stage was added by design.” Team member: “What does it check, and who can see whether it is working?” Coordinator: “It is meant to detect missing information. We should compare actual cases before changing it.” Team member: “So the extra stage is deliberate, but its usefulness still needs evaluating.”
The phrase does not prove the extra step saves time or prevents mistakes. Instead, it identifies one intended control and opens a factual evaluation. Another team might have entirely different procedures. Avoid describing these fictional tasks as professional standards, universal requirements or measured outcomes.
When ‘by design’ is being used to defend something
A person may say “It’s by design” as a factual explanation, but the same words can sometimes function as a way to end criticism: “That’s just how it is.” Do not immediately accuse the speaker of evasion. Ask a specific question about the intended goal and the current effect: “I understand that the restriction was deliberate. Could we check whether the existing arrangement still serves the intended users?”
If the issue concerns a potentially harmful or inaccessible arrangement, an explanation of original intention is not a substitute for attending to the concern. Route serious safety, accessibility or policy questions to the appropriate responsible party. The goal is not to win a debate about whether somebody had good intentions; it is to understand what needs to be checked.
Register: casual, school, technical and formal
With a friend, “Was that on purpose?” is often enough. In a classroom, “Was the empty space intentional, and what should we put there?” makes the learning task explicit. In technical teamwork, “Is this documented intended behaviour or an unexpected defect?” is clearer than “This is badly designed.” In a formal report, identify the feature, its stated objective, the observed issue and the planned assessment separately.
The expression can sound neutral, proud or defensive depending on tone and context. Written messages have fewer vocal clues, so explicit reasons help. Avoid sarcastic replies such as “Great design, then,” unless you deliberately want to criticise; sarcasm rarely repairs a factual misunderstanding. Ask what the person meant and what evidence would resolve the question.
Common misconceptions
- “By design” means the outcome was good. No: an intentional feature may not achieve its goal.
- “By design” identifies a malicious motive. No: it only states intentionality; a particular motive needs evidence.
- If the effect was unplanned, the entire product was accidental. No: intended features can have unintended side effects.
- If a user dislikes a feature, the designer must have intended to exclude the user. Not necessarily: distinguish impact from inferred motive.
- Explaining the rationale automatically settles a complaint. No: observed barriers and reasonable alternatives may still need consideration.
Diagnostic questions: before you blame, praise or change
- Which specific element is described as intentional?
- Who knows the intended purpose, and where is it documented if that matters?
- What did the speaker actually observe, and what are they inferring?
- Does the result match the intended purpose for the relevant audience?
- What is one proportionate test, explanation or adjustment?
Choose one or two questions appropriate to the stakes. There is no need to interrogate every ordinary sentence. If the person has plainly explained the feature, the purpose and the observed effect, move on to the practical next step.
Retrieval practice: six short repair challenges
Challenge 1. A classmate says, “They made the test hard by design so we would fail.” Rewrite that as a checkable question about what the assessment was intended to measure, without guessing an examiner’s motive. Challenge 2. A team claims a missing button is “by design”, but no one knows whether it should appear for this user. Ask for an appropriate way to verify the expected behaviour.
Challenge 3. A parent leaves a short checklist on the fridge. The child says, “You forgot the other chores.” Write a reply that states the checklist’s intended scope. Challenge 4. A public information leaflet uses plain language by design. Suggest one respectful question that would check whether its readers actually understand it.
Challenge 5. A supervisor says a slow approval step is “by design”. Write a response distinguishing the purpose of the step from evidence that it works. Challenge 6. Someone says a colleague arrived late “by design”. Write a neutral alternative that does not claim to know their intention.
Model checks. For Challenge 1: “What kinds of questions was the assessment designed to test, and what instructions tell us that?” For Challenge 2: “Could we compare this user’s view with the documented expected behaviour?” For Challenge 6: “They arrived later than expected; I don’t know why.” The common skill is to move from motive attribution to a specific feature or fact that can be checked.
A seven-day application routine
On the first day, notice one use of “by design” and name its referent. On day two, practise replacing a speculative accusation with “Was this intentional?” On day three, distinguish intention from impact using a fictional example. On day four, rewrite a defensive explanation as a statement of purpose followed by an invitation to check. On day five, role-play a complaint about an intended feature. On day six, practise a formal written summary. On day seven, retrieve the five diagnostic questions without looking, then choose the two that matter most in a new situation.
Parents can teach children that noticing a problem is valuable, while guessing a person’s hidden motive is a different activity. Students can practise distinguishing an observed feature from an inference in English and Science. Teachers can use paired examples where the intended design and the actual result differ. Adult teams can record requirements and user feedback separately so a reasonable criticism is not mistaken for a personal attack.
Frequently asked questions
Is ‘by design’ the same as ‘on purpose’?
In most ordinary contexts, both communicate intention. “By design” often sounds a little more formal or focused on a planned arrangement.
Does it mean something is not a bug?
A person may use it that way, but the phrase alone does not establish correct technical behaviour. Confirm the relevant requirements and actual result.
What if the speaker cannot prove the claimed intention?
Keep the claim provisional: “This may have been intentional. We need to check with the responsible person or documentation.”
Can an intentional design still be unfair or hard to use?
Yes. Evaluation of access, fairness or effectiveness is separate from whether the feature was intended. Ask about actual effects and appropriate remedies.
How can I challenge it without sounding hostile?
Try: “I understand that was intentional. Could we look at the purpose and the effect on users?” This recognises the statement without presuming it answers every question.
Sources and related learning
Meaning and usage: Cambridge Dictionary: by design and Cambridge Dictionary: design and intention. Conversational practice: British Council LearnEnglish: Agreeing and disagreeing. For broader repair habits, see How English Works | Conversation and Repair, and for precise word use see What Is Vocabulary?. All dialogues and settings are fictional educational demonstrations; they are not observations, statistics or accounts of institutional policy.