Explaining a Plan in English: Sequence Your Ideas With Prison Break
You know every step of your plan. Unfortunately, the person listening to you does not live inside your head. So you start explaining: first a detail, then a reason, then something that happens later, then you remember step one again. Ten sentences later, the listener asks the painful question: “So… what are we actually doing?”
The fix is not more vocabulary. It is sequence. A clear plan usually needs a visible spine: Setup → Next move → Decision point → Commitment or outcome. Once the listener can see those four pieces, extra detail becomes useful instead of chaotic.
Setup: What is the situation or goal?
Next move: What happens first or next?
Decision point: What needs to be checked, chosen, or reconsidered?
Commitment/outcome: What will you do once the decision is made?
1. Start with the plan, not the backstory
A weak explanation often begins with everything that happened before the plan. A stronger one gives the listener the destination first.
Information dump: “So I checked the train, and yesterday the hotel emailed me, and my sister might come, but I’m not sure because she has work, and the train is cheaper after six…”
Clear version: “The plan is to leave after work, take the evening train, and check in around nine. I just need to confirm whether my sister is joining us.”
Notice the difference: the clear version gives the route through the information. The listener knows the goal, the order, and the unresolved point.
2. Use short time anchors to make the order visible
You do not need academic connectors such as subsequently or thereafter. In conversation, short anchors usually work better:
| Job | Useful language |
|---|---|
| Open the sequence | First, to start with, the plan is… |
| Move forward | Then, after that, once that’s done… |
| Add a condition | If that works, if not, depending on… |
| Delay a choice | Before we decide, let’s check… |
| Finish | Then we can go ahead, so that’s the plan. |
Writer-original example: “First, I’ll send the draft. Then you can check the numbers. Once that’s done, we’ll decide whether to publish on Thursday or Friday.”
3. Give decisions their own sentence
Plans become hard to follow when actions and decisions are mixed together. If something is not decided yet, say so clearly instead of pretending the whole plan is fixed.
Mull it over. Come find me when you're ready to talk.
Mull it over means think carefully before deciding. It is useful because good plan explanations do not hide uncertainty. They mark it.
Writer-original repair: Instead of “We’ll probably launch Tuesday unless the design isn’t finished and maybe Wednesday would be safer,” say: “Tuesday is our first option. Let’s check the final design tomorrow, then make the call.”
4. Separate waiting from doing
Sometimes one person cannot move until another step is finished. Say that explicitly. Otherwise the listener may think they should act immediately.
Sit tight. Put direct pressure on that. I'll be back in a sec.
Sit tight is informal and means wait where you are. The transferable lesson is bigger than the idiom: tell people when the next step is “wait,” not “do.”
Casual: “Sit tight for a minute; I need to check the file.”
Professional: “Give me a minute to check the file, then we can continue.”
5. Make the decision point obvious
A plan usually has a moment where talking stops and action starts. In the episode, one line uses a very informal metaphor for that:
We have time. We don't, actually. At some point we gotta pull the trigger on this thing.
Here, pull the trigger means finally commit to a decision or action. It is common informal metaphorical language, but it is not ideal for every professional or international context because the literal gun image is strong.
For work, safer alternatives are: make the final decision, go ahead, commit to it, or move forward.
Casual: “We need to pull the trigger by Friday.”
Neutral: “We need to make the final decision by Friday.”
Professional: “We need to confirm the final option by Friday so implementation can start Monday.”
6. If the plan is wobbling, say why
Changing your mind is not the problem. Making the listener guess that you are changing your mind is the problem.
Are you putting this off? Are you having second thoughts? No.
Having second thoughts means beginning to doubt or reconsider a decision. In a plan explanation, this is useful for marking a decision that has become unstable.
Writer-original example: “I’m having second thoughts about booking the early flight because the connection is only forty minutes. I’m going to compare the later option before we pay.”
That is much clearer than giving five reasons and never saying the real message: I am reconsidering the choice.
7. Coordination needs ownership: who does what?
Sequence alone is not enough. Every important step should have an owner.
So, how do we play this? You hook me up with a few weeks' supply? Nice try.
Hook me up is informal language for providing or arranging access to something. You do not need to copy the slang. Copy the planning principle: name the person responsible for the next dependency.
Writer-original work example: “I’ll finish the copy. Marta will send the images. Once I have both, I’ll build the page and send you the preview.”
That one sentence is easy to follow because responsibility and sequence are visible together.
8. Show whether everyone is included
Plans often fail because people discuss the steps without saying whether the necessary people have actually agreed.
We're all clear on the Burrows execution, except for one thing. Bishop McMorrow is not in the fold.
In the fold means included in or aligned with a group or plan. It is idiomatic, but the planning lesson is universal: distinguish people who know the plan from people who have agreed to it.
Writer-original version: “The product team is ready, but finance hasn’t approved the budget yet. Once they do, we can start.”
9. Put the reason after the step—not five sentences before it
A simple rule makes explanations much easier to process:
“We’ll leave at six because traffic gets worse after seven.”
“I’ll send the draft today so that you can review it tomorrow.”
“Let’s wait until Monday because we still need the test results.”
Avoid burying the action under a mountain of context. The listener should hear what happens before they hear every reason why.
10. The 20-second plan formula
When you need to explain a plan quickly, use this template:
Goal: “The plan is to ___.”
First move: “First, we’ll ___.”
Next: “Then/Once that’s done, ___.”
Decision: “Before we ___, we need to decide/check ___.”
Finish: “If that works, we’ll ___.”
Writer-original travel example: “The plan is to reach the airport by four. First, we’ll leave the hotel at three. Once we’re there, I’ll check the bags while you return the rental car. Before we go through security, we need to confirm the gate. If everything is on time, we’ll grab food after that.”
Practice: repair a scrambled plan
Put these ideas into a clear order before opening the answer:
- The team may need another day if the test fails.
- You will run the test on Tuesday morning.
- The goal is to send the client the final version Wednesday.
- If the test passes, design will export the final files Tuesday afternoon.
Show one clear version
Writer-original model: “The goal is to send the client the final version on Wednesday. First, we’ll run the test Tuesday morning. If it passes, design will export the final files that afternoon. If it fails, we’ll need another day and I’ll update the client immediately.”
Practice: delete the unnecessary explanation
Imagine a colleague asks, “What’s the plan for tomorrow?”
“Well, I was thinking about it yesterday because last time we started too late, and then Alex said the supplier might call at ten, although I’m not sure whether he meant ten our time or their time…”
Show a cleaner version
Writer-original model: “We’ll start at nine. First, I’ll confirm the supplier call. Then Alex will prepare the order. If the supplier changes the delivery time, we’ll adjust the afternoon schedule.”
The cleaner version is not less intelligent. It simply respects the listener’s working memory: goal first, steps second, exceptions third.
Use the show as a sequencing workout, not a script to memorize
When a scene contains planning or negotiation, pause before the next line and predict the function, not the exact words: Is the speaker setting up the goal, asking someone to wait, reconsidering, assigning a task, or committing to action?
That is where FunFluen can help: with subtitle context and speaking/guess-the-dialogue practice, you can pause, say your own next step aloud, then compare it with the character’s version. The useful question is not “Did I copy the line?” It is “Did I move the plan forward clearly?”
The rule to remember
A good plan explanation is not a timeline of everything you know. It is a map of what the listener needs next.
Give the goal. Move through the steps in order. Mark the decision point. Name who owns the next action. Then stop. If the listener wants the backstory, they can ask for it.
Explore more language-learning guides in FunFluen Learn.