Why Do We Sometimes Mistake Speed for Competence?

Ask two people the same difficult question. The first answers almost immediately, speaking smoothly and without hesitation. The second pauses, asks for a moment to think, considers two possibilities, and then responds. Even before examining what either person actually said, it can be surprisingly easy to form an impression: the first person seems to know the answer, while the second seems less certain. Sometimes that impression is justified. Expertise really can make certain decisions and responses faster. But speed and competence are not the same thing, and confusing them can affect how we judge other people, how we behave when we want to appear capable, and even how we judge our own thinking.

Everyday life gives speed a great deal of visibility. We notice how quickly someone responds to a question, solves a problem, completes a task, understands instructions, or makes a decision. The quality of the underlying process can be harder to see. We may not know what information the person considered, what assumptions they made, whether they checked their answer, or whether the result will still look good tomorrow. Speed arrives first, so it can become part of our judgment before quality has had time to reveal itself.

This does not mean that fast performance is suspicious or that careful thinking must always be slow. In many situations, speed is precisely what experience produces. A skilled person may recognize a familiar pattern almost immediately because they have encountered similar situations hundreds of times. The important distinction is that speed can sometimes be a consequence of competence without being reliable proof of competence by itself.

Fast Answers Give Us an Immediate Signal

When someone responds quickly, we receive information before we have evaluated the content of the response. There is no long silence to interpret, no visible search for words, and no obvious uncertainty. The interaction moves smoothly. That smoothness can itself influence the impression we form.

Imagine asking for directions. One person immediately says, “Take the second street on the left, continue for two blocks, and it will be opposite the pharmacy.” Another says, “Wait, I think it’s the second street… let me make sure.” Before either route has been tested, the first answer may feel more trustworthy because it was delivered with greater fluency.

Yet the first person could be confidently mistaken, while the second may be accurately checking a detail before sending us in the wrong direction. Response speed gives us a clue about certainty, familiarity, personality, or preparation, but it does not independently verify the answer.

Expertise Really Can Make Some Things Faster

There is a reason we associate speed with skill. Practice changes what a task requires from us. A beginner may need to consciously remember each step of a familiar procedure, while someone with years of experience can perform much of it with little visible effort. A new employee may spend several minutes finding an option in a software system that an experienced colleague locates immediately. A musician learning a piece may consciously think about individual notes that an experienced player recognizes as familiar patterns.

In such situations, faster performance can reflect knowledge. The expert is not necessarily skipping thought. Some of the work that once required deliberate attention has become familiar enough to be handled efficiently.

But this relationship can create an incorrect shortcut in the opposite direction. If expertise can produce speed, we may start assuming that speed demonstrates expertise. That conclusion does not always follow. A person can answer quickly because they recognize the problem, but they can also answer quickly because they have not noticed its complexity.

Familiar Problems and New Problems Should Not Be Judged by the Same Clock

A mechanic who has seen the same problem many times may recognize it within moments. Give the same mechanic an unusual failure involving several interacting causes, and careful diagnosis may take considerably longer. The slower response does not mean the mechanic suddenly became less skilled. The problem changed.

This distinction appears outside technical expertise too. Someone may answer routine questions about their work effortlessly but need time when asked to predict an unfamiliar outcome. A manager may make a common scheduling decision quickly but spend days considering a decision that affects several employees. A writer may immediately improve a familiar sentence while needing an afternoon to decide how an entire argument should be structured.

When we compare response times without comparing the problems being solved, we can mistake task familiarity for general ability. The person who answers one question in ten seconds and another in ten minutes has not necessarily become ten times less competent. The second question may simply require a different kind of thinking.

Visible Hesitation Can Look Like Lack of Knowledge

Hesitation is easy to observe. Someone stops in the middle of an explanation, corrects a word, says “I’m not sure,” or asks to check something before continuing. Because uncertainty becomes visible, we may lower our confidence in the speaker.

Sometimes that is appropriate. If someone is uncertain about a fact, we should not pretend their answer carries the same confidence as a well-established one. But visible uncertainty can also reflect intellectual care. A person may know enough about a subject to recognize that the simple answer has exceptions. They may distinguish between what they remember clearly and what they need to verify. They may notice that the question can be interpreted in two ways.

