Cargosight is a Berlin–Athens logistics platform with a 64-person product organisation. Lena Voss, VP of Engineering, walks us through the eight-month rollout.
Cargosight ran specs in Confluence, tickets in Jira, conversation in Slack and roadmap in a quarterly slide deck maintained by one person. Each artefact was accurate on the day it was written.
The failure was not any single tool. It was that the reasoning behind a decision lived in a channel that scrolled away in eight days, while the decision itself lived in a document that never explained itself. New engineers re-opened settled questions because there was no honest way to find out they had been settled.
The platform team moved its stand-up first. Nothing else changed. Two weeks of running both was enough to make the old meeting feel expensive.
New specs opened as Doc Threads. Old ones stayed in Confluence and were left to age out rather than migrated, which is the decision Lena says saved the rollout.
Sprint Pulse ran on two squads for a quarter before anyone else saw it, so the thresholds were tuned before they were trusted.
Only after three quarters of Decision Records existed did the roadmap leave the slide deck. By then it had something to link to.
The thing I did not expect: onboarding got faster. A new engineer can read why we chose the queue we chose, in the thread where we argued about it, without asking anyone.
Cargosight is moving async architecture review across the remaining three squads through 2026, and is piloting public roadmap export for their two largest freight customers.
Lena joined NexaFlow as VP of Customer Success in 2023. She still runs the Cargosight account review personally, which is either good practice or a conflict of interest depending on who you ask.