Make a decision vs. take a decision: A subtle difference in meaning

Examples of Make a Decision vs Take a Decision for Project Managers

You are in a board meeting. The project director says: "We need to take a decision on this today." Your stakeholder says: "We're still making a decision." Both are correct English, but they mean something different, and as a project manager, getting this distinction right signals a level of precision that native speakers notice.

Understanding the difference between make a decision and take a decision is one of those precision distinctions that separates proficient English from authoritative English, especially in formal professional environments where the wrong phrase signals uncertainty rather than control.

Woman pondering two options; making a decision

When it comes to making decisions, there are two common phrases in English:

Make a decision vs. take a decision

While they may seem interchangeable, there is actually a subtle difference in meaning between the two.

Making a decision

The phrase “make a decision” is the more common and informal of the two.

It can refer to the actual moment where a course of action is chosen, but it can also sometimes refer to the whole process leading up to it. This includes research, discussion, and thinking about the different options.

For example, a project manager might say, “We're still making a decision about whether to use waterfall or agile methodology for this project.” This means that the project team is still in the process of gathering information and thinking about the different options.

In everyday professional communication, make a decision is the more common and flexible of the two phrases; appropriate for team discussions, planning conversations, and any context where the process of deciding is still underway.

Taking a decision

Take a decision, by contrast, carries a formality and finality that make a decision does not. In board meetings, governance documents, and executive communications, take a decision signals that the matter is resolved and consequential — which is precisely when project managers need to get it right.

For example, a project manager might say, “The project board took the decision to extend the project deadline by two weeks.” This means that the project board made a final decision to extend the deadline and that this decision will have consequences for the project schedule and budget.

When to use each phrase

This distinction matters more than it might seem. In formal stakeholder communications (board minutes, executive updates, project governance documents) "take a decision" signals that something is final, consequential, and not open for further discussion. Using "make a decision" in that context can accidentally suggest the matter is still open. In high-stakes professional English, precision is credibility.

For example, if a project manager says that they are “making a decision” about a particular issue, this suggests that they are still gathering information and considering options. This is different from saying that they are “taking a decision,” which suggests that they have already made a final decision and that there is no going back.

In general, you should use the phrase “make a decision” when you are talking about the decision-making process, or when the consequences of the decision are not serious.

You should use the phrase “take a decision” when you are talking about a formal decision that has serious consequences.

Here are some examples of how to use each phrase correctly:

Make a decision:

• “The project team is still making a decision about how to handle the unexpected technical challenge.”

• “The project manager made a decision to hold a weekly status meeting to keep everyone informed of the project's progress.”

• “The stakeholders made a decision to approve the project budget.”

Take a decision:

• The project board took the decision to cancel the project due to unforeseen circumstances.

• The project manager took the decision to reassign the team member who was struggling to meet their deadlines.

• The customer took the decision to change the scope of the project, which had a significant impact on the project schedule and budget.

Here are some specific examples of how project managers can use this knowledge to their advantage:

• When discussing a potential problem with the project team, the project manager can say, “We're still making a decision about how to handle this issue.” This shows the project team that the project manager is still gathering information and considering options and that they will not make a decision until they are confident that it is the best course of action.

• When communicating with stakeholders about a change to the project plan, the project manager can say, “We had to take the decision to extend the deadline because of unforeseen circumstances.” This shows the stakeholders that the project manager had no choice but to make this decision, and that they are doing everything they can to minimize the impact on the project.

By understanding the subtle difference between “make a decision” and “take a decision,” project managers can use these phrases more effectively to communicate with stakeholders and team members, build trust and credibility, and manage expectations.

The difference between "make a decision" and "take a decision" is small, but in professional English, small differences carry weight, especially in formal communications, governance meetings, and stakeholder relationships where every word signals how much you understand the context you're operating in.

If you want more of this kind of precision (the language distinctions that native speakers notice but rarely explain) the free guide below is a good starting point.

→ Download: 5 Communication Strategies That Make You Sound Like a Leader