Interview the Person Who Says No

The most valuable knowledge in your organization is why things get rejected. Almost nobody writes it down.

I built a Copilot intake agent for a clinical research institute, and the obvious version of that project was automating the form — faster submissions, fewer clicks. But the expensive problem was never intake speed. It was what happens downstream, when a submission bounces: rework. Every bounce is days of delay and a loop through a queue that was already full.

So before building anything, I did two things most agent projects skip.

First, I interviewed the reviewer. The person who bounces submissions carries an entire rejection taxonomy in her head — criteria she applies in seconds, refined over years, documented nowhere. What makes you send something back? What do you check first? What’s the mistake people make over and over? That conversation was the requirements document. Not what users say they want — what the expert refuses to accept.

Second, I mined the rework history. Every bounced submission is a labeled example of failure the organization already paid for. Patterns fall out fast.

Both went into the agent as a validation layer. It checks each submission the way the reviewer would — before it enters the pipeline, not after it’s wasted a spot in the queue. Rejection knowledge moved from the end of the process to the front. The reviewer reviews exceptions instead of everything.

The pattern generalizes anywhere a queue meets a reviewer: contracts, claims, credentialing, code review. Interview the person who says no. Their rejections are the spec.