• +1 (602) 922-5990
  • This email address is being protected from spambots. You need JavaScript enabled to view it.
  • Mon - Fri 8:00a - 5:00p AZ
  • Executive silhouetted against a sunrise city view beside a glowing holographic network sphere linked to servers and buildings, with the article title Connecting AI Governance and Resilience and icons for AI inventory, critical services, dependencies, oversight, scenario testing, fallbacks, an

    Many organizations now run two important programs side by side without connecting them. One is AI governance: the policies, committees, and risk assessments that decide how artificial intelligence may be developed, bought, and used. The other is operational resilience: the discipline of keeping critical services running through disruption. They are often staffed by different people, report to different executives, and use different vocabularies.

    That separation made sense when AI sat at the edges of the business, in pilots and productivity tools. It makes less sense now that AI models help route customer calls, flag fraud, schedule maintenance, draft communications, and prioritize work queues. When AI becomes part of how a critical service is delivered, its failure becomes a resilience problem, and resilience planning that ignores it has a blind spot.

    This article explains why the two disciplines need each other and how leaders can connect them without building another layer of bureaucracy.

  • Person seen from behind raising a hand toward a glowing holographic brain made of network lines in a dark operations room, with the article title Human Oversight That Works and icons for review points, authority, automation bias, competence, capacity, feedback, and evidence.

    "There will be a human in the loop." It is one of the most common reassurances offered when organizations deploy artificial intelligence, and one of the least examined. A person somewhere in the process is expected to catch errors, prevent harm, and take responsibility. Yet in practice, that person may be reviewing hundreds of AI recommendations an hour, may lack the information to judge them, may have no real authority to overrule them, and may have learned through experience that the AI is usually right.

    In those conditions, human oversight becomes a formality. The human signs off, the AI effectively decides, and accountability becomes harder to locate when something goes wrong.

    Meaningful oversight is achievable, but it has to be designed. This article explains how to define review and intervention points that work: where to place them, what the people in them need, and how to know whether oversight is real.

  • Executives silhouetted around a boardroom table in front of floor-to-ceiling windows overlooking a city at sunrise, with the article title From AI Principles to Accountability and icons for principles, ownership, inventory, risk tiers, approvals, monitoring, and reporting.

    Over the past several years, many organizations have published statements of AI principles. They commit to fairness, transparency, privacy, safety, and human oversight. These statements are a reasonable starting point. They signal intent to employees, customers, and regulators, and they give teams a shared vocabulary.

    But principles do not govern anything on their own. A commitment to fairness does not tell a product team which tests to run before launching a credit model. A commitment to transparency does not say who decides what customers are told when AI is involved in a decision. A commitment to human oversight does not specify who can stop a system that is behaving badly. Between the principle and the practice sits a gap, and that gap is filled either by deliberate accountability or by assumptions.

    This article explains how to turn AI principles into practical accountability that works across the full lifecycle of AI systems, from the first idea to retirement.

  • Analyst seen from behind at a desk with two monitors showing performance charts and dashboards, a magnifying glass on the desk and a sunrise city view through the window, with the article title Evidence Behind Trusted AI and icons for testing, monitoring, documentation, independent review, incidents, traceability, and assurance.

    Organizations want their customers, employees, regulators, and boards to trust the AI systems they use. Trust, however, cannot be requested. It has to be earned, and in a governance context it is earned through evidence: documented, verifiable information showing that an AI system was designed responsibly, tested appropriately, operates as intended, and is overseen effectively.

    Many organizations have pieces of that evidence. A data science team has validation results. A vendor has supplied a technical summary. A risk team has completed an impact assessment. A monitoring dashboard tracks some performance metrics. But the pieces often sit in different places, follow different standards, and stop at the moment of deployment. When someone asks a direct question, such as "How do we know this model is still performing fairly?", assembling an answer takes weeks, if it can be done at all.

    This article sets out how to connect testing, monitoring, and assurance into a continuous chain of evidence that supports trust in AI over its full life.

  • Industry Insights banner: Supply Chain, Recovery, and AI on the Grid, over a sunrise landscape with power infrastructure.

    Energy and water utilities are often asked to show a continuity plan, a cyber program, and a vendor list. The harder question is whether a utility can keep essential service flowing when a supplier, a control-system vendor, or a model used in operations fails. For many organizations those three issues sit under different managers and different regulatory labels, even though they describe the same operating problem.

    The official landscape is split, and it is a mistake to blur the split. Applicable users, owners, and operators of the Bulk Electric System are subject to mandatory NERC Critical Infrastructure Protection reliability standards, which the Federal Energy Regulatory Commission approves and which include supply-chain and recovery obligations. Community drinking-water systems that serve more than 3,300 people are subject to America's Water Infrastructure Act section 2013, which amended section 1433 of the Safe Drinking Water Act and requires a risk and resilience assessment and an emergency response plan, recertified on a five-year cycle. Wastewater systems are encouraged to plan; they are not required to certify those products to EPA. Public power may fall under CIP, AWIA, both, or neither, depending on registration and on whether the organization also operates a community water system.

    This article treats that split as the starting point, then asks how third-party risk and AI used in operations should be governed so that recovery, supply-chain control, and resilience assessments describe the same set of critical dependencies.

  • Industry Insights banner: AI, Contractors, and Continuity of Operations, a resilience briefing for public agencies, with a domed capitol.

    A public agency can hold a continuity of operations plan, a set of information-technology contracts, and a growing list of artificial-intelligence use cases, and still be unprepared for the moment a contractor, a cloud service, or a model used in a public-facing decision is unavailable or untrustworthy. For state, local, tribal, and territorial governments, as well as for federal executive agencies and public pension systems, that is now a single management problem. Continuity, contractor oversight, and AI governance are often housed in different offices. The public experiences them as one service: either the agency can still perform its essential functions, fairly and safely, or it cannot.

    The official federal starting point for agency use of AI has also changed, and that change should be stated accurately. On March 28, 2024, the Office of Management and Budget issued Memorandum M-24-10, Advancing Governance, Innovation, and Risk Management for Agency Use of Artificial Intelligence. On April 3, 2025, OMB issued Memorandum M-25-21, Accelerating Federal Use of AI through Innovation, Governance, and Public Trust, which in its official text "rescinds and replaces" M-24-10. M-24-10 is therefore part of the recent history of federal AI governance. It is not the current OMB memorandum. This article works from M-25-21, from FEMA's Continuity Guidance Circular as whole-community continuity guidance, and from the NIST AI Risk Management Framework as a voluntary method that agencies and their contractors can use together.