I treat team-building as the first product. Before any tool ships, the team that ships it has to be the right shape, the right people, the right division of labour, the right rhythm. Most projects that fail in newsrooms or social-sector programmes fail at this layer, not at the execution layer. Getting the team right is slow work and looks unproductive from the outside; I prefer to be slow at it on purpose.
Multilingual operation is not a nice-to-have for me, it's the medium I work in. I run technical conversations in English, social-sector conversations in German, editorial conversations in Arabic, and stakeholder management in whichever combination the room needs. The interesting part isn't the languages themselves; it's noticing, in real time, which register a conversation is actually being held in, and adjusting before the misunderstanding compounds. Most cross-cultural project failures are register failures, not language failures.
I prefer decisions documented in plain prose to decisions captured in tickets. Tickets describe tasks; prose captures why. A team that knows why a decision was made can adapt it when conditions change; a team that only has the task can only execute or escalate. I write a lot, internal briefs, executive summaries, decision memos, because writing is how I find out what I actually think.
The journalism years left a habit I haven't lost: the assumption that an audience will not forgive imprecision. That carries into engineering work as a low tolerance for hand-waving, into social work as a low tolerance for paperwork that doesn't survive contact with reality, and into management as a low tolerance for plans that no-one on the team can repeat back accurately. Specificity is the cheapest form of respect.