AI 时代,系统思维至关重要

IEEE Spectrum 11 月刊来了!
在 AI 时代,系统思维至关重要
面向技术业内人士
IEEE Spectrum 是 IEEE 的旗舰出版物——IEEE 是全球最大的致力于工程与应用科学的专业组织。我们的文章、视频和信息图向读者介绍技术、工程和科学领域的最新进展。
创建账户即可享受更多免费内容和权益
将文章保存以便稍后阅读需要 IEEE Spectrum 账户
The Institute 的内容仅面向会员开放
下载完整 PDF 各期为 IEEE 会员专属
下载本电子书为 IEEE 会员专属
访问 Spectrum 数字版为 IEEE 会员专属
关注话题是 IEEE 会员专属功能
加入全球最大的致力于工程与应用科学的专业组织,即可访问 Spectrum 的全部文章、档案、PDF 下载及其他权益。进一步了解 IEEE →
加入全球最大的致力于工程与应用科学的专业组织,即可获得本电子书,以及 IEEE Spectrum 的全部文章、档案、PDF 下载及其他权益。进一步了解 IEEE →
访问数千篇文章——完全免费
创建账户,即可获取专属内容与功能:收藏文章、下载合集、发表评论——全部免费!如需完整访问权限与权益,请订阅 Spectrum。
在 AI 时代,系统思维至关重要
机器可以将枯燥繁琐的工作自动化,但关键决策仍由工程师做出
Sufian Aldogom 是 IEEE 会员、MIT 研究附属成员,也是位于加州 Sunnyvale 的 Google 高级负责人。
Moor Studio/Getty Images
现代工程项目越来越多地将人类判断与机器能力结合起来。工程师可以界定一个问题,然后让人工智能工具检索相关研究和技术标准、生成设计方案、在仿真中测试这些方案并比较结果。之后,工程师可以把结果交给专家——他们了解 AI 无法自行判断的部分,例如某个设计能否安全地建造、在特定场景中是否合理,或者可能对用户产生何种影响。至于是否推进以及如何推进,最终决定仍由人负责。
AI 可以帮助工程师完成项目早期的步骤,而这些步骤过去需要多名具备不同技术技能的人共同完成。因此,工程师的角色正在从亲自执行每一个技术步骤,扩展为决定人、机器与专家知识应如何在项目中协同。
问题本身,而非头衔
工程学一直按学科划分,而且理由充分。电气、机械、土木、软件及其他工程领域都需要多年积累才能形成的深厚知识。AI 并不能取代这种需求,它只是改变了工程师探索自身专业之外那部分问题的难易程度。
以一位从事医疗器械开发的软件工程师为例。AI 可以帮助这位工程师查阅相关生物医学研究、理解陌生术语、分析数据,并构建早期模型。
这并不会让工程师变成医生或生物医学专家。它的作用是让工程师在与专家合作之前能提出更好的问题。
能源、交通、制造以及许多其他领域同样如此。一个问题可能起初只是软件问题,随后很快牵扯到硬件、安全措施、经济性、人类行为和法规。
工程师不需要精通每一个领域;他们需要识别出问题需要哪些专业知识,并把合适的人和工具汇聚到一起。
系统思维的重要性
因此,系统思维变得尤为重要。它要求审视整个问题:理解各部分如何相互影响,识别约束条件和失效点,并做出权衡取舍。
AI 为这一过程增添了新的要素。工程师不仅要决定技术各部分如何衔接,还要决定哪些工作交给 AI、哪些必须由人来核查、何时应由专家做出决策,以及何时需要重新定义问题。
工程师的价值不在于通晓一切,而在于懂得如何界定问题、如何提出正确的问题、如何检验答案,以及何时应由另一位专家来主导项目。
这一点至关重要,因为工程中的技术挑战很少是一成不变的。随着新认识的涌现,目标可能发生变化,未被察觉的限制可能浮现,最初的假设也可能被证明有缺陷。高效的工程师不会死守最初的规格,而是随着对系统的理解不断深入而调整并细化范围。
因此,工程学不止于掌握技术概念;它还是一套可灵活调整、结构化的方法,用于应对不断演变的挑战。
新的证据可能改变目标、揭示隐藏的约束条件,或表明最初的假设是错误的。优秀的工程师不会仅仅按照最初的问题陈述行动,而是随着对系统的理解不断加深来更新它。
从这个意义上说,工程学不仅是一套技术知识体系,也是一种严谨的项目思维方式。
人的判断很重要
AI 即便在假设薄弱时也能给出看似有说服力的答案。它能生成在一项测试中可用、在另一项测试中却失败的代码。它能总结研究,却不了解哪项证据最有分量,或者为一个错误的目标优化设计。这些局限使人的专业能力变得更加重要,而非更不重要。
在速度、规模、搜索、模式识别和数据生成重要的地方,机器很有用。在背景、价值观、责任和判断重要的地方,人不可或缺。挑战在于确定各自应处于什么位置。
例如,一个 AI 系统可能为某种医疗传感器生成若干设计方案,并预测每个方案的表现。工程师可以检验这些预测,并剔除违反技术要求的设计。临床医生可以判断该传感器能否在实际中投入使用。患者和从业者可能揭示出工程师和开发者都未曾考虑的问题。最终的解决方案来自各方视角的结合。
工程师仍然是构建者和专家,但正日益成为知识的协调者。
工程师的价值不在于无所不知,而在于懂得如何界定问题、如何提出正确的问题、如何检验答案,以及何时应由另一位专家来主导项目。
这种更广义的工程实践为 IEEE 创造了重要的角色。IEEE 旗下的各个学会已经汇集了多种技术、工程教育、技术标准等领域的专业知识。这使 IEEE 处于有利位置,能够帮助工程师跨专业协作,同时又不削弱专业化的价值。
IEEE 可以围绕需要多个领域专业知识的问题,建立更多社群。例如可信的临床 AI、具备韧性的基础设施、能源可靠性、科学发现,以及安全的自主系统。工程师可以从自己的本专业出发,然后根据项目需要,与来自 IEEE 其他社群的专家合作。
IEEE 还可以帮助制定人机协作的实用标准。工程师将需要明确的指引:AI 生成的工作何时必须核查,不确定性应如何记录,何时必须由专家做出决策,以及当一个系统同时使用人类判断与机器输出时,责任由谁承担。
这些问题正成为日常工程工作的一部分。它们不应被留给每家公司或每位项目经理各自独立作答。专业组织可以提供共同的预期,让工程师在更换工作、跨越行业和技术领域时依然有所依循。
对工程师更宽泛的定义
AI 并不会让工程学科变得不那么重要;它让各学科之间的联系更易于利用。深厚的专业能力为工程师打下判断什么才可靠的基础。系统思维帮助他们理解问题的各个部分如何组合在一起。AI 可以拓展工程师跨领域探索、验证和沟通的能力。人的判断则为工作指明方向并赋予责任。
工程师的定义,不只看职位头衔或一套固定的任务。工程师是经过训练的人:能够理解复杂系统,界定并重新界定问题,汇集解决问题所需的知识与工具,检验解决方案是否有效,并对结果负责。
这就是成为“无界”工程师的含义。
专业之间的边界变得更易于跨越,机器可能承担更多技术性工作,但工程的核心仍然属于人:决定哪个问题值得解决,什么样的证据足够充分,各个部分如何组合在一起,以及在答案不确定时该怎么做。
译文由英文原文机器翻译,术语按行业惯例统一,可在文末展开原文核对。
查看英文原文(Systems Thinking Is Vital in the Age of AI)
Systems Thinking Is Vital in the Age of AI - IEEE Spectrum
The November issue of IEEE Spectrum is here!
Systems Thinking Is Vital in the Age of AI
FOR THE TECHNOLOGY INSIDER
IEEE Spectrum is the flagship publication of the IEEE — the world’s largest professional organization devoted to engineering and applied sciences. Our articles, videos, and infographics inform our readers about developments in technology, engineering, and science.
Enjoy more free content and benefits by creating an account
Saving articles to read later requires an IEEE Spectrum account
The Institute content is only available for members
Downloading full PDF issues is exclusive for IEEE Members
Downloading this e-book is exclusive for IEEE Members
Access to Spectrum 's Digital Edition is exclusive for IEEE Members
Following topics is a feature exclusive for IEEE Members
Join the world’s largest professional organization devoted to engineering and applied sciences and get access to all of Spectrum’s articles, archives, PDF downloads, and other benefits. Learn more about IEEE →
Join the world’s largest professional organization devoted to engineering and applied sciences and get access to this e-book plus all of IEEE Spectrum’s articles, archives, PDF downloads, and other benefits. Learn more about IEEE →
Access Thousands of Articles — Completely Free
Create an account and get exclusive content and features: Save articles, download collections, and post comments — all free! For full access and benefits, subscribe to Spectrum .
Systems Thinking Is Vital in the Age of AI
Machines can automate drudgery but engineers make key decisions
Sufian Aldogom is an IEEE member, a research affiliate at MIT, and a senior leader at Google in Sunnyvale, Calif.

