Why You Should Track Decisions Made

In early March, many organizations are deep into execution mode. Plans for the year are underway, projects are moving, and teams are working hard to follow through on priorities. But there is one type of work that often slips through the cracks because we don’t always recognize it as work.

Decision-making.

In business and in life, we frequently say things like, “I need to decide about that,” but we rarely treat the decision itself as a task that needs to be completed.

Instead, the decision sits in the background lingering on your mental to-do list and often getting revisited time and time again in meetings.

At Nimble Up, we see this all the time with leadership teams. Work stalls because a decision that unlocks the next step has not yet been formally made.

That is why I recommend tracking decisions made.

A Decision Is a Task

Many decisions require time, information, and perspective.

Some decisions involve financial investment.
Some carry risk.
Some affect other people or teams.
Some require research or outside input before you can move forward.

Because of this, a decision often requires real work before it can be made. That work might include:

  • Gathering additional data

  • Seeking input from stakeholders

  • Running scenarios

  • Evaluating tradeoffs

  • Clarifying desired outcomes

When we fail to treat decisions as tasks, we underestimate the effort required to make them well.

Personally, I track decisions intentionally in my planning systems. In my weekly planning and accountability groups, I mark decisions with a simple “D:” in front of the item. This signals that the task a decision point.

For example:

  • D: Select marketing platform for Q2 campaign

  • D: Approve budget for new hire

  • D: Choose vendor for website redesign

By labeling it this way, the decision becomes visible work. It gets the time and attention it deserves.

Why Tracking Decisions Matters

There are two parts to a decision.

  1. Making the decision

  2. Communicating the decision

Many teams struggle because the first part happens informally and the second part never happens clearly.

This is where a Decision Log or RID Log (Risks, Issues, Decisions) becomes incredibly valuable.

A Decision Log is simply a running record of the decisions that have been made. It typically includes the date, the decision itself, who made it, and sometimes a short note explaining why the decision was made or what the other options were that weren’t chosen. A RID Log expands on this by tracking Risks, Issues, and Decisions together, giving teams visibility into the factors that might influence future choices.

These logs serve two important purposes:

First, they clarify communication. Instead of relying on memory or hallway conversations, teams have a documented record of what was decided and when. When someone joins a project midstream or needs to understand the reasoning behind a direction, the answer is already captured.

Second, they help teams stop revisiting the same decisions over and over again.

If you have ever been in a meeting where the group starts circling back to something that was already resolved weeks ago, you know how frustrating that can be. Without documentation, it is easy for uncertainty to creep back in. People may wonder if the decision was final, whether circumstances changed, or whether someone important was left out of the conversation.

When the decision is recorded, the team can confidently say: “That decision was made on this date. Here is the outcome. Here is the context.”

This allows everyone to move forward.

A Simple Practice You Can Start This Week!

If you want to improve decision clarity inside your organization, start with a simple step.

Add a Decision Marker to your task system.

Whenever you encounter something that requires a decision, label it clearly. Treat it as a task with an owner and a timeline.

For example:

  • D: Finalize pricing model

  • D: Decide on conference sponsorship

  • D: Approve product launch timeline

Once the decision is made, record the outcome and communicate it to the people affected.

This small habit helps you and your team see where thinking work needs to happen. It will also prevent important decisions from drifting indefinitely and ensure that once a decision is made, everyone can move forward together!

Next
Next

Accountable vs. Responsible