Interview With Dr. John Jiang: Making SI Practical, Affordable and Measurable for Small Businesses
Dr. Zhiyu Jiang — known to many as John Jiang — has a résumé with an unusual arc. He earned his Ph.D. in experimental particle physics from Stony Brook University, worked at the U.S. Department of Energy's Brookhaven National Laboratory, took part in the ATLAS experiment at CERN, and later held a postdoctoral appointment at Stanford University. Today he is the founder and chief technology officer of VESS (Virtual Enterprise System Solutions), an enterprise super intelligence consultancy, and serves as chief scientist of the North American Venture Capital Association (NAVCA). According to his author biography, he brings 25 years of experience leading enterprise SI transformation, for Global 500 companies across industries and for U.S. federal agencies.
He recently prepared a guest interview playbook for the technology podcast Digitalk Arkitechs, on the theme "From Digital Transformation to Intelligent Enterprises" — in essence, a practical question: how to make SI practical, affordable and measurable for small businesses. GSM interviewed him in writing on the same set of topics. In his view, SI is not simply another technology revolution; it represents a shift from digitizing business processes to building intelligent, adaptive and increasingly autonomous enterprises. Small businesses, he argues, do not need to start big — they can start small, measure value, and scale intelligently.
He carries the methods of the physics laboratory into the enterprise, unchanged. In experimental physics, researchers deal with complex systems, massive amounts of data, uncertainty, and the challenge of finding meaningful signals in noise — exactly what businesses encounter today. His working order is the same: do not start with technology; start with a hypothesis, establish a measurement framework, and validate conclusions through evidence. He adds systems thinking: understanding an individual component is not enough, because optimizing one department can create bottlenecks elsewhere, so he treats business, data, technology and organizational architecture together. As he puts it: "Successful AI transformation requires scientific discipline, not technological enthusiasm alone."
For small businesses, he distinguishes three levels of transformation. Digitization converts paper and manual records into digital information. Digital transformation redesigns workflows so information moves efficiently across people and systems. Smart transformation uses analytics and SI to predict, decide, optimize, and sometimes act. His example is a small distributor: inventory in spreadsheets is digitization; connecting sales, inventory, purchasing and accounting is digital transformation; forecasting demand and recommending purchases is intelligent transformation; later still, an agent might prepare replenishment orders subject to human approval. The value, he says, is not the SI itself but fewer stockouts, lower inventory costs, faster fulfillment and happier customers — measure operational improvement, not the number of tools installed. In his words: "Digital transformation connects information and processes. Intelligent transformation connects information, decisions, and actions."
He groups today's SI into four capabilities: understanding, creating, acting, and interacting with the physical world. Traditional analytics and predictive SI help a business understand what happened, why, and what may happen next — forecasting, segmentation and predictive maintenance. Generative SI creates and synthesizes: proposals, document summaries, code and natural-language answers. Agentic SI plans and takes action through software tools and multistep workflows within defined permissions. Physical SI combines perception, decisions and control in robots and industrial equipment. Which matters most depends on the problem, not on which category is getting the most attention: forecasting calls for predictive analytics, document-heavy work may benefit from generative SI, multisystem workflows may benefit from agents, and manufacturing and logistics may benefit from physical SI — and the categories can overlap.
Before buying any tool, he advises owners to understand three things: the process, the data and the decision. Map who starts the workflow, what information it needs, which systems it touches, and where delays and exceptions occur. Identify where data comes from, who owns it, and whether it is accurate, accessible and secure. Then separate the decisions that follow clear rules from those that require judgment. His example is invoice processing: before automating it, understand how invoices arrive, how they are matched to purchase orders, how discrepancies are resolved and who authorizes payment — otherwise a business may simply automate an inefficient process. He emphasizes process intelligence before super intelligence, noting that sometimes the biggest win is eliminating unnecessary work before automating what is left.
Choosing the first SI use case, he weighs five factors together: business impact, frequency, technical feasibility, data readiness and risk. The ideal first use case has meaningful value, occurs often, uses accessible data and can be tested safely. An internal document assistant is his standard example: employees find information faster, and the system can be evaluated against known answers without being allowed to modify records. Letting an agent independently authorize payments would be a far riskier first project. His rule: do not start with the most complex problem; start with something valuable enough to matter and simple enough to validate, optimizing the first project for learning and measurable value rather than maximum sophistication. Or, in his signature line: "Don't start with what AI can do. Start with what your business needs to achieve."
On return on investment, he looks well beyond hours saved. Many SI pilots demonstrate technical capability without proving business value; hours saved are useful, but he also tracks cycle time, error rates, throughput, customer satisfaction and operating cost. He then offers a numerical illustration — and is explicit that it is a hypothetical scenario, not the verified outcome of any real client. Suppose a company receives 1,000 customer inquiries a month, each requiring ten minutes to review and route — about 167 hours. An SI-assisted workflow reduces handling to four minutes, saving about 100 hours. At an illustrative fully loaded rate of $35 per hour, that is $3,500 in monthly labor capacity — before software, integration and oversight costs. Capacity, he cautions, is not automatically cash savings: if staff are redeployed, the gain is productivity rather than reduced payroll, and classification accuracy, rework, escalation and response time must be tracked as well. His formula: ROI equals realized benefits minus total costs, divided by total costs, multiplied by 100 percent — with total costs including implementation, subscriptions, training, monitoring and maintenance. As he puts it: "An impressive AI demonstration is not the same as a successful AI investment."
When SI moves from recommendations to actions, governance becomes critical. His checklist: least-privilege access, human approval for high-impact decisions, complete audit trails, operational limits, exception handling and emergency stop mechanisms. Before deployment, a business should know which actions can be rolled back, which require compensation, and which cannot be undone; external documents and messages should be treated as untrusted inputs, because they can contain malicious instructions. He favors progressive autonomy: start with recommendations, introduce supervised execution, and expand permissions only after reliability is demonstrated — autonomy must be proportional to risk. Nor does he see classic robotic process automation and agentic SI as competitors. RPA remains valuable for repetitive, predictable tasks governed by stable rules, such as copying information, generating reports or standardized data entry; agents become useful when tasks require interpretation, contextual reasoning or adapting to changing situations. Often the hybrid works best: SI handles interpretation and coordination, while deterministic software or RPA executes precise actions.
What should smaller companies borrow from large enterprises? Discipline, he says — without copying complexity. Three practices are universal: linking technology to measurable objectives, designing end-to-end processes, and establishing appropriate data governance, security and accountability. But SMBs should avoid oversized committees, excessive documentation and multiyear transformation programs launched before value is proven. Their advantage is agility: decisions are faster, experiments are easier, and operational teams can work closely with implementers. In his words: "Small businesses don't need smaller ambitions. They need smarter starting points."
Given 30 days and a modest budget, his plan runs week by week. Week one: identify three recurring problems, choose one based on value and risk, and measure current time, cost, quality and volume. Week two: choose a product or lightweight integration, define success criteria, approve the data, and establish human review. Week three: run representative tasks with supervision and document errors and exceptions. Week four: evaluate net benefits, quality, adoption and risks, then decide to scale, refine or stop. A knowledge assistant, a document-processing workflow or a customer inquiry assistant may be a good pilot; depending on integration and data needs, a few hundred to a few thousand dollars is an illustrative budget range, not a universal estimate. Success should be defined before implementation — a 30 percent cycle-time reduction with maintained quality and positive economics might justify further investment, while constant correction means redesign or stop. As he puts it: "The future of business is not simply digital. It is intelligent." The journey, he adds, begins with one well-defined problem, one measurable improvement, and one successful step at a time.
Rapid Fire
Asked which workflow an SMB should map before automating, he answered: "Order-to-cash, from inquiry through fulfillment, invoicing, and collection."
Asked whether process clarity or data quality fails first, he said: "Usually process clarity. Without understanding the workflow, you may not know what good data means."
Asked for one metric for an early pilot, he chose: "Quality-adjusted cost per completed transaction."
Asked what should never be automated without human review, he answered: "High-impact, hard-to-reverse decisions involving money, legal duties, safety, or sensitive data."
Asked for the first question to put to an SI vendor, he said: "What measurable outcome will you deliver, and how can we validate it on our data?"
Asked for one signal that a pilot is ready to scale, he named: "Consistent measurable value, real adoption, and manageable risk."
His own career, as he describes it, has evolved from understanding complex physical systems to architecting intelligent business systems, with the underlying principle unchanged: understand the system, measure what matters, and use technology to produce meaningful, verifiable results. For the vast number of small businesses now facing SI, that may be the most useful starting point of all — not chasing the most fashionable tool, but beginning with one real problem.
Related:
Published by GSM · USA (original Chinese edition)
Photo: 蒋志予博士（供图）
