Balancing Tech and Business: Aligning Goals for Sustainable Growth

The author revisits a recent post on stability assurance and uses it as a springboard to ask whether technology or business is more important. While most companies rely on business revenue, neglecting technology leads to lower investment, poorer system quality, bad user experience, and operational failures that ultimately hurt the business.

By reframing the question, the article defines the relationship between technology and business as a feedback loop: technology enables rapid fulfillment of business needs, which drives revenue; revenue then funds continued technical investment, which in turn improves the ability to meet business goals.

Using Alibaba Cloud’s major outage as an example, the author illustrates that cloud service providers sell computing, storage, networking, database, big‑data, and large‑model capabilities as services, not as raw technology products. The business originates from market demand, translates into product requirements, and is delivered through technology.

From this logic, the author derives three shared objectives for both sides:

Clear scope – requirements must be precisely defined to be implementable and deliverable.

Quantifiable metrics – both parties need measurable indicators for change‑response speed and delivery efficiency.

Business value realization – business seeks fast feature delivery to monetize; technology seeks to support that revenue, earn recognition, and achieve a sense of accomplishment.

These common goals ultimately boil down to quality. Business demands that technology reliably supports its objectives without causing downtime, while technology aims to avoid quality issues that could lead to complaints or performance penalties. The author links this to the core purpose of software testing and quality assurance.

The article also lists the typical expectations from product or business teams toward engineering:

Fast implementation – “just do it, I don’t care how.”

Change responsiveness – handling urgent, ad‑hoc requests during development.

Rapid delivery – from request in the morning to production release by night.

Correspondingly, engineering’s goals when facing these demands are:

Assess implementation difficulty for quick features.

Evaluate impact scope and technical efficiency for changes.

Ensure delivery quality and online stability for rapid releases.

An accompanying diagram (shown in the original article) visualizes the mutual relationship between technology and business, reinforcing the three shared objectives.

In summary, aligning technology and business goals requires clear, measurable, and value‑driven criteria, with quality as the underlying foundation that sustains both sides.