What’s one lesson you’ve learned from a project that didn’t go as planned?

One of the most enduring lessons I’ve learned came from a project that was, on paper, a failure—delayed, over budget, and misaligned with the sponsor’s expectations.
But the deeper issue wasn’t execution — it was assumption.
We assumed alignment where there was only polite agreement, and we mistook silence for buy-in.
That experience taught me that alignment is not a checkbox — it’s a continuous dialogue.
True alignment requires space for dissent, the courage to surface hidden expectations, and a willingness to revisit understanding throughout the project lifecycle — not just at kickoff.
Since then, I’ve prioritized active listening, stakeholder mapping, and early signal detection.
It reminded me that even the most robust plan can be undone by unspoken assumptions — and that clarity is the real currency of successful delivery.
Sometimes, it takes a project that breaks down to help us build ourselves up as better leaders

One key lesson came during an overseas installation project where we faced significant delays due to the lack of emergency logistics support. A critical piece of network equipment arrived damaged, and without pre-staged spares or local sourcing options, we were stuck waiting on a replacement from the U.S., which took nearly two weeks.

I quickly adapted by reorganizing the team’s tasks to stay productive and identifying a compatible workaround using available gear. Since then, I’ve made contingency logistics planning a core part of every project—ensuring critical spares are pre-staged, alternate sourcing options are identified, and escalation paths are clear before we deploy.

This experience reinforced that even the best execution plan can stall without logistics resiliency. Planning for the unexpected is what keeps projects on track.