Artificial intelligence and autonomous intelligence
AI is moving from tool to infrastructure, and from infrastructure to
delegated action. That last step is the one boards are least prepared for,
because it changes who — and what — decides.
Most institutions already have adoption programs. Fewer have answered the
institutional questions underneath them: which decisions a model may
recommend and which it may execute, who signs when a machine-mediated
recommendation goes wrong, and what the operating model becomes when a
meaningful share of knowledge work is produced by systems rather than
staff. Beneath all of these sits a distinction most organizations have not
yet drawn — between productivity tooling and decision infrastructure, two
categories that look identical in a procurement deck and behave nothing
alike in a crisis.
Datum North works with boards and executive teams on exactly this layer:
decision rights, accountability, governance that enables rather than
stalls, workforce and operating-model redesign, and the data and model
foundations these depend on.
The questions that tend to open this work: When your model provider
ships an update, who inside your organization is told — and would they
recognize a material change in decision behavior if they saw one? How many
of your current approvals are already ratifications?
Where this becomes an engagement. Most often the delegated decision rights and accountability review, or the board-level questions of a discontinuity review. Either way the boundary holds: the firm designs the decision and governance architecture; the client's teams build and run the systems.
Physical AI, robotics, and intelligent machinery
Autonomy is leaving the screen. Robotics, autonomous machinery, drones,
sensor networks, and cyber-physical infrastructure are moving AI into
environments where an error is not a bad paragraph but a bent asset, an
injured worker, or a stopped line.
The strategic difficulty is that the opportunities do not generalize. A
warehouse retrofit, a port, a surgical suite, and a mine can be pitched
from the same vendor deck and carry entirely different risk, capital, and
liability profiles. Much of the firm's work in this area is helping leaders
tell those apart before capital is committed — and designing the oversight,
safety, and operating models required when software begins to act on the
physical world.
The questions that tend to open this work: Where does autonomy enter
your physical operations first — and which of your insurance, liability, and
labor assumptions breaks on that day? What must be true, technically and
institutionally, before you let it?
As an engagement. The physical autonomy strategy — authorization conditions defined venue by venue. Machinery selection, systems integration, and safety certification stay with qualified providers.