Mythology Canvas · The Argonauts · 12 min read
This is not a retelling. It is a debrief.
The Project
Project Name: The Golden Fleece Expedition. Project Manager: Jason of Iolcus. Sponsor: King Pelias of Iolcus. Executing Organisation: The Argonauts. Duration: Approximately 3 years. Outcome: Fleece retrieved. Project closed. Post-project governance: catastrophic.
Initiating — The Hostile Charter
Every project begins with a mandate. Not every mandate is honest.
King Pelias did not commission this project because he believed in Jason’s leadership. He commissioned it because he expected Jason to die trying. The Golden Fleece was in Colchis, guarded by a dragon that never slept, held by a king who killed visitors. The business case was a death sentence dressed as an opportunity.
This is the hostile sponsor pattern. The project exists not to succeed but to dispose of the project manager. Jason’s first risk was not the dragon. It was the person who signed the charter.
Sponsor alignment is not optional. A sponsor whose interests diverge from the project’s success is not a sponsor. They are a stakeholder with veto power and plausible deniability.
Mytholagile lens: In the Prometheus Cycle, the pioneer pays the cost of delivery. Jason accepted the mandate knowing the cost. That acceptance was the real initiating event.
Planning — Build Before You Sail
Jason did not sail the day after the mandate. He built.
The Argo was not an existing asset. Jason commissioned it from Argus, the greatest shipbuilder of the age, using timber from Mount Pelion blessed by Athena. Resource planning began with the vessel — because without the right infrastructure, no team survives the journey.
Then came team acquisition. Jason did not hire generalists. He recruited archetypes. Hercules: physical capability, extreme capacity — unmanageable at scale, invaluable in crisis. Orpheus: communication and influence — his lyre would later solve a problem no weapon could. Castor and Pollux: navigation and combat, dual-skilled operators. Medea: not in the original plan. The most critical resource on the project was not identified during planning.
This is the planning paradox every project manager knows: you cannot plan for the resource that will save you, because you do not know you need them yet.
A risk register is not a comfort document. It is an honest map of what you do not control. The dragon risk was logged and left open. Sometimes you plan knowing that a critical risk has no identified response. You proceed anyway, because the alternative is not proceeding.
Executing — Three Encounters, Three Principles
The plan met reality at the first port of call. It always does.
The Symplegades: the Clashing Rocks crushed everything that passed between them. The solution was not strength. It was timing and sacrifice — release a dove, watch the rocks clash, sail through in the window before they reset. Minimum viable passage. One shot. This is constraint navigation under irreducible risk. You cannot remove the rocks. You can only find the window.
The Sirens: they did not attack. They persuaded. Their weapon was not force but narrative — a story so compelling that sailors abandoned the mission to chase it. Orpheus’s response was not to block the Sirens. It was to play louder. Counter-narrative as risk response. The team stayed on course not because they could not hear the Sirens, but because they had a better story to listen to. The greatest threat to a project in execution is not the external obstacle. It is the internal narrative that makes stopping feel rational.
Medea at Colchis: King Aeetes had no intention of surrendering the fleece. He set impossible conditions. Jason could not do this alone. He could not do this at all — without Medea. She was the king’s daughter, a sorceress, and she fell in love with Jason. She provided the ointment that made Jason fireproof, the strategy that defeated the warriors, and the sleeping draught that neutralised the dragon. The fleece was retrieved because of a resource that was not in the project plan, not in the budget, and not in the risk register. She was not a dependency. She was a discovery.
Every major project has a Medea moment — the unplanned intervention that makes delivery possible. The question is not whether it will happen. It is whether the project manager is positioned to recognise it and move.
Monitoring and Controlling — Every Port Is a Checkpoint
The return journey was longer than the outward one. It always is. Each stop on the return route was a control point. Losses were recorded. The team that arrived in Colchis was not the same team that left Iolcus — Hercules had departed mid-journey, others had fallen. Change requests were processed under duress.
Control is not about preventing change. It is about making change visible, deliberate, and documented — even when the pace of execution makes documentation feel like a luxury.
Closing — The Bitter Harvest
The fleece was delivered. The project was closed. The project manager was not.
Jason returned to Iolcus. Pelias was dead. The mandate was fulfilled but the sponsor was gone, the political landscape had shifted, and Jason had no governance structure for what came next. He moved to Corinth. He abandoned Medea. He sought a politically advantageous marriage. Medea destroyed everything he had built.
The Argo rotted on the shore. A beam fell from it and killed Jason.
Closing is not signing off the deliverable. It is extracting the knowledge, honouring the formation, and ensuring that what was built during execution does not collapse the moment the project ends.
Mytholagile lens: The pioneer cost is not always paid during delivery. Sometimes it arrives after — when the organisation moves on and the change agent is left without a formation to stand in.
The Canvas
Below is the full PM Canvas for the Golden Fleece Expedition — risk register, process groups, team archetypes, and lessons extracted. Built on PMI’s process framework, viewed through the Mytholagile lens.
PDF toolkit version coming soon — download the full canvas as a print-ready reference.
This canvas is part of the Mytholagile Mythology Canvas series — where the 49 process groups of PMI, the 12 principles of the Agile Manifesto, and the archetypal wisdom of world mythology converge into a single operating doctrine for leaders navigating uncertainty.
Hat Sarsılmaz. The line holds.
Leave a Reply