HAOP.ai Research   ← HAOP.ai
HAOP workflow pilots · Field feedback

Piloting an AI product? Examine the work system before you scale it.

A product pilot can show whether the technology performs. A HAOP workflow pilot examines what the product changes in one bounded workflow across its human, AI, and organizational performers: which functions move, where outputs become consequential, whether verification and correction remain possible under actual operating conditions, and whether accountability follows control.

The question is not whether an AI product can perform a task. It is whether that function should leave its current performer, what else moves with it, and whether the resulting work system can still detect and correct deviation before consequence. A legitimate finding may be to redesign the work, constrain the proposed use, delay deployment, retain the current arrangement, or not deploy.

Put forward a workflow

Not ready to talk? Run the free True Function Diagnostic on one workflow first. It stays in your browser.

You bring

One bounded workflow, a sponsor who permits the review, and people with current knowledge of how the work is actually done.

The pilot examines

Function allocation, consequential transitions, verification conditions, grounding, and correction.

You leave with

A confidential map of the work as actually performed, findings on where control is provided and where it is assumed, and the requirements any allocation or product must meet before it enters the workflow.

Before you pilot the product, examine the work.

You do not need to have selected an AI product. A pilot can begin with a current workflow, a proposed use case, a candidate product, or an existing deployment. The method starts by establishing what the work requires; technology is evaluated against that requirement, not used to define it.

Pre-product

No product selected. The pilot tests whether and how functions should be allocated to AI, and what requirements any product would have to meet.

Candidate product

One or more products under consideration. The pilot tests whether a product's actual functions, evidence, constraints, and operating bounds fit the work-system requirements.

Deployment design

A product selected but not fully introduced. The pilot tests whether the proposed allocation, integration, gates, authority, staffing, and controls are viable.

In operation

AI already part of the workflow. The pilot examines how work actually travels now, where control holds or fails, and what must be redesigned or withdrawn.

One bounded workflow No product selection required Duration scoped to the workflow Engagement records confidential by default Either party can stop
Research status

HAOP Revision 6.0.1 and the applied method are deposited and publicly available. The framework remains under development and has not yet been empirically validated. Pilots are part of that development: they bring the method into contact with work-as-done and produce evidence for what should be retained, revised, or rejected.

Scope is named accurately in every engagement. A pre-product pilot exercises the method's early design and allocation stages; the later stages of selection, control engineering, and confirmation require a product or a follow-on phase.

Read the framework

Research collaboration and the standing challenge: see the research page.

What happens next

Your message comes straight to me. I reply to set up a scoping conversation: the boundary of the workflow, who holds current work-as-done knowledge, which stages of the method the engagement can exercise, and terms. Scope is agreed in writing before any work begins. Sending a workflow starts a conversation, not a commitment.

Bring a workflow. Bring evidence. Bring disagreement.

or email me directly

Submissions are processed by Web3Forms and delivered to my inbox. The information is used only to reply and, with your opt-in, for occasional updates. It is not sold, and not shared beyond that processing. Do not include confidential or safety-sensitive operational detail here; name the workflow at a high level. Specifics wait until scope and terms are agreed.