The question underneath the question: what to do when someone asks again.

Picture a volunteer-run music festival preparing its largest outdoor stage. During a crew meeting, a new stage captain asks why the performers need a separate check-in tent. The production manager explains that the tent holds wristbands and schedules. Ten minutes later, the captain asks why check-in cannot happen beside the stage. Someone explains that the sound crew needs the entrance kept clear. Near the end, the captain asks whether they are expected to stay at the tent all day or lead changeovers onstage.

Every answer about the tent was true. None answered what the captain needed to know: what job have I been given, where am I supposed to spend the day, and who takes over when the first band arrives?

That is what a repeated question often means. The easy reading is that the person was not listening. A better reading is that the answers so far have addressed the topic without meeting the need. The first question may sound like a request for facts. The second is evidence that those facts did not build the picture the person needs. By the third, the wording is usually different enough that the room treats it as a new question, even though the person is still reaching for the same missing answer.

People who know a system tend to answer from inside it. Ask the production manager why a tent exists and they see credentials, crowd flow, weather cover, and equipment lists. The new captain is standing outside that system. They may not care about the tent at all. They are trying to locate themselves in the day. More features will not help because the real question is personal: what does this mean for me?

When people do not get that answer, many stop asking. They nod because they do not want to hold up the meeting. Later they improvise, avoid the new process, or appear to ignore instructions. The team calls it resistance. Often it began as an unanswered question that everyone believed they had answered.

The first skill is noticing repetition. Keep a loose count of subjects rather than sentences. "Why do we need a check-in tent?" "Could we do this near the stage?" and "Am I there all day?" share almost no wording, but they orbit the same subject: the captain's place in the operating plan. If someone returns to one subject, treat that return as data. Do not wait for the exact sentence to repeat.

The second skill is to answer the person instead of explaining the topic again. Stop before giving a fuller description and test your reading. Say, "I think you are asking where your role begins and ends during the festival, not why we own a tent. Is that right?" This move does two things. It tells the person you noticed what was missing, and it gives them a safe way to correct you. A wrong guess offered as a question is more useful than a perfect lecture aimed at the wrong need.

Once they confirm, give the shortest answer that ends with their next action. "You lead stage changeovers. A greeter handles check-in. Start at the crew gate for the safety briefing, then move to stage left before the first sound check. If a performer arrives without a wristband, send them to the greeter rather than leaving the stage." Now the captain can see the day with themselves in it. The tent becomes one landmark instead of the center of the explanation.

Notice what made that answer work. It did not contain more detail about supplies, ticketing, or crowd control. It began with the person's responsibility, drew the boundary, and ended with what they should do when the two roles touch. A repeated question is rarely a demand for more total information. It is a request for the missing kind of information.

This can reveal that the system itself is wrong for the person. Once you understand the captain's actual responsibility, you might realize they should never report to the check-in tent. The room may have spent twenty minutes teaching a process that does not belong to them. Hearing the real question can make the object everyone was explaining disappear from the answer.

There is a trap for good explainers here. If you enjoy making ideas clear, a repeated question can feel like an invitation to improve the metaphor, draw a diagram, or add background. That instinct is useful when the first explanation was simply muddy. It works against you when you answered the wrong question. A longer answer aimed at the wrong target misses by the same distance.

Use the repeat as your signal to become curious. You can ask, "What decision are you trying to make with this answer?" or "Can you tell me what part still feels unclear?" Those questions are not a retreat from expertise. They are how expertise becomes useful to the person in front of you.

Try this in your next meeting. Count subjects, not exact phrases. The first time someone circles back, do not answer again immediately. Say what you think they are trying to understand in terms of their job, choice, or next move, and ask whether you have it right. Then answer in no more than four sentences, starting with their role and ending with what they do next.

Watch the room after that. The person will often add information they had been holding back because they finally believe the group understands the question. Everyone else may go quiet for a moment as they notice that several correct answers were never relevant.

That is lesson thirty one. When a question returns, stop polishing the answer. Find the need underneath it, put the person in the picture, and end with their next step.