“Nobody Would Do That” Is a Dangerous Sentence in Technology

There is a sentence that I have learnt to be quite suspicious of in technology: “Nobody would do that.”

Nobody would want to click that button repeatedly. Nobody would enter information in that way. Nobody would want to use the product for something that it hasn’t been designed for. Nobody would want to ignore the instructions. Nobody would take that particular sequence of actions.  

There is a sentence that I have learnt to be quite suspicious of in technology: “Nobody would do that.”

And still, someone inevitably does.

What starts by seeming to be an impossible user behaviour might become a broken workflow, a security vulnerability, a frustrated customer or, in the worst scenarios, a business problem with repercussions way beyond the product itself.  

My experience in quality assurance has taught me something which has stayed with me far beyond testing: the most valuable question is usually not “Does this work?” but “what happens if it doesn’t work the way I expected it to?”

That transformation in thinking is extremely valuable for founders and leaders.

Technology is built around assumptions

The discovery of every product begins with mere assumptions. We assume what users will want. We assume the way they will navigate a platform. We assume what features would be the most useful for them. We assume systems will behave predictably when certain conditions are met.  starts with assumptions.

Assumptions are however, not inherently bad. Businesses cannot function without making decisions on the basis of their available knowledge and what they expect. The dangerous part starts when an assumption becomes a fact simply because nobody risked challenging it.

This is where the QA mindset becomes quite crucial. A good tester is trained to look beyond just the happy path- the neat sequence where everything happens exactly the way it has been designed. The real world rarely behaves this way.

Users misunderstand things. They experiment. They make mistakes. They find shortcuts. They blend actions which were never considered during the product planning. They make use of products in ways that the original team never imagined to.

And that is not necessarily a failure of the user.

It serves as a reminder that technology exists in the hands of humans and not in controlled test environments.

The “What If?” questions changes the question,

One of the most powerful questions in technology is quite simple:

What if?

What if the customer does the opposite of what we expect?

What if ten thousand users perform this action simultaneously?

What if the internet connection disappears halfway through the transaction?

What if someone misunderstands this instruction?

What if the system receives information in a format we never anticipated?

What if the customer uses the feature for an entirely different purpose?

These questions do not exist to make teams paranoid but to make them prepared.  

Over time, this way of thinking was not just limited to software testing but has become a leadership skill.

A founder making a business decision is also testing a hypothesis. A product team launching a feature is testing an assumption. A company entering a new market is testing if its understanding of customers is correct.  

The strongest organisations are not just those making the least mistakes. They are the ones that create enough space for discovering their assumptions before reality does it for them.  

Rare does not necessarily mean irrelevant

There is also an important distinguishing factor between unlikely and unimportant.

Not every hypothetical scenario deserves equal time, resources or engineering effort. Businesses need to prioritise. The goal is not to build a product that anticipates every imaginable human action.

The goal is for identifying the unlikely scenarios that could have disproportionately large consequences.

A scenario which happens once in a mill that happens once in a million transactions may sound insignificant — until that one transaction involves a major customer, a critical payment, sensitive information or a system failure that affects thousands of people downstream.

This is why risk-based thinking matters.

Instead of asking, “How likely is this to happen?”, leaders should also ask, “What happens if it does?”

That second question can completely change a decision.

Good leaders make uncomfortable questions safe

There is another lesson here that I believe is particularly important for growing companies.

People will only challenge assumptions if they feel safe doing so.

If a team member says, “I don’t think this will work,” and the immediate response is, “We’ve already decided this,” the organisation has just taught that person to stay quiet next time.

Over time, this becomes expensive.

A sustainable technology company needs people who are willing to ask uncomfortable questions before customers, competitors or circumstances force those questions upon the business.

That means creating a culture where saying “I disagree”, “What if we’re wrong?”, or even “Are we sure?” is treated as contribution rather than resistance.

For founders, this can be difficult. We are often emotionally invested in the vision we have created. But leadership is not about being right more often. It is about creating systems that help the organisation find the truth faster.

Building for reality, not perfection

As technology becomes increasingly intelligent and interconnected, the temptation is to believe that better tools will eliminate uncertainty.

I think the opposite is true.

The more complex our systems become, the more important it is to question what we think we know.

AI can automate tests. Analytics can identify patterns. Automation can execute thousands of scenarios. Intelligent systems can help us identify risks faster.

But none of these replace curiosity.

Someone still has to ask the strange question.

Someone still has to wonder why a user might behave differently.

Someone still has to look at a perfectly functioning system and ask, “What happens if?”

That mindset has shaped how I think not only about quality, but about building a company.

When we started Qniverse, the idea of quality was never meant to be limited to finding defects at the end of a process. For me, quality is a way of thinking — one that encourages us to question, anticipate, learn and improve continuously.

And perhaps that is the bigger lesson QA can teach every technology leader:

Do not build only for the user you expect. Build for the human you have not thought of yet.

Because the moment someone says, “Nobody would do that,” there is usually a very good reason to find out what happens if they do.