The useful answer
When someone says ‘It doesn’t work’, ask two small questions before suggesting a fix: ‘What were you trying to do?’ and ‘What happened instead?’ Then confirm the difference in one sentence. This turns a vague complaint into a shared, checkable description.
A workable response is: ‘You expected the document to open when you tapped the link, but you saw a message asking for access. Have I got that right?’ The listener is not diagnosing the fault yet. They are establishing what the words ‘doesn’t work’ refer to.
Did You Know? A complaint can describe an experience, not a cause
‘It doesn’t work’ often communicates a real inconvenience while leaving out the attempted action, expected result and observed event. The speaker may be frustrated, rushed or unfamiliar with the product. None of those circumstances proves carelessness.
Cambridge’s guide to follow-up questions explains how conversational questions respond to information just given. The British Council’s dealing with a problem lesson illustrates listening, clarifying and addressing a practical difficulty. The method here applies those language skills to finding a reproducible observation.
The language mechanism: expected result versus observed result
A sentence such as ‘The printer is broken’ compresses several possibilities into one label. The device might be disconnected, out of paper, powered off, or simply producing a page with an unexpected layout. Naming a cause too soon can send the conversation in the wrong direction.
Separate three layers: intention (‘I wanted to print page two’), action (‘I pressed Print’), and observation (‘nothing appeared in the tray’). Next, distinguish observation from interpretation: ‘No page came out’ is observable; ‘the printer driver is faulty’ is a hypothesis needing evidence.
The contrast is the repair. By asking what was meant to happen and what actually happened, both people can discuss the same event instead of competing guesses. This is not a specialist engineering protocol; it is a useful conversational discipline.
A four-part conversation repair
First, acknowledge the difficulty without endorsing an untested explanation: ‘That sounds frustrating. Let’s identify the step that failed.’ Acknowledgment keeps the exchange cooperative without promising a solution.
Second, ask for the intended task: ‘What were you trying to get done?’ The answer gives the problem a practical destination, such as opening a file, submitting homework or receiving a payment confirmation.
Third, request a single observable event: ‘When you pressed Submit, what did the screen show?’ Invite the exact message or visible behaviour, not an imagined reason. If the person cannot remember, ask them to describe what they do remember and mark the rest uncertain.
Fourth, paraphrase both sides: ‘You expected a confirmation screen; instead, the page returned to the form. We don’t yet know if the submission was saved.’ That final sentence prevents a claim of failure from becoming an invented fact.
Worked dialogue: a primary pupil and a learning task
Fictional classroom demonstration. Pupil: ‘The science activity doesn’t work.’ Teacher: ‘What did you expect after choosing the answer?’ Pupil: ‘The next question.’ Teacher: ‘What did you see?’ Pupil: ‘It stayed on the same question and showed a red note.’ Teacher: ‘Let’s read that note before trying again.’
The teacher did not treat ‘doesn’t work’ as a verdict on the pupil. The pupil learned to report a step and an observation. A useful follow-up is to invite the pupil to say the two pieces back: ‘I expected the next question, but I saw the same page with a note.’
Worked dialogue: a teenager in group work
Fictional school-project demonstration. Student A: ‘The shared spreadsheet is broken.’ Student B: ‘What are you trying to change?’ Student A: ‘The total in the last column.’ Student B: ‘What happens when you type the number?’ Student A: ‘I can type, but the total stays unchanged.’ Student B: ‘So the input changes but the displayed total does not. We can inspect the formula together.’
Notice that the final suggestion follows a description of the discrepancy. It does not start with ‘You must have done it wrong.’ The next technical step could establish a cause, but the conversation has already become clearer.
Worked dialogue: an adult at a service counter
Fictional everyday-life demonstration. Customer: ‘My card isn’t working.’ Staff member: ‘I’m sorry this has been inconvenient. Were you trying to make a payment or use another service?’ Customer: ‘Pay for a purchase.’ Staff member: ‘What response did the terminal display?’ Customer: ‘It said the transaction could not be completed.’ Staff member: ‘Thank you. Let’s check the transaction status before making another attempt.’
The staff member must not conclude that the account lacks funds or that a payment failed permanently. Those would be assertions about a system they have not checked. For financial, medical or safety-critical situations, the authorised service process remains necessary.
Worked dialogue: a remote workplace
Fictional teamwork demonstration. Colleague: ‘The upload failed.’ Coordinator: ‘What file and action are we talking about?’ Colleague: ‘The revised agenda, using the team folder.’ Coordinator: ‘What did you see after clicking Upload?’ Colleague: ‘A progress circle, then a timeout message.’ Coordinator: ‘We expected the file to appear in the folder but saw a timeout. Let’s verify whether a copy is present before uploading it again.’
That final check reduces the chance of creating two conflicting copies. In another context, such as a message to a teacher, the proper response may be to preserve the original error and ask for a submission alternative rather than improvise.
Tone and register: one purpose, different expressions
With a friend, ‘What were you trying to do, and what showed up?’ is natural. In class, ‘Which step did you reach, and what did you expect next?’ gives learners a manageable task. With a customer, ‘Could you tell me what you were attempting and the message you received?’ is more formal.
Formal does not have to mean vague. ‘We regret the inconvenience’ alone can sound detached when it does not lead to a useful question. Equally, a rapid series of five technical questions may overwhelm a nervous or younger listener. Start with one question, listen, then ask the next.
Misconceptions that block repair
Mistake one is equating a complaint with a diagnosis. ‘The Wi-Fi is broken’ may mean a single application does not load. Mistake two is challenging the person’s honesty: ‘It works for me, so you’re wrong.’ A different person’s success does not erase another observation.
Mistake three is asking only ‘Why?’ That question can pressure the reporter to invent a cause. Replace it with ‘What did you see?’ Mistake four is pretending that a repeated unsuccessful attempt necessarily improves understanding. If the action could send money, submit a form twice or change records, verify state before repeating it.
Diagnostic questions for the listener
Can I name the exact task? Can I tell what the person expected? Have they described an observed result? Am I quietly turning a possibility into a fact? Did I check whether this is the same screen, file, device or account? These questions are more useful than immediately naming an external culprit.
If the reply is ‘I don’t know’, reduce the load: ‘What was the last thing that appeared?’ or ‘Can you show me the message?’ If the speaker becomes upset, focus on acknowledgment and a safe next step rather than relentless interrogation.
Retrieval practice: say the repair without a script
Cover this paragraph and practise this two-line sequence: ‘What were you trying to make happen?’ followed by ‘What happened instead?’ Then paraphrase: ‘You expected X, but observed Y; the cause is not yet confirmed.’ A parent or teacher can replace X and Y with a different real-world situation each day.
Try three short scenarios from memory: a worksheet link opens the wrong chapter; a booking page shows a loading circle; a group-mate says that a chart is missing. For each, write one question about intention and one about observation. Check that neither question embeds a guess about fault.
A small application routine for the next month
In week one, identify expected and actual events in fictional examples. In week two, practise two-question dialogues with a partner, allowing the partner to answer in their own words. In week three, use the technique in harmless everyday problems such as finding a missing document or checking a school activity. In week four, have the learner independently state the discrepancy and a cautious next action.
The goal is not a claim about measured improvement; it is a reproducible practice pattern. Keep a short reflection: ‘I avoided guessing’, ‘I asked one useful follow-up’, or ‘I confirmed what the person saw’. If a case cannot be solved, the communication can still succeed by accurately describing the remaining uncertainty.
Guidance for parents, students and teachers
Parents can model this language when a child says ‘I can’t do it’: ask which step the child attempted and what happened, while taking care not to turn an emotional need into a technical interview. A child who is distressed may first need calm attention, not a diagnostic checklist.
Students can practise describing errors during Mathematics or Science work: ‘I expected the total to be 24, but the calculation gave 21’ or ‘I expected the bulb to light, but it stayed dark.’ A teacher can then check the method or setup without assuming the underlying cause.
Teachers can model the difference between checking an explanation and checking a result. The British Council discusses concept checking as a way to see what a learner actually understood, rather than relying only on a general ‘Do you understand?’ The same principle of asking a targeted question supports this repair.
Transfer beyond technology
This method also works when someone says a recipe ‘failed’, a meeting ‘went badly’ or an instruction ‘didn’t help’. Ask about the intended result and the observable event, then decide whether the next step is clarification, a practical remedy or a referral to someone authorised.
Do not use the formula to dismiss feelings. In relationship disagreements, the person’s experience matters even when the sequence of events is contested. The method helps describe what occurred; it does not determine whose emotions are valid. For language that is initially vague, see eduKate’s guide to precise follow-up questions.
Frequently asked questions
Is ‘What did you do?’ rude? It can sound accusatory, especially with sharp intonation. ‘What step were you trying when the problem appeared?’ is more specific and less blame-focused.
What if the person cannot describe an error message? Ask for one visible detail, let them show it if appropriate, or accurately note that the message is unknown. Avoid filling it in from memory.
Should I offer a fix immediately? Only when the remedy is obvious, low-risk and within your role. Otherwise establish the expected–actual difference first.
Can this help English learners? Yes. They can use simple frames such as ‘I wanted …’, ‘I pressed …’ and ‘I saw …’, gradually replacing vague labels with precise verbs and observations.
What if the situation is urgent or unsafe? Follow the applicable safety procedure or contact the responsible professional. These conversation questions are not a substitute for emergency or specialist response.