Recognize, Reflect, Revise: What to Do When Things Don’t Go According to Plan

Something didn’t go according to plan.

Now what?

That sounds like a simple question, but it’s one of the most important questions we can ask in business, leadership, marketing, client work, project management, and really, life in general.

Because things go wrong.

Campaigns don’t produce leads. Projects go over budget. Customers aren’t happy. A strategy that looked smart on paper falls flat in the real world. A decision that seemed obvious at the time turns out to be the wrong one. A hire doesn’t work out. A timeline slips. A product launch misses the mark. A website redesign doesn’t convert the way we expected. A sales process that worked last year suddenly stops working.

The question is not whether something will go wrong.

The question is what we do next.

I’ve heard this described as going into the general’s tent, and I think that’s a great image.

Picture a battle. Things are happening fast. There’s noise, pressure, emotion, urgency, confusion, and incomplete information. Decisions are being made in real time. Some of them work. Some of them don’t. At some point, you have to step away from the chaos long enough to understand what just happened.

That’s the general’s tent.

It’s not where you go to hide. It’s not where you go to blame people. It’s not where you go to rewrite history so you can feel better about yourself. It’s where you go to get clear.

You step away from the battle for a moment so you can recognize what happened, reflect on what it means, and revise your plan before stepping back outside.

Recognize. Reflect. Revise.

That’s the process.

It’s simple, but it’s not always easy. In fact, it’s often hardest when we need it most, because when something goes wrong, the natural response is usually emotional. We get frustrated. We get defensive. We get embarrassed. We get anxious. We look for someone to blame. Or we beat ourselves up and tell ourselves we should have known better.

But none of that helps very much.

If the goal is to make a better next decision, then we need a process that gets us out of reaction mode and back into learning mode.

That starts with recognizing what actually happened.

Not what we hoped would happen.

Not what we intended to happen.

Not what we wish had happened.

Not whose fault it was.

What actually happened?

That distinction matters.

When something doesn’t go according to plan, it’s very tempting to immediately jump into explanation. Before we’ve even clearly defined the problem, we’re already telling a story about it.

“The client didn’t understand.”

“The market is bad.”

“The team dropped the ball.”

“The timing was wrong.”

“The platform changed.”

“The customer was unreasonable.”

“The budget was too small.”

“The campaign just needed more time.”

Some of those things might be true. But if we start there, we skip over the most important first step, which is simply recognizing reality.

What happened?

The campaign didn’t produce leads.

The project went over budget.

The customer wasn’t happy.

The launch was delayed.

The proposal didn’t close.

The email sequence had a lower response rate than expected.

The new process created more confusion instead of less.

The decision didn’t work.

That’s it. Start there.

The reason this is so important is that we can’t improve what we haven’t honestly acknowledged. If we soften the truth too much, we don’t learn from it. If we exaggerate the truth, we don’t learn from it either. We need to get as close as we can to the facts.

For example, there’s a big difference between saying, “That campaign was a total failure,” and saying, “That campaign generated 900 visits, 32 form submissions, and 2 qualified leads, when we were expecting closer to 15 qualified leads.”

The first statement is emotional. The second statement gives us something to work with.

There’s also a big difference between saying, “The customer hated everything,” and saying, “The customer was unhappy because the final deliverable didn’t include two items they believed were part of the scope.”

Again, now we have something we can examine.

Recognizing what happened is not about being cold or robotic. It’s about giving ourselves the best chance of learning something useful. If we stay vague, we stay stuck. If we get specific, we can start to see what needs to change.

This is especially important when there are people involved, because people bring emotion, personality, expectations, pressure, and history into the situation. When a project goes badly, it’s easy for the conversation to become about who messed up. But blame usually shuts down learning.

That doesn’t mean accountability doesn’t matter. It does. If someone made a commitment and didn’t follow through, that matters. If I made a bad call, that matters. If a team member missed something important, that matters. But accountability works best when it’s connected to reality, not emotion.

What happened?

What was expected?

What was delivered?

Where did the gap appear?

What was the consequence?

If we can answer those questions honestly, we’re already in a better position than we were when we were just reacting.

Once we recognize what happened, then we can reflect.

This is where the real learning starts.

Why did it happen?

What did I know when I made the decision?

What did I not know?

What assumptions did I make?

Which assumptions turned out to be wrong?

What signals did I miss?

What did I learn that I didn’t know before?

This is also where a lot of people get stuck, because reflection can feel uncomfortable. It requires us to look directly at the gap between what we thought would happen and what actually happened.

There are usually two unhelpful directions we can go.

One is beating ourselves up.

“I should have known better.”

“That was stupid.”

“I can’t believe I made that decision.”

“I always do this.”

“I’m terrible at this.”

