I have changed professional context several times: photography, audiovisual production, a digital agency, products and a tech company. The thread is neither the industry nor a job title. It is how I enter problems, connect people and accompany an idea until it takes concrete form.
Every change included a phase that felt like starting again: new words, metrics, stakeholders and definitions of what matters. The danger is either presenting previous experience as irrelevant or forcing similarities that do not exist. I learned a third approach: recognise what has genuinely changed and carry forward only the method that still works.
An industry is not a backdrop. It has its own rules, timing and responsibilities. Audiovisual production teaches that a lost shooting day cannot be recovered with good intentions. An agency teaches simultaneous management of projects and expectations. A product requires continuity beyond delivery. A tech company adds technical dependencies and complex decision cycles. Transferring a method does not mean ignoring these differences.
Observe first, transfer later
In a new context, the most useful skill is not having an immediate opinion but understanding how the system distributes information and decisions: who knows and decides what, which errors are reversible, and which words carry specialist meanings. Previous experience should improve the questions, not produce automatic answers.
Photography left me the habit of observing before intervening. In production it became an awareness of the set and its dependencies; with customers and products, attention to what is requested and what remains implicit. The tool changes, the posture stays: do not fill a context with what you already know before understanding what it is saying.
The thread lies in the questions
The questions I carry remain surprisingly stable. What is the concrete result? Who must contribute? Which constraint are we ignoring? What has to happen after delivery? The answers differ across a shoot, a digital project and a technology negotiation, but the questions continue to orient the work.
A thread does not require an immutable professional identity. It provides criteria for learning. If my value lies in connecting the broad picture with delivery, I look for that connection in every new sector: the vertical expertise to respect, the languages to learn and the point where translation may help.
Lose status to gain context
Changing environment temporarily reduces confidence. In a familiar sector you know which details matter and recognise errors quickly; in a new one you must ask, accept uncertainty and rely on others' judgement. It is uncomfortable when you already have years of experience, but pretending to know creates worse decisions.
Operational humility does not erase existing knowledge. It means not using that knowledge as authority over what is still unfamiliar. I can bring coordination experience to a technology project without pretending to be the developer, or contribute to content strategy without claiming the creative work. This distinction protects the team and makes experience transferable rather than invasive.
"Continuity does not mean always doing the same thing. It means recognising the questions we continue to carry with us."
Consistency does not mean remaining the same
Looking back, the path is not linear but no longer feels fragmented. Its consistency lies in moving from vision to delivery and caring for the relationships required along the way. I changed tools and contexts because that passage took different forms, not because I wanted to become a different professional every time.
That awareness is useful for the future. I need not predict my next sector to know what to carry: observation, translation, precision in promises and respect for other people's expertise. They are stable enough to guide me and flexible enough not to become a cage.
Changing context without losing the thread is not about retrofitting a perfect story. It means identifying a way of working and testing it under new conditions. If it holds, it becomes experience; if not, it must change. The thread does not prove every choice was planned — it prevents wasting what each choice taught.
There is also the work of explaining the path. CVs divide experience into companies and roles, while transferable value often crosses those boxes. Precision requires examples: not simply claiming adaptability, but showing which question recurred, which transition became clearer and where learning began from zero. The path becomes legible without hiding its discontinuities.
Changing context also has a cost that should not be romanticised. Credibility, references and speed must be rebuilt each time. For months, learning may make the contribution less visible. Treating that time as an investment rather than evidence of inadequacy prevents compensation through false confidence. New credibility grows as better questions gradually become better decisions.
