Everyone who has organised a large event will tell you the idea is the easy part. Turning “Penang should have its own digitalisation conference” into two days at Setia SPICE Convention Centre with government, MNCs and industry leaders in the same room meant running straight into the same execution failures I now see inside almost every organisation I work with.
Three Failures That Almost Sank PDX
1. Everyone agreed on the goal, nobody agreed on the trigger
Early on, three teams all believed “get sponsors confirmed” was someone else’s next move. Nobody was wrong about the goal. Nobody had been told exactly what event should trigger their part of the work. The fix wasn’t a pep talk about ownership — it was a one-page document naming, for every workstream, the single event that started it.
2. Knowledge lived in one person’s head
For the first PDX, sponsor relationships existed mostly in my own memory and inbox. The moment I was unreachable for two days, decisions stalled, not because the team lacked judgement, but because they lacked the context I hadn’t written down anywhere. We now document context, not just tasks — the “why” behind a relationship or a commitment, not just the “what.”
3. Feedback arrived too late to matter
In year one, we found out what delegates actually wanted from post-event surveys — useful for next year, useless for the event already over. Now we build in short feedback checkpoints during planning, not just after the event, so a bad assumption gets caught in week three instead of month eleven.
The Pattern Behind All Three
None of these were knowledge problems. Every team involved knew, in the abstract, what needed to happen. What was missing was the specific trigger, the written-down context, and the fast feedback loop that turns knowing into doing. That gap — not a lack of smart people or good intentions — is what I’d call the real execution gap.
FAQ
Isn’t this just a project management problem?
Partly — but project management tools don’t fix it if the underlying triggers and context were never defined. The tool organises the gap; it doesn’t close it.
What's the fastest way to check if my team has this problem?
Ask three people on the same project to describe, unprompted, what specifically triggers their next task. If you get three different answers, you've found the gap.