For a while, I did not really like being described as a “cross-disciplinary talent.”
Not because the phrase is wrong.
It just feels too light.
It sounds as if doing a few different jobs, touching a few different industries, and speaking a few languages can naturally be packaged as an advantage.
But for me, being cross-disciplinary was never an advantage I had from the beginning.
It feels more like something I only understood after many different experiences slowly piled up. Looking back, the things that once seemed scattered had actually been connecting somewhere along the way.
Photography, events, model management, overseas business development, hospitality coordination, IT support, and AI tool implementation.
On the surface, these things do not always seem related.
But after actually working in them, I realized they often deal with the same core issue:
People, process, what happens on-site, and how to move something all the way to completion.
It did not start as a cross-disciplinary plan
I did not plan my career around becoming cross-disciplinary.
The first field I worked with in a serious way was photography and event operations.
Photography may look like a form of creation, but once it enters an event setting, it is no longer just about taking pictures.
You need to read the light, the person’s condition, the schedule, and the atmosphere of the room.
In portrait shoots or group photo sessions, photographers, models, participants, and organizers all have their own expectations.
Taking good photos is only one part of the work.
Whether the event ends smoothly, whether participants feel taken care of, and whether the model can work within a reasonable condition are just as important.
Later, through my work at Chingarno Studio, this became even clearer.
I was not only involved in shooting or on-site support. I gradually touched model management, event planning, marketing, promotion, and arrangements for Japanese model photo sessions.
That was when I started to realize that what I was doing was no longer just “photography.”
It was about arranging people and resources within limited time, limited manpower, and limited budgets so that things could actually work.
At the time, I did not call it project management.
I only knew that things could not be messy, the site could not fall apart, and what had been promised had to be delivered.
Language is not decoration. It is a tool that keeps things moving.
When people see Chinese, English, and Japanese on a profile, they may first think of language ability itself.
But for me, language has never been just a test score or a line on a resume.
It becomes useful only when it is used in the field.
Live interpretation is needed during events.
When speaking with Japanese partners, I need to understand concerns that are not always said directly.
When working with overseas clients, I need to find balance between different cultures, expectations, and working rhythms.
What matters to me is not the fact that I can speak several languages.
It is that language lets me stand between different people, help them say things clearly, and align what they actually need.
This becomes especially obvious in cross-border work.
Many collaborations are not blocked because there is no opportunity. They are blocked because both sides do not fully understand each other’s assumptions at the beginning.
What feels normal in Taiwan may feel risky from the Japanese side.
What feels like a basic procedure in Japan may feel too rigid from the Taiwanese side.
If I only translate the words, the real problem is not solved.
I need to understand what the other side is worried about, and also understand what my side can truly commit to.
So language, to me, is not a way to prove that I am international.
It is more like a tool that prevents things from getting stuck.
Hospitality taught me more than service. It taught me control.
After moving to Japan for work, I entered the world of high-end travel and business hospitality.
At first glance, this field looks very different from photography.
One side has studios, models, and event sites. The other has luxury travel, hotels, cars, suppliers, and overseas clients.
But after doing it for a while, I found that the core was actually quite similar.
Behind a smooth and polished outcome, there are always many details that most people will never see.
The itinerary has to make sense.
Suppliers need to be confirmed.
Client requests have to be turned into executable arrangements.
Someone needs to judge what to do when plans change suddenly.
And when something happens on-site, it is not enough to say, “That is not my responsibility.”
This is especially true in high-end service.
Clients may never know how many messages, calls, and confirmations were needed just to secure one car, one hotel, or one time slot.
But if one part goes wrong on the day itself, they will feel it immediately.
That is very close to event work.
The best situation is when participants or clients feel that everything happened naturally.
But that kind of naturalness is usually built on a lot of preparation that was not natural at all.
IT support and AI implementation changed how I understand problem-solving
Later, I started moving closer to IT support and AI tool implementation.
At first, it looked like a major shift.
Moving from photography, events, and hospitality into IT, systems, and AI tools does not look like one straight line.
But to me, it did not feel like a break.
It felt more like an extension.
Because IT support is also about breaking down problems.
When users run into trouble, they cannot always describe the issue clearly.
Sometimes they say the computer is broken, but the real issue is the network.
Sometimes they say the system does not work, but the actual problem is permissions, workflow, or the way they are used to operating.
You cannot hear one surface-level sentence and rush to a conclusion.
AI implementation is similar.
Many companies already know that AI is becoming important.
The real question is where to use it, who should use it, how to teach it, and how to make it part of daily workflow.
When doing this kind of work, I often found myself using abilities I had built in events, hospitality, and photography.
Read the field.
Listen to how people describe the problem.
Find the real bottleneck.
Break something complicated into steps the other person can actually understand.
Do not just throw a tool at people. Help them use it for real.
After moving into IT and AI, I became more certain about one thing:
What I had accumulated was not just a fixed skill from one industry.
It was a way of handling problems.
Cross-disciplinary experience is not just a pile of job titles
I used to worry that my experience might look too scattered.
COO at a photography company, event marketing, model management, procurement project assistant at a school, hospitality coordination, IT support, AI consultant.
If you only look at the titles, it is not exactly a straight path.
But I no longer see it that way.
A straight path is not always more valuable.
And a scattered path does not always mean there is no direction.
What matters is whether these experiences have slowly formed a shared ability.
For me, that ability is probably this:
Entering an unfamiliar environment, understanding the field first, and then moving things forward.
Photography events were like that.
Cross-border collaboration was like that.
High-end hospitality was like that.
IT support was like that.
AI implementation is also like that.
Every field has its own language, rules, and habits.
But once you actually enter the field, you realize many problems cannot be solved by professional terms alone.
You need to be willing to ask.
Willing to observe.
Willing to admit that you do not understand everything at the beginning.
And you need to find the next step even when the information is incomplete.
These abilities do not appear overnight.
They do not become real just because someone writes “cross-disciplinary integration skills” on a profile.
They are built one case at a time.
How I see my own cross-disciplinary background now
If I had to describe myself now, I would not start by saying I am a cross-disciplinary talent.
I would rather say that I am someone who has built problem-solving ability through different on-site environments.
I have worked in photography, where aesthetic judgment and field awareness matter.
I have worked on cross-border events that required communication, trust, and coordination.
I have handled high-end clients, suppliers, itineraries, and sudden changes.
Later, I brought those experiences into IT support and AI tool implementation.
Not every step was smooth.
Not every transition looked clean.
But those experiences helped me understand the language of different people.
Creators care about the work.
Clients care about the experience.
Companies care about cost and results.
On-site staff care about whether the process can actually run.
Users care about whether a tool can really make their work easier.
None of these perspectives is more important than the others.
They simply need to be understood.
And I happened to spend a lot of time moving between them.
So for me, being cross-disciplinary is not the advantage itself.
It is only the result.
The real advantage is what slowly formed behind these experiences:
The ability to read the field.
The ability to communicate with different kinds of people.
The ability to turn vague needs into concrete action.
And the ability to move things forward even when there is no standard answer yet.
These things are not easy to package.
But now, I think that is exactly why they feel closer to the truth.