That might feel like accountability, but it usually isn’t. It’s just punishment. And punishment doesn’t necessarily produce better thinking. In fact, it often makes us more afraid to make decisions in the future.

The other unhelpful direction is defending the original decision no matter what.

“Well, it would have worked if…”

“The idea was still good.”

“We couldn’t have known.”

“They didn’t do their part.”

“That’s just how it goes.”

Sometimes those statements are partly true. But if the goal is to protect our ego, we’re probably not learning much.

The useful question is not, “How do I prove I wasn’t wrong?”

The useful question is, “What did this teach me?”

That one question changes the whole conversation.

It shifts us from defense to curiosity. It moves us out of shame and into improvement. It lets us look at a mistake without becoming the mistake.

Because a decision can be wrong without making us useless. A strategy can fail without making us failures. A project can go sideways without meaning the whole team is incompetent. Something can go badly and still become valuable if we learn from it.

Reflection is where we separate a bad outcome from a useful lesson.

Let’s say a marketing campaign didn’t produce the leads we expected. Reflection might reveal that the offer wasn’t clear, or the audience was too broad, or the landing page created friction, or we were measuring the wrong thing, or we didn’t give the campaign enough time, or the traffic source wasn’t aligned with the buyer.

But we don’t know that until we reflect.

If we simply say, “That didn’t work,” and move on, we may repeat the same mistake in a different form. If we say, “Marketing doesn’t work,” we learn the wrong lesson entirely. If we blame the platform, the economy, the audience, or the algorithm without looking deeper, we may miss the part we could have improved.

Reflection asks for more honesty than that.

What did I believe would happen?

Why did I believe that?

Was that belief based on evidence, experience, hope, pressure, habit, or someone else’s opinion?

Did I have enough information?

Did I ask the right questions?

Did I ignore any warnings?

Did I confuse activity with progress?

Did I define success clearly before starting?

Did everyone involved have the same expectations?

Did the plan depend on something we didn’t control?

Those are not always comfortable questions, but they’re useful.

And the point is not to become overly cautious. The point is to become smarter.

There’s a danger in learning the wrong lesson from a mistake. If one campaign fails, the lesson may not be, “Never run campaigns like that.” It might be, “Don’t launch without a clear offer.” If one client relationship becomes difficult, the lesson may not be, “Clients are impossible.” It might be, “We need a better onboarding process and clearer scope.” If one decision leads to a bad outcome, the lesson may not be, “Don’t trust your judgment.” It might be, “Get better information before making that kind of call.”

Reflection helps us find the real lesson instead of the easy lesson.

And that matters because the easy lesson is often too broad.

“We tried that once. It didn’t work.”

That sentence can be dangerous.

What exactly did we try?

Under what conditions?

With what budget?

With what timing?

With what team?

With what message?

With what expectations?

For how long?

Measured how?

If we don’t reflect, we may throw away a good idea because of poor execution. Or we may keep repeating a bad idea because it once almost worked. Reflection helps us tell the difference.

It also helps us be fair to our past selves.

That may sound strange, but it’s important. When we look back on a decision with new information, it’s easy to judge the old decision too harshly. But the real question is not, “Does this decision look good now that I know everything that happened afterward?”

The better question is, “Given what I knew at the time, was this a reasonable decision?”

Sometimes the answer is yes.

Sometimes the outcome was bad, but the decision was reasonable based on the information available. That still gives us something to learn, but it doesn’t mean we were foolish.

Other times, if we’re honest, the answer is no.

We rushed. We assumed. We ignored something. We let pressure drive the decision. We didn’t ask enough questions. We wanted a certain outcome so badly that we treated hope like evidence.

That’s useful too.

The goal is not to perfectly judge ourselves. The goal is to understand the decision-making process so we can improve it.

After we recognize what happened and reflect on what it means, then we revise.

This is the step that turns learning into action.

What changes now?

Not in theory. Not someday. Not as a vague intention.

What changes now?

Maybe the strategy changes.

Maybe the process changes.

Maybe the timeline changes.

Maybe the budget changes.

Maybe the offer changes.

Maybe the communication changes.

Maybe the expectations change.

Maybe the checklist changes.

Maybe the approval process changes.

Maybe we need better information before making the next decision.

Maybe we need to stop doing something.

Maybe we need to start doing something.

Maybe we need to keep the same goal but take a different route.

Revision is where we decide what we’re going to do differently when we step back outside the general’s tent.

This is where a lot of lessons get lost. People will say, “We learned a lot from that,” but nothing changes. Same process. Same assumptions. Same communication gaps. Same rushed decisions. Same vague expectations. Same preventable problems.

That’s not learning. That’s just remembering pain.

A lesson isn’t complete until it changes behavior.

