Episode 2, the short cut. Watch the full episode on YouTube.
Ask a turnaround organization where its program lives and you will get a list, not an answer. The ten-year plan is in a spreadsheet. The work process is in a binder, or a PDF of a binder. The standards are on a share drive somebody reorganized last year. The risks are in one register, the actions in another, and the lessons are in a closeout report that got presented once and then went quiet.
Every one of those is defensible on its own. Somebody built each of them carefully, and each does its job. The failures do not happen inside them. They happen in the seams.
Three seams, and what falls through each one
The plan knows the dates. It does not know the people. A long-range plan will happily show two events preparing in the same months. What it does not show is that the same four people are carrying both, because staffing lives somewhere else. That collision is cheap to solve two years out and expensive to discover two months out, and almost nobody sees it in time, because seeing it requires two systems to be looking at each other.
The work process names an accountable approver. Nothing tells the approver. A good work process assigns responsibility and accountability on every activity. Then it gets published, and the named person finds out what they own in a meeting three weeks after the deliverable was due. Accountability that is written down and not delivered is not accountability, it is documentation.
The last event learned it. The next event repeats it. Closeout is where the most expensive knowledge in a turnaround gets captured, and it is captured into the least-read document the program produces. The planner about to repeat the exact step that went wrong has never seen page 40 of anything. The lesson exists. It just does not arrive where the work is.
What one system actually has to do
The point is not to buy fewer tools. The point is that a program has one spine, one event record, and that the pieces read on each other. Five things follow from that, and they are the test worth applying to whatever you run today.
The standard travels with the work. Every activity reads on the standard that governs it, and the document is on the activity, not on a shelf two clicks away. Your standard, in your language, with your governance, so a planner never has to know which folder was the current one.
Accountability sits on the activity, not on a chart. A responsible role and an accountable approver, on the item itself, and the person is told when they are assigned. Not a matrix on a wall.
A gate is a recorded decision, not a meeting. Continue, conditional, or hold, made by a named person, after they have been shown what is owed: the lessons captured this phase, the risks reviewed, the open actions being accepted through the gate. Most programs write this on a slide. It has to be how the thing works.
Evidence, not a checkbox. A key deliverable cannot be signed off empty. Submitted, approved, recorded, with the artifact attached, which is an audit trail rather than a cell somebody typed “done” into.
The loop closes without anybody being heroic about it. A lesson is a thirty second capture with no blame attached. It resurfaces at the same step of the next event, feeds the closeout workshop, and becomes an owned action with a real date that can land in the next event as work. Risks carry forward the same way, each behind one question: does this still apply.
The layer that is hardest to retrofit
Everything above is structural, and a determined organization can approximate most of it with discipline and spreadsheets. The layer that does not retrofit is the individual one.
All of that governance exists so that one planner, on one Tuesday, knows what to do next and does it better than the person who sat in that chair last event. That means a page derived from their actual assignments on this actual event: their activities in the order they come due, the deliverables they owe, the standards to read with the date each one is first needed, and the lessons the last crew learned on those same steps, with the fix attached. Nobody went looking for any of it. It showed up where the work is.
And when they have a question, they should be able to ask it and get an answer that cites their own standard by section, pulls in their own team's lessons, and then says what it cannot tell them. Whether a plan is acceptable is the named approver's call. A coach explains, points to the standard, and hands the decision back to the people who own it. It coaches. It never decides. That boundary is not a limitation, it is the reason the answer is trustworthy.
The test
Software does not run a turnaround. People run turnarounds. But a lot of world-class teams spend their capacity fighting their own filing cabinets, and that capacity is the scarcest thing in the window.
So the question worth asking about your own program is not which tools you have. It is this: when a planner sits down at T minus two hundred days, where does your organization actually keep what good looks like, and how does it reach them? That is the problem STO·PATH was built to solve, and the episode above walks the whole thing end to end. All figures and screens shown are illustrative.