Expertise Should Not Make People Feel Small
Good expertise does more than provide answers. It helps people understand their own problem, ask better questions, and take part in the decisions that shape the work.
People often look for an expert before they know exactly what to ask. They may believe they need a video without knowing what the video should change. They may want a new website without having decided what visitors should do there. They may feel that their organization should use AI while still being unsure where it would genuinely help.
That uncertainty is often the honest beginning of a project.
We seek expertise because we hope someone will help us organize what feels vague. Yet some consultations leave people feeling smaller than when they arrived. A question is answered with unfamiliar language. A concern is dismissed as too basic. By the end, the client may feel that not understanding the field has disqualified them from the conversation.
I do not think that is a good expression of expertise.
Kindness does not weaken expertise
Expertise is more than knowing more than another person. It also includes the ability to explain what matters, distinguish what is known from what still needs to be learned, and help another person participate safely in a decision.
Complicated language can make someone sound impressive. A good expert, however, does not make a difficult problem harder than it needs to be. They explain which choices are available, what each choice may cost, and where deeper knowledge is required. They make room for questions without turning uncertainty into embarrassment.
Kindness is not the opposite of professional rigor. It is one of the ways rigor becomes useful. When people understand the work, they can make informed choices and share responsibility for the result.
I do not have every answer. What I try to offer is a clear account of what I know, what I do not yet know, and whose deeper expertise may be needed. I want people to leave with a better understanding of their problem, not a stronger sense of their own inadequacy.
A requested deliverable is often only the first clue
Most enquiries begin with the name of a deliverable: a film, a website, an application, an AI workflow. Those requests are not wrong. They are often the most concrete way to describe a need before the purpose and constraints have been discussed.
The same promotional film can attract attention, explain a complex technology, or build trust. A website may be a public introduction, or it may need to support applications and daily operations. An AI project may reduce repetitive work, organize evidence, or help a team explore options.
Before deciding what to make, I ask what should become different. Who is the work for? What do they already understand? What should they remember or do next? Who will continue using the result after delivery?
These questions do not suggest that the client has failed to prepare. They bring the purpose and constraints that already exist in different parts of the client’s mind into a form we can examine together.
Looking beyond one familiar answer
Deep specialists are essential. A filmmaker notices choices in image, sound, and production that others may miss. A developer sees structural risks inside a system. A designer pays attention to how a person understands and moves through an interface.
At the same time, all of us naturally interpret problems through the disciplines we know best. A video producer may see a film. A development company may see an application. An AI consultant may see automation. This is not necessarily self-interest. Familiar tools simply shape the way we see.
My experience across production, platforms, education, applied AI, international communication, and Scouting gives me several ways to examine the same situation. Its value is not that I can replace every specialist. It is that I can resist narrowing the problem too early.
Sometimes a clear document serves the purpose better than a film. Sometimes an existing process needs repair before a new system is built. A request for a simple website may also reveal a need for an operating platform.
The same principle applies to networks. A network is not proof that one person has every answer. It helps bring another perspective into the room, identify when deeper expertise is needed, and connect the work with an appropriate collaborator.
When working together is useful
If a problem is already well defined and only deep execution in one discipline is required, the best choice may be to go directly to the strongest specialist in that field. Not every project needs me.
My way of working becomes useful when several fields overlap, when the deliverable is still only a guess, or when important meaning is likely to disappear between strategy and execution. I can help make a shared map, compare possible forms, and carry the original purpose into the work.
Expertise should not silence the person asking for help. It should give them better questions and a clearer place in the decision. A good consultation does not prove how little the client knows. It helps everyone understand what the work now requires.