Meanwhile, someone with less knowledge may not see those complications at all. Their answer can therefore sound simpler, faster, and more certain precisely because fewer possibilities are being considered.

Knowing More Can Sometimes Make an Answer Take Longer

Imagine asking whether a particular strategy “works.” Someone with limited experience might immediately say yes because they have seen it work once. Someone with broader experience may hesitate because the word “works” raises several questions. For whom? Under what conditions? Compared with what alternative? Over what period? What counts as success?

The second person’s hesitation does not necessarily mean they know less. Their knowledge may have made the question larger. They have encountered enough variation to know that an answer without conditions could be misleading.

This is one reason expertise does not always look like certainty. Greater knowledge can make some judgments faster through pattern recognition, while making other judgments more cautious because the person can see distinctions that were previously invisible.

Confidence and Speed Can Reinforce Each Other

People who feel confident about an answer may respond faster because they see little reason to reconsider it. That rapid delivery can then make them appear even more confident to the listener. Speed and confidence become mutually reinforcing signals, although neither one guarantees accuracy.

This can be particularly persuasive in conversation because listeners often have limited time to evaluate every claim independently. If one person speaks decisively while another repeatedly qualifies their statements, the decisive speaker may appear more knowledgeable even when the qualifications are important.

There is nothing inherently wrong with confident communication. Problems arise when presentation becomes a substitute for examining the substance of what was said. A useful question is not merely “Who sounded as though they knew?” but “What reasons, evidence, or explanation support the answer?”

Some Environments Reward an Answer Before They Reward a Good Answer

Speed can become especially important in environments where responses are public and immediate. In a meeting, the person who answers first occupies the conversational space before others have finished thinking. In a classroom, quick responses can be more visible than careful reasoning that takes longer. In online discussions, an immediate reaction may receive attention before a more considered explanation appears.

These environments can subtly teach people that appearing capable requires minimizing hesitation. Someone may begin speaking before they have fully formed their answer because silence feels riskier than an imperfect response. Another person may avoid saying “I need to check that” because verification could be interpreted as not knowing.

The result is an interesting mismatch: a setting may claim to value accuracy while socially rewarding immediacy. When that happens repeatedly, people can learn to optimize how quickly competence becomes visible rather than how carefully a problem is actually handled.

We Can Apply the Same Standard to Ourselves

The confusion between speed and competence does not only affect how we judge other people. We can use it against ourselves. A task that once took twenty minutes now takes an hour, and we immediately wonder what is wrong. A decision refuses to become clear after several days, and we interpret the delay as evidence that we are bad at deciding. Someone else understands an explanation quickly while we need to read it twice, and we conclude that they are simply more capable.

But time alone does not reveal what is happening. Perhaps the current task contains details the earlier one did not. Perhaps the decision has consequences worth examining. Perhaps the explanation assumes knowledge we have not previously encountered. Perhaps the other person already knows something related to the subject.

Without accounting for these differences, we compare completion times as though everyone started from the same place and solved the same problem.

Pressure to Look Competent Can Make Us Answer Before We Are Ready

If taking time feels like displaying weakness, the obvious response is to hide the time we need. We answer the email before checking one uncertain detail. We give an estimate even though we have not examined the work. We agree that we understand instructions rather than asking the question that would reveal we do not. We offer an opinion in a conversation because everyone else seems to have one already.

These behaviors can protect the appearance of competence for a few minutes while increasing the possibility of problems later. A rushed estimate may need correction. Unclear instructions may produce work that must be redone. A confident answer may become harder to retract once someone acts on it.

Sometimes the most competent response available is not an immediate answer but an accurate description of what is still needed: “I need to check that figure.” “I understand most of it, but this part is unclear.” “I don’t have enough information to give you a reliable estimate yet.” Such responses may sound less impressive than instant certainty, but they can protect the quality of what happens next.

Quick Decisions and Good Decisions Are Different Questions

A decision can be evaluated in several ways. How quickly was it made? How much information was available? Was the reasoning appropriate? Were the important risks considered? Did the decision produce a good outcome? These questions are related, but they are not interchangeable.

Sometimes delay adds nothing. We already have the relevant information, the consequences are minor, and additional thinking simply repeats the same arguments. Choosing between two ordinary options may not improve after another three hours of analysis. In that situation, speed can be useful because there is little value in waiting.

