Sep 14, 2026
There is a particular kind of frustration that shows up in many financial planning practices, and it usually sounds something like this: “Why do they keep asking me the same thing?”
The person saying it may be the founder, the practice manager, the senior administrator, the paraplanner, the compliance person, or simply the one person in the business everyone runs to when they are unsure. It is not always the most senior person. Often, it is the most reliable person, the most experienced person, or the person who has quietly become the unofficial operating manual for how things really work.
At first, repeated questions can look like a people problem. It can feel as though someone is not thinking for themselves, not remembering what was explained last time, not taking ownership, becoming too dependent, or interrupting someone else’s day because it is easier to ask than to check. Sometimes there is truth in that. There may be a capability issue, a confidence issue, a training gap, or an accountability problem that needs to be dealt with properly.
But before a practice jumps straight to irritation, it may be worth asking a more useful question: “Why does the team keep needing to ask?“
Repeated questions are rarely just about the question being asked. They are often a signal that something in the business is unclear, inconsistent, inaccessible, outdated, or not trusted. If the real process lives in someone’s head, people will ask that person. If the written process does not match what actually happens, people will ask whoever knows the real version. If exceptions are handled differently depending on the adviser involved, the client, the urgency, or who happens to be available that day, people will ask before acting. If the system is full of information but nobody knows which information is current, complete or reliable, people will stop treating the system as the source of truth.
This is how one person becomes the shortcut.
Instead of checking the process, people ask the person. Instead of relying on the system, people ask the person. Instead of escalating through a defined route, people ask the person. Instead of making a decision against an agreed standard, people ask the person. And because that person is usually capable, helpful and invested, they answer. They explain. They remind. They check. They fix. They rescue the matter before it becomes a visible problem. The business then starts to believe the issue is under control, when in reality it is being absorbed by someone competent.
That is where the operational risk becomes easy to miss. The reliable person becomes part of the process without anyone formally acknowledging that the process depends on them. Their memory becomes the reference point. Their judgement becomes the control. Their follow-up becomes the safety net. Their tolerance for interruption becomes one of the reasons work keeps moving.
That is not operational calm. That is a person holding the roof up with one hand while replying to emails with the other.
From the outside, the business may still look functional. Clients are serviced, documents go out, reviews happen, new business is processed, compliance evidence is eventually gathered, queries are answered and problems are solved. Underneath that visible activity, however, the practice may be relying heavily on informal knowledge, personal workarounds and the goodwill of people who are carrying more than their role should reasonably require.
This is where it starts to sting: If your team keeps asking the same questions, the issue may not be that they are hopeless. It may be that the business has not made the answer clear enough, accessible enough, trusted enough or owned enough for people to act with confidence. That is not a team problem alone. That is an operating model problem.
The difficulty is that repeated questions often become irritating long before they are properly analysed. The person being asked starts feeling interrupted and overburdened, while the people asking may become nervous, dependent or unsure because they do not want to get it wrong. Management may assume the team needs more training, another checklist, an updated SOP or a reminder to “please follow the process”.
Sometimes that may help. But let’s be honest. Another reminder rarely fixes a business that has trained everyone to ask the same person for the real answer.
If people do not know what to do, train them. If they are avoiding responsibility, deal with accountability. If the process is unclear or unrealistic, fix the process. If every exception turns into a judgement call, define the decision rules. If nobody trusts the data, clean up the system. If only one person knows how things really work, stop pretending that is fine just because they are good at it.
Helpful people often carry messy systems for far too long. They do it because they care about the client, the team and the quality of the work. They remember what was agreed. They know which adviser prefers what. They know which form needs to go where. They know what compliance will ask for later. They know who needs a reminder, who needs a nudge, and who needs a full rescue mission with snacks. That knowledge is valuable. It should also be captured, structured and supported properly.
A good operating model does not remove the need for experienced people. It makes sure their experience is used where it adds value, instead of being spent answering the same questions on repeat like a very tired helpdesk with feelings.
The danger is treating every repeated question as an individual irritation instead of seeing the pattern. One question may just be a question. The same kind of question from different people, at different times, about the same type of work, is information. It tells you where the process is not clear enough, where ownership is vague, where the team lacks confidence to act, or where the documented version of the business and the lived version of the business have drifted apart.
In an advice business, that uncertainty does not stay neatly contained. A question about who should follow up with the client can become a delay. A question about what evidence is required can become a compliance gap. A question about who may approve an exception can become inconsistent treatment. A question about whether something was done can become duplicated work. A question about where to find the latest information can become poor client service.
Small uncertainties create small interruptions. Small interruptions become normal. Normal interruptions eventually become the way the business runs. Then everyone wonders why the team is busy, tired and still not moving cleanly.
A useful test is to ask what would happen if the usual answer person was unavailable for two weeks. If work slows down, decisions pause, follow-ups drift, or the team starts circling like confused pigeons, the issue is not simply that people ask too many questions. The issue is that the business has allowed too much operational knowledge to sit with one person.
That is fixable, but only if the practice is willing to look at the real problem.
Every repeated question is pointing somewhere. It may be pointing to a missing process, a process nobody uses, unclear roles, weak handovers, poor system discipline, a decision bottleneck, or a reliable person who has quietly become the unofficial operating manual for the business. Once you know what the question is pointing to, you can start fixing the right thing.
The solution is usually not a beautiful new document that gets approved, uploaded and ignored. The solution is to align the way the business says work should happen with the way work actually moves through the team. That means clarifying ownership, making decision rules visible, agreeing where answers live, checking whether the system supports the process, capturing the knowledge that sits with key people, improving handovers, and creating escalation points that do not depend on panic as the official trigger.
This is what gives a team room to breathe. It also protects the people who have been holding too much together for too long. The goal is not to make people less helpful. It is to stop making helpful people compensate for unclear systems, vague ownership and knowledge that lives in the heads of a few exhausted humans. This is the type of operational gap Karenu Consulting (Pty) Ltd helps financial planning practices identify and fix.
We look at how work actually moves through the business, where the same questions keep appearing, where decisions get stuck, where handovers are unclear, and where the practice is relying too heavily on memory, goodwill and informal rescue missions. If your team keeps asking the same questions, the answer may not be another reminder, another checklist or another “please follow the process” email. It may be time to fix the part of the business that keeps creating the question.