Source A: The two-second gap

An original contemporary non-fiction-style practice text, written for this question.

Two seconds is long enough for someone to decide that you are failing. At a live public meeting, the words spoken on stage appear on a screen after I type them. If the screen remains empty for a moment, heads turn towards my desk. The audience cannot see the choices collecting behind that blank space; they see only that the speaker has moved on and I have not.

Before each event, I receive a list of names and technical terms. During it, I must separate voices when people interrupt one another, decide where unfinished sentences belong and avoid turning a hesitation into a statement the speaker never intended. Speed matters. People need the captions while the discussion is still happening. Yet an immediate word can be more misleading than a delayed one.

I learned this during a debate in which a speaker began, ‘We can approve the proposal...’ My fingers reached the end of the sentence before he did. Then he added, ‘...not in its present form.’ Had I released the first phrase immediately, the screen would have announced the opposite of his position. I waited, removed three words and entered the complete thought. To the audience, there had been a gap. To me, there had been a decision.

That does not mean every delay is evidence of care. At another event, I failed to recognise a place name and spent too long trying to rescue it from memory. By the time I checked the prepared list, several sentences had passed. My later correction was accurate, but accuracy arriving after the discussion had changed direction was less useful than I wanted to admit.

The organiser suggested that I should ‘type with more confidence’. I understood the complaint, although not the solution. Confidence could not make an unclear word clearer. Pretending certainty would simply hide the problem until it appeared in public. Instead, we changed the preparation. Speakers supplied key names in advance, and I used a brief notice when words could not be confirmed immediately. I also learned to correct an error plainly rather than allowing pride to defend it.

The new routine made my judgement more visible. People still noticed pauses, but they were less likely to read every pause as panic. I became quicker because I was better prepared, not because I had stopped checking meaning. The screen taught me that competence is not the absence of hesitation. It is knowing what the hesitation is for, communicating when necessary and recognising when the moment for caution has passed.

Source B: The answer at the counter

An original contemporary non-fiction-style practice text, written for this question.

When I began helping at a community bicycle workshop, I wanted to sound like someone who belonged behind the counter. Customers arrived describing clicks, wobbles and sudden slips. I thought expertise meant naming the fault before they had finished describing it. A quick answer seemed generous: it saved time, removed uncertainty and sent the customer away believing that the bicycle was understood.

The senior mechanic rarely performed that kind of certainty. She asked when the problem happened, whether it changed on hills and what had already been adjusted. Sometimes she turned the pedals and listened without speaking. Customers occasionally watched this process with disappointment. They had brought us a problem and expected us to produce its name.

One afternoon, a customer said that the chain slipped whenever he pushed hard on the pedals. I announced that the chain was worn and would need replacing. The senior mechanic asked me to test the bicycle first. The chain itself was serviceable; a small adjustment elsewhere solved the problem. My confident answer would have cost the customer money and failed to repair the fault. I had mistaken the speed of my conclusion for the quality of it.

After that, I became cautious in a way that was almost theatrical. I asked long lists of questions and avoided firm statements, even when the evidence was clear. This looked thoughtful, but it was partly fear of being wrong again. The senior mechanic exposed that mistake too. When a rider arrived with a brake that did not slow the wheel, she stopped him from riding away before beginning a fuller inspection. Uncertainty about the cause did not create uncertainty about the immediate risk.

Watching her, I realised that she was not simply slower than I was. She separated the decisions that had to be made now from those that needed more evidence. She could say, ‘This is not safe to ride,’ with complete directness and then say, ‘I do not yet know which part has caused it.’ Neither sentence weakened the other.

Customers still respond warmly to fluent explanations, and a workshop cannot examine one bicycle all day. Speed and confidence have value when they are supported by attention. The danger comes when they become a performance designed to protect the mechanic rather than the customer. I no longer try to have the first answer at the counter. I try to know when enough evidence exists for an answer, and when honesty requires one more question.