Moor Studio/Getty Images
Modern engineering projects increasingly combine human judgment with machine capability. An engineer can define a problem, then ask an artificial intelligence tool to search relevant research and technical standards, generate design options, test them in simulation, and compare the results. The engineer can then bring the results to specialists who understand the parts AI cannot judge on its own, such as whether a design can be built safely, whether it makes sense in a particular setting, or how it might affect its users. The final decision about whether and how to move forward remains a human responsibility.
AI can help engineers do early project steps that once required several people with different technical skills. The engineer’s role is therefore expanding from performing each technical step to deciding how people, machines, and specialists’ knowledge should work together on the project.
The problem, not the title
Engineering has always been divided into disciplines, and for good reasons. Electrical, mechanical, civil, software, and other engineering fields require deep knowledge that takes years to develop. AI does not replace that need. It simply changes how easily engineers can explore the parts of a problem that sit outside their own specialty.
Consider a software engineer working on a medical device. AI can help the engineer review relevant biomedical research, understand unfamiliar terms, analyze data, and build an early model.
That does not make the engineer a physician or biomedical expert. It allows the engineer to ask better questions before working with the experts.
The same is true in energy, transportation, manufacturing, and many other fields. A problem might begin as a software issue and then quickly involve hardware, safety measures, economics, human behavior, and regulations.
Engineers do not need to master every field; they need to recognize which expertise the problem requires and bring the right people and tools together.
The importance of systems thinking
Systems thinking thus becomes especially important. It requires looking at the whole problem: understanding how its parts affect one another, identifying constraints and failure points, and making trade-offs.
AI adds a new element to the process. Engineers must decide not only how the technical parts fit together but also what work to give to AI, what a person must check, when a specialist should make a decision, and when the problem needs to be redefined.
An engineer’s value is not in knowing everything. It is in knowing how to frame the problem, how to ask the right questions, how to test the answers, and when another expert must lead the project.
This aspect is crucial because technical challenges in engineering are seldom static. As new insights emerge, objectives might shift, unseen limitations can surface, and the initial premise might prove flawed. Rather than rigidly following the starting specifications, an effective engineer adapts and refines the scope as a deeper understanding of the system develops.
Thus, engineering extends beyond mastering technical concepts; it is an adaptable, structured approach to navigating evolving challenges.
New evidence can change the goal, reveal a hidden constraint, or show that the original hypothesis was wrong. Effective engineers go beyond merely acting on the initial problem statement. They update it as the system becomes better understood.
In that sense, engineering is not only a body of technical knowledge, it is also a disciplined way of thinking about a project.
Human judgment is important
AI can produce convincing answers even when its assumptions are weak. It can generate code that works in one test but fails in another. It can summarize research without understanding which evidence is strongest, or optimize a design for the wrong goal. Such limits make human expertise more important, not less.
Machines are useful where speed, scale, search, pattern recognition, and data generation matter. People are essential where context, values, responsibility, and judgment matter. The challenge is to decide where each belongs.
An AI system might generate several designs for a medical sensor, for example, and predict how each will perform. An engineer can test the predictions and reject designs that violate technical requirements. A clinician can determine whether the sensor can be realistically used. Patients and practitioners might reveal problems that neither the engineer nor the developer considered. The final solution emerges from combining the perspectives.
The engineer is still a builder and specialist but increasingly also a coordinator of knowledge.
An engineer’s value is not in knowing everything. It is in knowing how to frame the problem, how to ask the right questions, how to test the answers, and when another expert must lead the project.
The broader form of engineering creates an important role for IEEE. Its societies already bring together expertise in various technologies, engineering education, technical standards, and other fields. That makes IEEE well placed to help engineers work across specialties without weakening the value of specialization.
IEEE could create more communities organized around problems that require expertise from several fields. Examples include trustworthy clinical AI, resilient infrastructure, energy reliability, scientific discovery, and safe autonomous systems. An engineer could begin in a home discipline and then work with specialists from other IEEE communities as a project requires.
IEEE also can help set practical standards for human-machine collaboration. Engineers will need clear guidance on when AI-generated work must be checked, how uncertainty should be documented, when a specialist must make a decision, and who is responsible when a system uses both human judgment and machine output.
Those questions are becoming part of everyday engineering. They should not be left to each company or project manager to answer independently. A professional organization can provide common expectations that follow engineers as they move between jobs, industries, and technical fields.
A larger definition of the engineer
AI does not make engineering disciplines less important; it makes the connections between them easier to use. Deep expertise gives engineers the foundation to judge what is sound. Systems thinking helps them understand how different parts of a problem fit together. AI can extend engineers’ ability to explore, test, and communicate across fields. Human judgment gives the work direction and responsibility.
An engineer is not defined only by a job title or a fixed set of tasks. An engineer is someone trained to understand complex systems, define and redefine problems, bring together the knowledge and tools needed to solve them, test whether solutions work, and take responsibility for the outcome.
That is what it means to be an “unbound” engineer.
The boundaries between specialties become easier to cross, and machines might take on more of the technical work, but the core of engineering remains human: deciding what problem is worth solving, what evidence is good enough, how the pieces fit together, and what to do when the answer is uncertain.
Related Articles Around the Web
原文为英文,正文由自动抓取并保留原文。
原文发布于 IEEE Spectrum AI(Systems Thinking Is Vital in the Age of AI),标题、摘要与正文由机器翻译,术语按行业惯例统一,未经人工逐句校订。