SheetM-02

FieldMETHOD

StatusCURRENT

Version03

Nothing gets automated before it has been watched.

The workflow decides the technology. Every engagement runs the same four phases in the same order, because skipping one is how AI programs stall in month three.

The method comes from environments where systems had to run without their author present, and access to high-value assets was accounted for rather than assumed. It has been applied from the help desk to the C-suite.

M-02 · S01One request, end to end Four stages, in order

Intake

Capture the request as it arrives.

Request

Assemble a qualifications package for a healthcare fit-out.

Received

→

Source retrieval

Find and verify the right sources.

Sources

Project record
Personnel register
Approved imagery

Verified

→

Instruction set

Build governed instructions and rules.

Rules

Approved capability language
Cite the project record
No unverified claims

Locked

→

Execution

Run the workflow against real work.

Scope

Comparable projects
Named personnel
Assembled draft

Executed

→

Human review

Someone accountable reads it.

Checklist

Accuracy
Completeness
Client-facing risk

Approved

→

Reusable output

Keep it where the next person finds it.

Kept

Package
Instructions
Change record

Published

M-02 · S02Four phases / what is decided And how each one fails

Observe

Which work is worth touching

The decision is where to spend the engagement: which tasks repeat often enough, and cost enough, to be worth building around.

Fails when

the org chart gets mapped instead of the work
the loudest department sets the priority

Evidence needed

Frequency, duration, and who currently absorbs it.

Structure

What AI may reach, and who owns it

The decision is where the line sits between usable and controlled, and whose name is against each part of the answer.

Fails when

classifications are written that nobody can apply
the rule is so tight people return to personal accounts

Evidence needed

What is already being uploaded, and by whom.

Deploy

Who runs it and who reviews it

The decision is which named person operates each workflow, and which named person is accountable for what leaves the building.

Fails when

the training teaches the tool instead of the job
review is assumed rather than assigned

Evidence needed

The workflow run by its owner, on live work, once.

Measure

What scales and what stops

The decision is which workflows earn more investment and which are retired. The second list is what makes the first one credible.

Fails when

activity is measured instead of outcome
nothing is ever allowed to fail

Evidence needed

Before and after on the same task, same reviewer.

M-02 · S03Operating doctrine Where the method comes from

The system has to work when you are not there. Field network environments are built so the person on shift at three in the morning can run them without calling whoever designed them. A workflow meets the same test. If it only works when its author is available, it is not a workflow yet.

Positive control over what the system can reach. Around high-value assets, access is explicit, authorized, and accounted for — never inferred from convenience. Information classification for AI is that same discipline in a different setting.

Requirements come from the floor, not the vendor. Tactical systems that hold up are specified by the people who use them. So are workflows. What gets built is what the estimator, the project manager, and the coordinator actually need.

No new platform overhead. We do not sell proprietary software. We build the extraction logic and scripts directly into the tools your team already uses daily—whether via internal database pipelines or secure local server environments. Your team owns the capability, not a vendor subscription.

Adoption is decided in two places at once. Leadership can authorize a program. Only the floor can adopt it. I have spent my career at both ends, and most of it on the architecture in between.

Assume degraded conditions. Plan for the day the tool changes, the model changes, or the person leaves. A workflow with a named owner and written instructions survives all three. One without them survives none.

Translate in both directions. Executive intent has to become something a coordinator can execute on Monday. What the floor learns has to reach leadership in terms they can act on. Most programs die in that gap.

M-02 · S04What a finished workflow looks like Specimen

Every workflow is handed over as a single page: trigger, approved sources, exclusions, steps, the named reviewer, the failure modes, and how it is measured. If your team could not run it from that page without calling me, it is not finished.

Read one →

Next P-03 Four-week pilot What the engagement costs and produces →

Bring one workflow that repeats.

Bring one workflow that repeats. We will walk it end to end and see what the structure underneath it would have to be.

Book the call → Run the diagnostic first

Contact

nate@heilmanops.com
Hopkinton, Massachusetts