Influence was never the finish line.
Outcomes were.

I have spent much of my career helping organizations improve security culture, reduce human risk, communicate more effectively, and turn strategy into action. Over time, one question became harder to ignore: did any of it actually work?

Organizations can show how many people completed training, how many policies were published, how many risks were reviewed, and how many tickets were closed. They can produce more dashboards than any executive has time to read. What they often cannot show is whether the intervention changed the outcome. That is the problem I want to solve next.

Explore IO™

A finish line on a quiet track at dawn, symbolizing outcomes as the real goal.

We measure activity because activity is easy to count.

The problem was never a lack of effort. I have worked with talented security leaders, technical teams, communicators, educators, and executives, and most organizations are doing a tremendous amount of work. The challenge is that the systems recording the signals are separated from the systems assigning the work, and both are separated from the reports describing the result.

ENTERPRISE PLATFORMSEXECUTIVE OUTPUTSIEMIdentityThreat IntelHRMLMSCloudMicrosoft 365SlackJiraServiceNowGovernanceRiskCommunication01Executive Intelligence02Prioritized Actions03Execution04Measurable OutcomesIO
The IO™ Fabric — stack → IO → executive outcomes.

Training was completed. A campaign was delivered. A policy was approved. A finding was closed. A new control was implemented. Those records matter, but none independently establish that the organization became safer, more resilient, or better prepared.

The logical next step is to connect the signal that identified the problem to the decision that was made, the work that followed, and the evidence showing what changed afterward.

An executive intelligence platform.

IO™ is powered by the InfluenceOS™ methodology. It connects signals from the systems an organization already uses, correlates them across domains, interprets them within the organization's actual environment, recommends a defined course of action, and assigns the work to an accountable owner.

Most importantly, it returns to the original measure after the work is completed. The result is recorded whether the intervention improved the measure, produced no meaningful change, made the condition worse, or could not be verified with the available evidence.

The objective is not to manufacture a success story. It is to create a trustworthy record of what was observed, what was decided, what was done, and what happened next.

Speed without verification creates a different kind of risk.

AI and automation can accelerate analysis, compliance work, communication, decision support, and execution. They can also accelerate weak assumptions and make unsupported conclusions appear more authoritative.

The future will not belong to the organizations with the most dashboards, the largest technology stacks, or the greatest volume of activity. It will belong to organizations that can connect evidence to decisions, decisions to accountable action, and action to measurable outcomes.

IO™ is not intended to replace NIST, ISO, C2M2, risk-management methods, control frameworks, or professional judgment. Those approaches help organizations understand what should be governed, protected, assessed, and improved. IO addresses a different question — and where it takes a different position from conventional practice, that difference should be visible and defensible. The platform preserves evidence, uncertainty, limitations, and failed outcomes rather than hiding them behind a confident score.

A closed loop, not another linear workflow.

010203040506Closed loopverify · revalidate

Connect

Bring together signals from the systems already operating across the organization.

Correlate

Identify relationships across sources using attributable evidence rather than unsupported inference.

Interpret

Read the condition in the context of the organization, its environment, and its current operating position.

Prescribe

Match the condition to a defined playbook and explain why the recommendation was raised.

Execute

Assign accountable ownership and capture the baseline before the intervention begins.

Verify

Remeasure the original condition and report the result, including when the intervention did not work.

Eight security and operational domains.

  • Human Risk
  • Threat Detection
  • AI Governance
  • Policy & Governance
  • Resiliency
  • Assurance & Compliance
  • Third-Party Risk
  • Physical Security

Each domain has its own signals, measures, playbooks, and evidence boundaries. Together they create a more complete operating picture without forcing fundamentally different conditions into one unexplained number. Security is where the model begins because it is an environment where decisions matter, evidence is fragmented, and unsupported confidence has consequences. It is not where the idea ends.

The broader opportunity is to measure the relationship between influence, execution, and outcomes across the enterprise: leadership, culture, AI adoption, communication, workforce behavior, governance, operational resilience, and business transformation. In each case the challenge is similar — organizations invest in interventions without defining the measure beforehand or returning afterward to determine whether the intended outcome occurred. InfluenceOS™ provides the methodology. IO™ makes it operational.

See what I am building.

IO™ is not a departure from the work I have been doing. It is the next logical step, bringing together security leadership, human behavior, culture, communication, governance, executive decision-making, and measurable accountability.

I am building it because organizations deserve a more honest answer than “the work was completed.” They should be able to ask whether it worked and receive an answer they can defend, including when that answer is no. IO™ is currently being developed with a small number of design partners who want to help shape how the platform works in real organizations.

Explore IO™