Observe the real workflow

Start with the decision, not the interface

A workflow is not a list of screens. It is a sequence of decisions made by people and systems under constraints. Begin by asking what arrives, who must decide, what evidence they inspect, what action follows, and where the result is recorded. This keeps the observation tied to work that can later be measured and designed.

Treat the sponsor, process knower, operating owner, and disposition authority as separate roles. One person may hold several roles, but do not infer one from another. A sponsor can describe intent; the person doing the work can reveal practice; policy can define what is allowed; only a scoped authority can change the engagement boundary.

Ask for one recent case, not a tour of the ideal process. Open with: ‘Could you reconstruct the last case that required judgment?’ Then ask what arrived, what made it difficult, which source changed the decision, what workaround was used, and what the next person received. Avoid questions that embed the sold solution or invite a yes-or-no description of policy.

Use claim-matched evidence

An observed representative case proves that something occurred in that case. It does not prove frequency or permission. A test against an exact system build proves technical behavior for that build. A policy is normative only within its stated scope and revision. A stakeholder assertion proves that the statement was made. Preserve those limits beside every consequential claim.

Observe one routine case and one meaningful exception when feasible. Record exact passages, source identity, date, scope, owner, and limitations. If access is denied or the case is not representative, mark the evidence gap explicitly and route a next action rather than filling it with an assumption.

Finish with a field move

A field observation is useful only when it changes what happens next. End with one of three movements: find or validate the person who knows or owns the work; observe a representative case; or resolve a cited conflict. Avoid converting every unknown into a backlog item. Pick the unresolved constraint most likely to change the outcome or boundary.

Before leaving, read back the path in neutral language, distinguish observation from interpretation, and ask the operator what you missed. Confirm what evidence may be retained, who may review it, and who owns the next move. The field-conversation kit provides a reusable outreach, observation, and readback script.