Go to the Field, Not the Meeting Room

Pain appears in the work, not in a conference-room summary. Shadowing is the FDE’s field method.

Where do the right problems come from? FDE experience says they come from pain, and pain appears in the work itself—not in the meeting room.

After reading, you should be able to answer:

• What shadowing actually involves, and why you blend into the customer’s daily work
• Why watching what people really do beats hearing what they say the process is
• How to get past a rehearsed, spotless demo to the process underneath

Participatory observation

Anthropologists call it participant observation; Toyota calls it genchi genbutsu. Go to the place where the work happens, watch the real objects, and learn from the actual situation. A soldier may never ask for a better map because they do not know software can provide one. An engineer following the patrol sees the hesitation that creates the real product idea.

Go around the translation layer

Requirements lose information each time they pass through IT, procurement, consulting, or a vendor. “We need a data platform” may really mean “this person cannot reconcile four sources every Monday.” The FDE’s first responsibility is to reach the nerve of the pain, not to accept the translated version.

Shared work reveals the truth

In an interview, the customer is being studied and may perform a polished version of reality. While debugging together, the customer becomes a teammate. a16z puts it more bluntly: what changes a company is people, not only product a16z-forward-deployed. That is when comments such as “we never trust this field” or “we still call someone even though the process is in the system” surface. Those details often decide whether a deployment works.