In other situations, additional time allows something important to happen. We obtain missing information, notice an assumption, compare alternatives, calculate a cost, ask another person, or allow an initial emotional reaction to stop dominating the decision. The value comes not from slowness itself but from what becomes possible during the additional time.

Taking Longer Does Not Automatically Make Thinking Better

It would be easy to correct our bias toward speed by creating the opposite rule: careful people take their time, therefore slower thinking must be better. That would simply replace one unreliable shortcut with another.

People can spend a long time thinking without improving a decision. We can revisit the same information repeatedly, search for certainty that the situation cannot provide, add irrelevant details, or postpone choosing because every option has a disadvantage. More time is useful only when something productive happens with it.

A ten-minute decision based on the relevant information can be better than a three-day decision spent circling the same uncertainty. Likewise, a three-day investigation can be better than a ten-second answer when important information needs to be gathered. The clock cannot tell us which process occurred.

Efficiency Is Not Simply Doing Everything Faster

We often describe an efficient person as someone who moves quickly, but efficiency is better understood in relation to resources and results. Finishing a task rapidly and then spending twice as long repairing preventable errors is not necessarily efficient. Neither is taking enormous amounts of time to perfect details that have little effect on the result.

The useful question is what level of time and attention the task deserves. A routine message may require only a quick check. A contract, important calculation, major purchase, or consequential decision may justify considerably more verification. Treating both tasks with identical speed would not demonstrate consistent competence; it could demonstrate failure to distinguish their stakes.

Competence Includes Knowing When Speed Matters

There are situations in which speed is genuinely part of performance. Emergency responses, timed competitions, live technical problems, customer queues, and many professional tasks can require accurate action within limited time. In those contexts, saying that speed does not matter would be unrealistic.

But even there, competence is not speed in isolation. A fast response that repeatedly produces incorrect outcomes is not equivalent to a fast and accurate one. Skilled performance often involves knowing which decisions can be made immediately, which require verification, and which warning signs justify slowing the process down.

That distinction is more interesting than simply asking whether someone is fast. It asks whether the person can adjust the amount of thought to the demands of the situation.

Sometimes the Fastest Person Had a Head Start We Cannot See

Two people may appear to begin the same task at the same moment while bringing very different histories to it. One has solved similar problems before. One knows the software. One recognizes the terminology. One already made a related decision last week. One has a template ready. What looks like exceptional speed in the visible task may partly reflect work, experience, or preparation that occurred earlier.

This matters when we compare ourselves with others. We usually see their completion time, not all the learning that preceded it. Someone who writes a polished explanation in fifteen minutes may have spent years learning the subject. Someone who immediately knows what to do in a familiar professional situation may be drawing on hundreds of previous examples.

Speed can therefore hide history. The final action is quick because part of the problem has already been solved before the clock we are watching began.

The Better Question Is What the Task Requires

Instead of deciding that faster is more competent or slower is more thoughtful, we can ask a more specific question: what does this particular task require? Does it reward rapid recognition? Does it contain unfamiliar information? Are errors easily reversible? Does someone else depend on the answer? Is there useful information we could obtain by waiting? Would additional time actually change anything?

Those questions shift attention away from the appearance of thinking and toward its function. Sometimes competence will look impressively fast. Sometimes it will look like a pause. Sometimes it will look like checking a fact everyone else assumed was correct. Sometimes it will look like deciding quickly because there is genuinely nothing important left to investigate.

The time taken becomes one piece of information rather than the verdict itself.

Research Gives Us a Good Reason Not to Equate Thinking Time With Thinking Quality

Research on response time provides an important warning against replacing “faster is better” with the opposite assumption that slower thinking must always be better. In a study involving 391 participants, Stupple and colleagues examined response times on the Cognitive Reflection Test, a small set of reasoning problems designed in part to capture the tendency to move beyond an initially appealing response. The researchers found only a weak relationship between response time and accuracy overall, and for two of the three problems they did not find the response-time differences that a simple “incorrect intuitive answers are fast, correct reflective answers are slow” account would predict.

The study concerns a specific reasoning task, so it should not be generalized into a claim about every kind of decision or everyday performance. That limitation is precisely what makes it useful here. It demonstrates why response time alone is an incomplete measure of thinking quality. A longer answer is not automatically more thoughtful, just as a faster answer is not automatically more competent. What happened during that time, what kind of problem was being solved, and whether the reasoning produced an accurate or useful result all matter.

