SQA

[A hidden SQA indicator] Structured error codes

·3 min read

An SQA indicator that is often overlooked, yet very easy to recognise

When people talk about software quality, most think first of test coverage, bug counts or system stability.

But in practice, I have come to rely on a very concrete and often overlooked way to judge it:

Whether a system has ever had its error codes "seriously designed" often says more about its quality maturity than the features themselves.

By this I do not mean error codes that are just numbers used as an index, but error codes with deliberate structure and meaning.


When error codes become a "quality signal"

I first really understood the value of error code design while reading Microsoft source code.

In those systems, error codes are not arbitrarily defined integers. Using bit-wise AND / OR across 16 or 32 bits, they encode the source, module, type and severity of an error in a structured way.

That was when I realised:

Error codes are part of the system design itself, not an add-on.


A very common pattern in practice is this:

when a system grows large without a clear error code and error handling scheme, the team ends up spending a great deal of effort on "finding the problem" rather than solving it.


What does a system without error codes really cost?

To sum up the impact of lacking structured error codes in one line:

Diagnosing errors takes longer, the diagnosis is more often pointed in the wrong direction, and in the long run the customers you lose because of errors will be far more than you expected.

On the surface, these systems are not entirely without error handling: there are error messages, logs, exception call stacks,

and even some input-guarding logic.

When something goes wrong, the team often has to spend a lot of time working out:

Is this a data problem or a system problem?

Which module threw the error?

Is it a variation of a known issue, or something entirely new?

Because errors were never defined in a structured way, everyone has to piece together the truth from experience, guesswork and endless back-and-forth.

From an SQA point of view, this is a very clear quality signal:

The system never treated "errors" as a first-class design concern.


Error codes really reflect the designer's maturity

The real dividing line is usually not "whether there are error codes", but:

whether the designer already expected that problems will happen.


Mature system designers do not treat errors as exceptions. They treat them as certainties. Once you accept that premise, the role of error codes changes completely.

They are no longer just a debugging tool for engineers. They become a carrier of information across roles, passing key information along the whole product line.

That is exactly why error codes can almost be treated as a hidden quality indicator.

What they reflect is not engineering skill, but whether the team has thought about "how we will deal with problems together once they happen".

better_error_resolver.jpg

Error codes are not just about errors, they are about experience

Error codes are often misunderstood as an after-the-fact firefighting tool, but in reality their effect on user experience is often more direct.

An error message, by nature, is only "for people to read", while an error code is "a semantic signal for the system to use".

When errors are expressed as structured information, the front end and the flow design have more options. They can offer guidance that fits each situation,

rather than just showing a line of error text.


From a product experience point of view, a system that only has error messages usually hands the job of understanding and fixing the problem back to the user.

Think about it: would you rather the system showed you the usual toast saying "Error while saving!"?

Or a guided dialog telling you that you do not have permission to edit and save this document, and what you can do about it?


Users usually leave without saying anything. Paying attention to every detail that might affect the user experience is what makes a product win.


Conclusion

A mature system is not one with fewer errors. It is one where, before errors happen, the team has already worked out how to deal with them.

And error codes are one of the most concrete, and most overlooked, expressions of that maturity.

Need Professional Assistance?

Our team are senior engineers and former executives with 20+ years in commercial product development — from apps serving hundreds of millions of users to B2B SaaS platforms serving tens of thousands of merchants. In recent years the focus has been enterprise AI adoption, from mapping the opportunity through to tuning what is live. Whether that means:

  • Mapping AI opportunities and sequencing them
  • Preparing data flows and integrating existing systems
  • Building forecasting and optimisation models
  • Monitoring and tuning after go-live
  • Test strategy and process review
  • Building and adopting test automation

We can provide professional advice and concrete solutions for teams of different scales and types. If you're facing similar challenges, feel free tocontact our consulting team.