If a project went over budget because the scope wasn’t clear, revision might mean adding a more detailed discovery process before quoting. It might mean documenting assumptions. It might mean creating change-order language. It might mean having a hard conversation earlier instead of trying to be flexible until it becomes a problem.

If a customer wasn’t happy because expectations weren’t aligned, revision might mean improving onboarding, confirming deliverables in writing, setting clearer milestones, or creating a better review process.

If a campaign failed because the audience was too broad, revision might mean narrowing the target, changing the offer, testing messaging before launch, or improving tracking so we can see where the drop-off happens.

If a decision failed because it was made too quickly, revision might mean building in a pause before committing, asking one more person for perspective, or defining what information is required before making similar decisions in the future.

The revision doesn’t always have to be huge. In fact, some of the best revisions are small. A better question at the beginning of a project. A clearer checklist. A five-minute review before launch. A more specific success metric. A simple written confirmation. A habit of asking, “What are we assuming here?”

Small revisions can prevent big problems.

But the revision does have to be real.

That’s the difference between insight and improvement.

Insight says, “Now I understand what happened.”

Improvement says, “Here’s what I’m changing because of it.”

This process matters because mistakes by themselves do not automatically make us better.

There’s a saying that experience is the best teacher, but I don’t think that’s quite right. Experience can teach us, but only if we pay attention. Otherwise, experience can just make us repeat ourselves with more confidence.

Making a mistake doesn’t necessarily make the next decision better.

Learning from it does.

That distinction matters a lot.

Plenty of people have years of experience, but they haven’t necessarily revised their thinking. They’ve lived through the same type of problem many times, but they haven’t stopped long enough to recognize the pattern, reflect on the cause, and revise the approach.

So they keep running into the same wall.

Different customer, same problem.

Different project, same confusion.

Different campaign, same missing strategy.

Different team, same communication breakdown.

Different year, same frustration.

The general’s tent is how we interrupt that pattern.

It gives us a structured pause.

And in a world that rewards speed, the pause can feel inefficient. We want to move on. We want to fix it fast. We want to get back to work. We want the discomfort to be over.

But the pause is not wasted time.

The pause is where better decisions are formed.

That doesn’t mean we need to turn every mistake into a weeklong analysis. Sometimes the whole process takes five minutes.

What happened?

Why?

What changes?

Done.

Other times, especially when the stakes are higher, we may need a more deliberate review. We may need to gather data, talk to people involved, look at communication, compare expectations, and examine the sequence of decisions that led to the outcome.

The scale can change, but the process is the same.

Recognize.

Reflect.

Revise.

One of the most useful things about this process is that it helps reduce drama. When something goes wrong and there’s no process, people often default to emotion. The conversation becomes scattered. Someone is upset. Someone is defensive. Someone is trying to move on too quickly. Someone is looking for a villain. Someone is rewriting the story.

But when there’s a process, the conversation has somewhere to go.

First, let’s recognize what happened.

Then, let’s reflect on why it happened.

Then, let’s revise what needs to change.

It creates a shared path forward.

That’s valuable whether you’re leading a team, working with clients, managing vendors, building a business, or just trying to make better decisions personally.

It also creates a healthier relationship with mistakes.

A lot of people say they want a culture where it’s okay to make mistakes. But that can be misunderstood. It doesn’t mean mistakes don’t matter. It doesn’t mean carelessness is acceptable. It doesn’t mean outcomes are irrelevant. It means mistakes are treated as information, not just ammunition.

There’s a big difference.

If mistakes are punished without examination, people hide them.

If mistakes are ignored without accountability, people repeat them.

But if mistakes are examined honestly and used to improve the system, people learn from them.

That’s the balance.

We don’t want to be reckless.

We also don’t want to be so afraid of mistakes that we stop making decisions.

Because decisions always involve uncertainty. If we wait until every outcome is guaranteed, we won’t do much of anything. Business doesn’t work that way. Leadership doesn’t work that way. Marketing doesn’t work that way. Life doesn’t work that way.

We make the best decision we can with the information we have. Then reality gives us feedback. Then we learn.

That feedback loop is powerful.

Plan.

Act.

Observe.

Learn.

Adjust.

Continue.

The general’s tent is basically the learning and adjustment part of that loop.

Without it, we just act and react. With it, we improve.

There’s also something humbling about this process. It reminds us that no matter how experienced we are, we will still be wrong sometimes. We will misread situations. We will make assumptions. We will overlook details. We will underestimate complexity. We will overestimate demand. We will think something is clear when it isn’t. We will believe we’ve communicated enough when we haven’t.

That’s not a reason to lose confidence.

It’s a reason to stay teachable.

Confidence and humility need to work together. Confidence helps us make decisions and take action. Humility helps us learn when the outcome tells us something we didn’t expect.