You can read the full scientific article for free on PubMed Central: Slower is not always better: Response-time evidence clarifies the limited role of miserly information processing in the Cognitive Reflection Test.

Some Tasks Have a Speed–Accuracy Trade-Off

There are situations in which working faster changes more than the amount of time a task takes. It can also change the probability of noticing an error. Reading a paragraph rapidly may be perfectly adequate when we only need its general meaning, but the same reading speed may be inappropriate when checking a contract for a particular clause. Entering information quickly can save time when mistakes are easily corrected, while the same approach becomes more costly when an incorrect entry triggers a difficult process to reverse.

This means that asking whether someone is “fast” is less informative than asking what they are trading for that speed. Sometimes nothing important is being sacrificed because experience has genuinely made the task efficient. Sometimes a small reduction in precision is acceptable because the decision is low-stakes. At other times, the seconds saved are insignificant compared with the consequences of an avoidable mistake.

Competence therefore includes calibration. It involves recognizing when a quick approximation is sufficient and when the situation deserves another check. The same person can appropriately move quickly through one task and slowly through another without either pace defining their general ability.

The Cost of an Error Should Influence How Much Time We Give a Decision

Imagine choosing what to order for lunch and choosing which apartment to rent for the next year. Both are decisions, but treating them with the same amount of analysis would make little sense. If lunch is disappointing, the consequence is usually temporary. An unsuitable apartment can affect finances, commuting, comfort, and daily life for months.

This seems obvious when the examples are dramatically different, yet we do not always apply the same distinction to smaller decisions. We can spend twenty minutes comparing inexpensive items online while responding too quickly to a message whose wording may affect an important relationship. We may carefully organize an unimportant document while approving a consequential decision because someone is waiting for an immediate answer.

The amount of time something deserves is not determined solely by how complicated it feels. Reversibility and consequences matter too. When an error is cheap and easily corrected, speed may be sensible. When an error is expensive, difficult to reverse, or likely to affect other people, verification becomes more valuable.

Knowing When to Check Is Part of Expertise

Expertise is sometimes imagined as reaching a point where checking is no longer necessary. In many real situations, however, skilled people develop a better understanding of what needs checking. They may move rapidly through familiar parts of a task while slowing down at particular points where errors are common or consequences are significant.

This produces a form of uneven speed that can look less impressive than constant rapid performance. Someone might complete most of a process quickly and then spend several minutes verifying one detail. From the outside, that pause can look inefficient. From inside the task, it may be exactly where additional attention has the greatest value.

A person who checks everything repeatedly may waste time, while someone who checks nothing may create preventable errors. Competence can lie between those extremes: knowing which uncertainties deserve investigation and which do not.

“I Don’t Know Yet” Can Contain More Information Than an Immediate Guess

There are moments when people expect an answer even though the available information does not support one. How long will the project take? Why did this happen? Which option is going to work? What will the final cost be? The social pressure created by a direct question can make an estimate feel better than an admission of uncertainty.

But “I don’t know yet” can be a precise answer when followed by an explanation of what is missing. “I need the final measurements before I can estimate the cost.” “There are two possible causes, and I can’t distinguish between them from what we know.” “I can give you a rough estimate now or a more reliable one after I check the figures.”

These answers do not eliminate uncertainty; they describe it. That can be more useful than filling the silence with a number or conclusion that appears precise but has little support behind it.

Good Questions Can Make Someone Look Slower Before They Make Them More Accurate

A person who immediately begins solving the problem may appear faster than someone who first asks questions. Yet clarification can prevent considerable wasted effort. “Which version do you need?” “What does success mean here?” “Is this deadline fixed?” “Are we comparing total cost or monthly cost?” “Does this include the previous data?”

Those questions delay visible production because nothing has been completed yet. But they can change what gets produced. Ten minutes spent clarifying the task may prevent two hours of solving the wrong problem.

This is another reason completion speed can be misleading when we observe only the final stage. Some people spend more time before acting because they are defining the problem. Others begin immediately and discover later that the original interpretation was incomplete. The person who appeared slower at minute five may be substantially further ahead at hour two.

