@vista8: In 2018, JPMorgan Chase CEO Jamie Dimon mentioned during an internal meeting that the tool he uses to evaluate complex business scenarios is actually a theoretical model derived from air combat. That model is the OODA loop. OODA loop, short for Observe-Orient-Decide-Act (Observe-...)
Summary
Introduces the OODA loop (Observe-Orient-Decide-Act), a theoretical model originating from air combat, and how JPMorgan Chase CEO Jamie Dimon applied it to assess complex business scenarios, extending to the importance of rapid iteration in AI organization competition.
View Cached Full Text
Cached at: 06/30/26, 03:45 PM
In 2018, JPMorgan Chase CEO Jamie Dimon mentioned at an internal meeting that the tool he uses to evaluate complex business scenarios is actually a theoretical model originating from aerial combat.
That model is the OODA loop.
The OODA loop, short for Observe-Orient-Decide-Act, is a decision-making cycle.
Proposed by U.S. Air Force Colonel John Boyd in the early 1970s, it was originally used to explain how fighter pilots make quick, accurate decisions in aerial combat.
In a confrontation, speed isn’t everything, but the difference in cycle speed can determine who wins or loses.
It feels like competition among future large models or AI organizations will be similar — whoever iterates on their self-improvement cycle faster will win.
Similar Articles
@GoSailGlobal: Practical data on multi-agent AI collaboration: Use Opus 4.8 for planning, Deepseek/Gemma for execution — 10x cost reduction, 2x speed improvement. The secret is not using the most expensive model, but having cheap models do the heavy lifting and expensive models only make decisions. This is the same as company management: the CEO shouldn't write code, and interns shouldn't set strategy. A…
A practical sharing on multi-agent AI collaboration, proposing a hierarchical strategy using Opus 4.8 for planning and Deepseek/Gemma for execution, achieving a 10x cost reduction and 2x speed improvement, with open-source implementation.
@snowboat84: https://x.com/snowboat84/status/2072106695040565615
This article provides a detailed overview of the origins and development of MCP (Model Context Protocol), explaining how it bridges the gap between AI models and real-world tools. It also reviews the protocol's rapid adoption across the entire industry—including by competitors—within just twelve months.
@king1818888: https://x.com/king1818888/status/2073999140770775117
This article introduces the concept of Loop Engineering, which involves building repeatable AI workflows by defining goals, execution rules, and verification standards. Using a U.S. stock investor as an example, it demonstrates how to upgrade AI from a chat tool to a continuously collaborative research assistant.
@miles_mazy: https://x.com/miles_mazy/status/2087516591244361755
Drawing on the FDE roadshow experience, the article explores that what enterprises truly lack in AI implementation is not the model itself, but Forward Deployed Engineers (FDEs) who can connect models, business, data, and organizational responsibilities. It elaborates on their responsibilities, organizational mechanisms, technical and sales attributes, and the role of scientific evidence methods in delivery, proposing the view that one FDE leading a group of Agents can complete AI transformation delivery.
@wlzh: Microsoft + UPenn Open-Source Multiplex Thinking: Let LLMs 'Clone' at Forks Then Merge. In a nutshell: When reasoning reaches a critical decision point, the model 'clones' into K pathfinders, each taking a different path. After one step, they merge back into a composite token and continue. With K=3, one token carries the information of three…
Microsoft and the University of Pennsylvania open-source Multiplex Thinking, which allows LLMs to split into K parallel paths during inference, explore, then merge, improving efficiency. On a 7B model, it achieves over 50% accuracy on AMC2023 (first 7B model to do so) and over 55% on AIME2025.