If we only have confidence, we become stubborn.

If we only have humility, we may become hesitant.

But together, they create better judgment.

I can make a decision.

I can also revise that decision when I learn more.

That’s not weakness. That’s wisdom.

One of the biggest traps after something goes wrong is tying our identity too closely to the original decision. Once we do that, changing course feels like admitting defeat. So instead of revising, we double down.

We keep funding the campaign because we don’t want to admit the message is wrong.

We keep pushing the project plan because we don’t want to admit the timeline was unrealistic.

We keep defending the decision because we don’t want to admit we missed something.

We keep trying to make the original idea work because we don’t want to face the fact that the facts have changed.

But revising is not the same as quitting.

Revision is what responsible people do when new information arrives.

Sometimes revising means staying the course with small adjustments. Sometimes it means changing direction completely. Sometimes it means stopping. Sometimes it means starting over. The point is not to protect the original plan. The point is to pursue the best next step based on what we now know.

That phrase is important: what we now know.

Because we know more after the mistake than we did before it.

The only question is whether we’re willing to use that information.

This process also helps prevent overcorrection.

When something goes wrong, we may be tempted to swing too far in the opposite direction. One client relationship goes badly, so we become rigid and suspicious with every future client. One marketing channel underperforms, so we abandon it completely. One employee misses a deadline, so we create a burdensome approval process that slows everyone down. One risk doesn’t pay off, so we stop taking risks.

That’s not always learning. Sometimes that’s just fear wearing a business suit.

Reflection and revision help us make a proportionate change.

What actually needs to change?

Is this a one-time exception or a pattern?

Was the issue strategy, execution, timing, communication, fit, resources, or expectations?

What adjustment would reduce the risk without creating a new problem?

Good revision is thoughtful. It doesn’t just react to pain. It responds to evidence.

That’s why the first two steps matter so much. If we don’t recognize clearly and reflect honestly, our revision may be wrong.

We solve the wrong problem.

And solving the wrong problem can create more frustration than the original mistake.

For example, if a campaign didn’t generate leads, we might assume the platform was the issue and move to another one. But if the real problem was the offer, the same issue follows us to the next platform. If a project went over budget, we might assume the team worked too slowly. But if the real problem was unclear scope, pushing everyone harder won’t fix it. If a customer was unhappy, we might assume they were difficult. But if the real problem was expectation-setting, we’ll encounter the same issue again later.

That’s why going into the general’s tent is not just about asking, “What are we going to do now?”

It’s about asking that question after we’ve taken the time to understand what actually happened.

Recognize.

Reflect.

Revise.

There’s a certain discipline to it.

And like most useful disciplines, it gets easier with practice.

At first, it may feel unnatural. Especially if your normal pattern is to react quickly, explain immediately, or move on without review. But over time, this process becomes a habit. Something goes wrong, and instead of spiraling, you know what to do.

Recognize the facts.

Reflect on the lesson.

Revise the approach.

Then get back out there.

That last part matters too.

The point of the general’s tent is not to stay in the tent forever.

Analysis has its own danger. We can reflect endlessly, review every detail, and become so focused on understanding what happened that we delay the next decision. That’s not the goal either.

The goal is to pause long enough to learn, then act.

Some people avoid reflection because they don’t want to feel the discomfort of the mistake. Other people hide inside reflection because they don’t want to face the uncertainty of the next step.

Neither one is ideal.

The process is complete when we return to action with a better plan.

That may mean having a conversation.

Sending the revised proposal.

Changing the campaign.

Updating the process.

Apologizing to the customer.

Adjusting the timeline.

Making the decision.

Trying again.

Whatever the next step is, we take it with more clarity than we had before.

This is how improvement actually happens. Not from pretending everything went well. Not from blaming everything on external forces. Not from beating ourselves up. Not from endlessly replaying the mistake.

Improvement happens when we turn experience into insight and insight into action.

Recognize what happened.

Reflect on what it taught you.

Revise what needs to change.

Then get back out there.

The next time something doesn’t go according to plan, it may feel like a setback. And maybe it is. But it can also be useful. It can reveal a weak spot in the strategy. It can expose a missing step in the process. It can show where communication broke down. It can challenge an assumption. It can point toward a better way.

Not automatically.

Only if we use it.

That’s the responsibility.

A mistake is not automatically wisdom. A failed campaign is not automatically a better campaign next time. A difficult project is not automatically a better process. A bad decision is not automatically better judgment.

The learning is the bridge.

And the bridge is built through recognition, reflection, and revision.

So when something goes wrong, don’t just react. Don’t just defend. Don’t just blame. Don’t just move on.

Step into the general’s tent.

Ask what actually happened.

Ask why it happened.

Ask what changes now.

Then step back outside and make the next decision with what you’ve learned.