Preparation Can Move Thinking Outside the Moment We Measure

When a presentation looks effortless, we may attribute the smoothness entirely to the speaker’s ability to think quickly. But perhaps they anticipated the questions, reviewed the numbers, organized examples, and rehearsed the explanation beforehand. The visible response is fast because much of the thinking happened earlier.

The same thing occurs in writing, meetings, interviews, teaching, customer service, and countless routine tasks. Templates, checklists, experience, notes, and previous decisions reduce the amount of work required in the visible moment. What appears to be spontaneous competence can partly be prepared competence.

This does not make the performance less skilled. Preparation itself can be part of skill. It simply reminds us that measuring only the seconds between question and answer ignores everything that made those seconds possible.

Repeating a Task Can Make Us Faster Without Making Us Better at Everything

Practice often improves speed because repeated tasks become more familiar. But improvement can be highly specific. Someone who becomes extremely efficient at preparing one type of report has not necessarily become equally fast at every form of analysis. Someone who answers familiar customer questions rapidly may still need substantial time when encountering an unusual case.

This distinction protects us from turning task-specific fluency into a global judgment about intelligence or competence. A beginner may look slow beside an experienced person because the beginner is still learning the structure of the task. That does not tell us how capable the beginner will become once the same structure becomes familiar.

Likewise, being unusually fast at a familiar task does not guarantee superior reasoning when the situation changes. Sometimes familiarity is exactly what produces the speed.

A Fast Routine Can Become a Problem When the Situation Quietly Changes

Efficiency built through repetition has a potential disadvantage: we can become so familiar with a process that we stop noticing when the problem is no longer the same. The usual answer arrives quickly because it has worked many times before. A small new detail may be overlooked precisely because everything else looks familiar.

This is why unusual cases often deserve a deliberate interruption of routine. The question becomes not only “Do I recognize this?” but “Is there anything here that makes the familiar response inappropriate?” Expertise can help someone recognize the pattern quickly, but expertise can also involve recognizing the exception.

Fast pattern recognition is valuable when the pattern genuinely fits. The ability to stop relying on it when something does not fit can be equally valuable.

We Often See Other People’s Output but Not Their Corrections

Comparisons become particularly misleading when we judge ourselves against finished work. We see someone’s polished article, completed design, successful presentation, or confident explanation without seeing discarded drafts, corrected errors, previous attempts, preparation, or feedback from other people.

Then we compare their finished product with our active process. Our pauses are visible to us. Our uncertainty is visible to us. We remember the sentence we rewrote five times and the mistake we had to correct. We do not necessarily see equivalent moments in someone else’s work.

Speed comparisons made from those two perspectives are inherently uneven. We are timing our entire process while seeing only the result of theirs.

Deadlines Change What “Good Enough” Means

Not every task allows unlimited refinement. Sometimes an answer that is very good today is more useful than a theoretically perfect answer delivered after it is needed. A deadline creates a point at which additional accuracy, detail, or polish must be weighed against the value of actually completing the work.

This does not mean deadlines justify careless work. It means quality exists within constraints. A competent person may intentionally stop investigating when the remaining uncertainty is small relative to the time required to reduce it. In another situation, they may request more time because the unresolved issue is too important to ignore.

Knowing when the answer is sufficiently reliable to act on is itself a judgment. Neither endless checking nor automatic speed solves that problem for us.

Some People Think Better While Speaking; Others Need a Different Sequence

Conversation can make speed differences especially visible because there is little opportunity to hide processing time. Some people develop an idea while speaking. They begin with a rough answer and refine it aloud as the conversation continues. Others prefer to organize the answer internally before saying much. The first style can sound faster even when both people eventually reach equally thoughtful conclusions.

Writing changes the comparison again. A person who hesitates in conversation may produce a clear written explanation when given time to organize it. Someone who speaks fluently may find written structure more demanding. Neither format provides a complete measure of general competence because each asks for a somewhat different combination of abilities.

This is particularly important when judging people in settings where quick verbal responses receive disproportionate attention. The ability to answer immediately in a meeting is useful, but it should not automatically be treated as the same thing as having the best analysis of the problem.

Asking for Time Can Be More Precise Than Pretending We Do Not Need It

