#NotesApp
← All Journals

Productivity

Before Your Next Project Fails, Ask This One Question

20 November 2026  |  3 min read

Before Your Next Project Fails, Ask This One Question

Imagine your team is launching a new project next month.

Everyone is excited. The deadlines are set, responsibilities have been assigned, and the launch date is already on the calendar.

Naturally, the team starts asking:

"What do we need to do to make this project successful?"

Fair question.

But here's another question worth asking:

"Imagine it's one month later, and this project has completely failed. What went wrong?"

👀

Sounds a little dramatic, I know. 😂

But there's an actual project management technique behind this exercise. It's called a pre-mortem.

Unlike a post-mortem, which examines what went wrong after something has failed, a pre-mortem asks you to imagine failure before it happens.

The goal is simple: identify potential problems while there's still time to address them.

Let's put it into practice.

Imagine you're preparing to launch a new website.

You gather everyone involved and ask them to imagine that the launch was unsuccessful.

What could have happened?

Here are a few possibilities:

  • The client didn't approve the content on time.
  • The designer became unavailable halfway through the project.
  • Nobody allocated enough time for website testing.
  • An unexpected expense pushed the project over budget.
  • Important updates weren't communicated to the people who needed them.

Notice something?

None of these problems is particularly impossible or unusual.

They're the kinds of things that happen in everyday projects. Yet they can easily derail an otherwise promising plan.

So, what happens next?

You don't just write down the problems and move on.

For every risk identified:

1. Assign an owner.

Someone should be responsible for monitoring and addressing each potential problem.

2. Decide on a response.

If the designer becomes unavailable, is there a backup? If approval is delayed, what's the escalation process?

3. Identify early warning signs.

Don't wait until the deadline passes to realize something is wrong. Decide what signs might indicate that a problem is developing.

4. Take preventive action.

Build those solutions into the project plan before work gets underway.

Now, instead of simply hoping everything goes according to plan, your team has prepared for what could derail it.

Why I think more teams should use this technique

One of the biggest mistakes in project planning is assuming that because everyone understands the goal, everyone has considered the risks.

Those are two very different things.

A team can have a clear objective, a talented workforce, and a detailed timeline and still overlook something that eventually causes problems.

A pre-mortem creates room for people to raise concerns before those concerns become expensive mistakes.

And sometimes, the person who spots the biggest risk isn't the project manager or the team lead. It might be the person handling a small but critical part of the process.

Good planning isn't just about deciding what should happen. It's also about preparing for what could go wrong.

So, before your next project begins, try asking:

"If this project fails, what will probably be the reason?"

You might discover that preventing failure starts with a conversation most teams never think to have.

**Have you ever spotted a potential problem early enough to prevent it from becoming a bigger one? I'd love to hear about it.

Book a session with Precious Chinahuzo

Native calendar, no redirect — payment collects inline.

View calendar
👁 2 views

Comments