Legal Ops

If Your Team Keeps Asking, Your System Isn't Answering

Repeated questions are not a people problem. They are a system problem. Here is the fix.
If Your Team Keeps Asking, Your System Isn't Answering
Written by:
Camila Costa
Published in:
May 8, 2026

How many times this week has someone asked legal:

"What template should I use?"

"Did legal already approve this vendor?"

"Where is the Acme contract right now?"

"Who do I need to copy on this?"

"Do I need a separate NDA for this conversation?"

If the answer is "every day, multiple times, often the same person twice," you don't have a curious team. You have a system that isn't answering.

Repeated questions are signals, not annoyances

When the same five questions come back over and over, the obvious response is to feel impatient. The right response is to treat it as data.

A repeated question is the system telling you something is missing. The information exists, but it lives in a place where the asker cannot reach it without going through a person. So they go through a person. Every time.

The lawyer becomes the lookup service. Their day fills with answers that the system should have given automatically.

If this is happening in your company, mapping just one workflow is the fastest way to expose the problem.


Why the questions multiply

Companies tend to respond to repeated questions in two ways. Both make it worse.

The first is writing a wiki page nobody reads. The page exists. It is comprehensive. It is also out of date within three weeks, hard to find, and assumes the reader already knows the vocabulary. So the questions keep coming.

The second is sending a Slack reminder. "Please remember to fill out the intake form before sending contracts." A week later, the same person sends a contract by email. Memory does not scale.

What works is removing the question entirely. Make the system surface the answer at the moment the person is about to ask. The form auto-shows the right template based on what the user selects. The status shows up next to the request. The vendor's prior approval gets flagged automatically when their name is entered.

The question never gets asked. Not because the user got smarter. Because the answer was already there.

The compound cost of small questions

A two-minute question doesn't seem expensive. Repeated forty times a day across a five-person team, it consumes more than six hours of legal time per day. Every day. Forever.

That is one full-time lawyer, hired to answer questions the system could have answered for free.

The team feels stretched, the leadership feels frustrated, and the budget conversation eventually turns into "we need more headcount." It probably doesn't. It probably needs the system to start answering for itself.

Closing thought

If you want to know whether your operation is well-designed, listen to the questions your team gets asked the most. Each one is a piece of friction the system left for a human to absorb.

A well-designed system reduces those questions over time. A poorly-designed system multiplies them. The team feels the difference long before the dashboard does.