When an immediate answer is unnecessary, a short delay can sometimes improve both the response and the communication around it. “Let me check and come back to you this afternoon” gives the other person information about what will happen next. “I want to look at the numbers before answering” explains why an immediate conclusion would be premature.

The important part is that the delay has a purpose. Asking for more time without using it does not improve the answer. But when the time allows verification, comparison, clarification, or preparation, it can be part of an efficient process rather than evidence that the person could not cope with the question.

Speed Can Be Practiced Without Making It the Only Goal

There are legitimate reasons to become faster. Repeated routine work can consume time unnecessarily if every step is approached as though it were new. Templates can remove repetitive decisions. Practice can improve fluency. Learning shortcuts in software can reduce mechanical effort. Preparing common information in advance can make future responses easier.

But useful speed usually comes from reducing unnecessary work rather than removing necessary thought. There is a difference between becoming faster because we understand the task better and becoming faster because we stopped checking something important.

When improving efficiency, it can therefore help to ask what exactly has been eliminated. If the removed step added no meaningful value, the improvement is genuine. If the removed step was where important errors were detected, the faster process may simply be transferring time and cost to a later stage.

We Can Judge Performance Over a Longer Window

The quickest person in the first ten minutes is not necessarily the quickest person by the end of the project. A rushed beginning can create corrections, clarification requests, duplicated work, or decisions that need to be reversed. Conversely, excessive preparation can consume time without preventing meaningful problems.

Looking at the complete process gives a better picture. How long did the task take including corrections? How reliable was the result? How much additional work did it create for other people? Was the process repeatable? Did the person know when to ask for help or verify something uncertain?

These measures are less dramatic than watching someone produce an immediate answer, but they often tell us more about practical competence.

We Do Not Need to Apologize for Every Pause

Because rapid responses can carry social status, people sometimes apologize before taking even a reasonable amount of thinking time: “Sorry, I’m slow today,” “This should be obvious,” or “I don’t know why this is taking me so long.” Sometimes the frustration is understandable, especially when a familiar task suddenly becomes difficult. But not every pause needs an explanation.

A pause may mean the question is unfamiliar. It may mean several answers are plausible. It may mean we are checking whether the first answer is actually correct. It may simply mean that language has not yet caught up with the idea. The existence of processing time is not enough to determine which explanation applies.

Instead of immediately interpreting delay as failure, we can first ask whether the extra time is doing useful work.

We Can Observe Where Speed Helps and Where It Hurts

Rather than trying to become generally faster or generally more deliberate, it can be more useful to notice which tasks benefit from each approach. Perhaps routine emails become unnecessarily expensive when we rewrite them repeatedly. Perhaps financial decisions deserve more checking than we usually give them. Perhaps we answer questions too quickly in meetings but overthink minor choices afterward.

These patterns are more actionable than a general rule about pace because they identify where adjustment would actually matter. Readers who want a simple space for observing patterns in their own decisions can also use the Mibosma Free Tools without turning the exercise into a complicated tracking system.

The Goal Is Not to Become Slower — It Is to Use Time Where It Adds Value

The original idea that “slowness is a form of trust” contains something appealing, but slowness itself is not what makes a decision trustworthy. A slow answer can be poorly reasoned. A fast answer can be excellent. An expert may recognize something instantly, while the same expert may spend hours investigating an unfamiliar exception.

A more useful principle is that the amount of time we give a task should have some relationship to what the task requires. Familiarity, consequences, uncertainty, reversibility, available information, and the cost of mistakes can all influence that judgment. Sometimes the appropriate response is immediate action. Sometimes it is a deliberate pause. Sometimes the best answer is that we need more information before answering at all.

Speed becomes misleading when we treat it as evidence before examining what produced it. Someone may be fast because they are experienced, prepared, familiar with the problem, overlooking complexity, guessing confidently, or working under different conditions from ours. Someone may be slower because they are inexperienced, confused, excessively cautious, carefully verifying an important detail, or solving a genuinely harder problem.

The clock cannot distinguish among those possibilities for us. Competence becomes clearer when we look beyond how quickly an answer appeared and ask what the person noticed, what they ignored, what the situation required, and how well the result held up afterward. Sometimes good thinking is fast. Sometimes it needs time. The skill lies less in choosing one pace than in recognizing which pace the moment deserves.