Pursue Decisions

WHY

Operations run on repetition. Projects do not.

Operations reward compliance. Projects demand judgment.

In operations, tasks are predefined, paths are known, and decisions have largely been made upstream. Execution is the job. In projects, the opposite is true. The path does not exist yet. It is created through decisions, one after another, under uncertainty. Every meaningful project action is preceded by a decision, whether acknowledged or not.

This is why projects do not stall due to lack of effort. They stall due to lack of decisions.

Project teams are often busy, sometimes exhausted, yet strangely immobile. Tasks are “in progress,” meetings are happening, emails are flowing, but nothing decisive moves forward. This is not a workload problem. It is a decision problem. Activity without decisions is motion without direction.

Every project contains hundreds of decisions. Some are technical, some commercial, some organizational, some political. Some are small, some irreversible. Each decision unlocks multiple downstream actions. Conversely, a single pending decision can silently block dozens of tasks across teams. The longer it remains unresolved, the more damage it causes.

Decision absence is more dangerous than wrong decisions. A wrong decision at least creates movement, information, and learning. Indecision creates stagnation, parallel assumptions, rework, and conflict. While teams wait, they hedge. They keep options open. They partially execute multiple paths. Resources get consumed without commitment. Progress becomes an illusion.

Time is the only resource that cannot be replenished. Every day a decision is delayed, cost accumulates, options shrink, and pressure increases. What could have been a calm, controlled choice slowly turns into a forced, reactive one. Decision latency compounds silently, and by the time it becomes visible, the project is already on the back foot.

Decisions bring clarity. Clarity brings alignment. Alignment converts effort into progress.

Without decisions, teams pull in different directions while believing they are aligned. Energy is spent maintaining ambiguity instead of advancing outcomes. Conflicts arise not because people disagree, but because no one has closed the question.

Unresolved decisions are breeding grounds for conflict. When direction is unclear, individuals fill the vacuum with personal judgment. Convictions harden. Positions form. What began as a technical choice escalates into ego, authority, and territory. Fast, explicit decisions prevent this decay and preserve team harmony.

Projects do not need perfect decisions. They need timely ones. In most cases, making two fast decisions, the first imperfect and the second corrective, is far superior to waiting for certainty that never arrives. Decisions generate information. Information improves judgment. This feedback loop is the engine of agile execution.

Decisions also establish leadership. When decisions are made and pursued, roles become clear, ownership becomes visible, and accountability sharpens. Teams gain confidence when they see direction backed by conviction. Indecision may feel safe in the moment, but it quietly erodes trust and morale.

Pursuing decisions is not about authority. It is about responsibility. Stakeholders are human. They hesitate, defer, avoid conflict, or get distracted by competing priorities. Projects do not move just because decisions are assigned. They move when someone ensures those decisions are made.

Innovation also depends on decisiveness. Projects rarely have the luxury of perfect information or generous buffers. When decisions are pursued actively, teams feel safe to propose ideas, challenge assumptions, and take initiative. When decisions linger, risk-taking dies and mediocrity becomes the default.

Scope changes, too, demand decisive handling. While change often increases value, delayed acknowledgment and delayed decisions destroy it. The cost of change grows exponentially with time. What could have been a smart adjustment becomes a crisis because no one closed the loop early.

In the end, projects move at the speed of decisions. More decisions create more actions. Faster decisions create faster learning. The project that decides well does not just move faster. It moves correctly. If you want your project to progress, do not just manage tasks.

Pursue decisions. Relentlessly.

WHAT

So what exactly are the “decisions” you must pursue? Is there a checklist? Unfortunately, no. As in real life, the hardest part is not solving problems but identifying them correctly. In projects, progress is rarely blocked by lack of effort or competence; it is blocked by invisible, delayed, or avoided decisions. Your job is to learn to see them.

Decisions do not always announce themselves clearly. Some are explicit and visible, while many are silent, deferred, or disguised. The project manager’s real skill lies in detecting where decisions are missing, stalled, or being made by default.

Every stakeholder in a project holds decision authority, whether formally defined or informally exercised. A single pending decision by one stakeholder can hold up dozens of downstream tasks. Conversely, multiple teams may continue working while unknowingly waiting on one unresolved choice. Projects stall not because nobody is working, but because nobody is deciding. Therefore, you must continuously track who needs to decide what, by when, and what remains blocked until that decision is made.

It is critical to distinguish between decision absence and decision latency. Decision absence is when no one has even acknowledged that a decision is required. Decision latency is when everyone agrees a decision is needed, but it keeps getting deferred. Latency is often more dangerous than absence because it creates the illusion of progress while quietly consuming time, slack, and patience. Most projects bleed to death through decision latency, not dramatic failure.

Many of the most damaging decisions in projects are silent decisions, made through inaction. When no one decides, the project still moves forward, but along the path of least resistance. Defaults get locked in, assumptions harden into reality, and options quietly disappear. Later, these outcomes are treated as given rather than choices that were never consciously made. As a project manager, you must surface these silent decisions before they fossilize.

Another common trap is decisions masquerading as tasks. Statements like “Let’s explore options,” “Do a study,” or “Prepare a proposal” often hide an unresolved decision behind activity. Work gets generated, documents get produced, but the actual choice remains untouched. Activity increases, clarity does not. When you see effort without convergence, pause and ask: What decision is this work supposed to enable? Until that is answered, the project is only burning time.

Projects also suffer from decisions trapped in alignment loops. Stakeholders repeatedly ask for more inputs, more validation, or more consensus, not because clarity is lacking, but because commitment is uncomfortable. Alignment becomes an excuse for postponement. While some alignment is necessary, endless alignment is a symptom of decision avoidance. Your responsibility is to recognize when discussion has crossed the threshold from useful to evasive and to push for closure.

A particularly dangerous category is decisions nobody feels authorized to make. These decisions sit in limbo because they fall between roles, functions, or hierarchies. Everyone sees the need, but no one claims ownership. Meanwhile, teams continue to work around the issue, accumulating technical debt, workarounds, or compromises. Such decisions must be deliberately escalated, reframed, or reassigned. Unclear authority is deeply damaging to projects.

Conflicts are another major decision sinkhole. Disagreements persist not because solutions are unavailable, but because stakeholders cannot agree on which path to choose. In such cases, the decision itself becomes the bottleneck. The longer conflicts remain unresolved, the more they spill into relationships, morale, and execution quality. Tracking conflicts without tracking the decisions required to resolve them is ineffective. Every unresolved conflict implies at least one missing decision.

Certain decisions are also more consequential than others. Changes affecting scope, architecture, schedule logic, or cost structure are significantly harder to reverse than cosmetic or local changes. These high-impact decisions must be identified early and pursued aggressively. Delaying them pushes the project into a corner where options shrink and consequences multiply.

Finally, beware of decisions intentionally pushed to the back-burner. While deferral may occasionally be pragmatic, most deferred decisions eventually return with greater urgency, reduced options, and higher cost. What could have been decided calmly becomes a crisis decision under pressure. As a default rule, if a decision does not benefit from waiting, it should not wait.

In essence, decisions exist wherever progress pauses, ambiguity persists, or effort fails to convert into outcomes. Your task is not merely to record decisions once made, but to actively hunt for the ones missing. Seeing decisions clearly, early, and relentlessly is what keeps projects moving forward.

HOW

Knowing why decisions matter and where they hide is still insufficient unless you develop the discipline to pursue them relentlessly. In real projects, decisions do not get made simply because they are needed. They get made because someone applies sustained pressure, clarity, and structure. That someone is usually the project manager.

First, redefine what meetings are for. Meetings are not for discussion; they are for decisions. Discussion is only a means to that end. If a meeting does not aim to close at least one decision, it is a distraction. Agendas should state clearly what decisions are expected by the end of the meeting, not just what topics will be talked about. Require participants to arrive prepared, with positions and constraints thought through. Unprepared discussion is a form of delay.

Treat the project like a continuous flow of work items moving between people. Every work item pauses at decision points. When a person receives a “ball,” whether a task, query, or issue, something must happen before it moves forward. As a project manager, your job is to keep the balls moving. The moment someone holds onto one too long, intervene. Silence is not progress.

Maintain a dedicated decision tracker, separate from task lists. Tasks can often proceed partially without decisions; decisions cannot. In reviews, always address pending decisions before reviewing task status. A project with completed tasks but pending decisions is stalled, not healthy. Escalate decision delays early, even at the risk of discomfort. Harmony that delays progress is not harmony; it is avoidance.

When pursuing a decision, frame it in terms the stakeholder cares about. Do not argue that a decision is “important for the project.” That is meaningless. Explain what happens if the decision is made today, and what is lost if it is delayed. Add an explicit “if not decided by” consequence. Decision-makers act faster when the cost of inaction is made visible.

Never pursue a decision without presenting options. Decisions stall when stakeholders are asked to choose between vague directions or undefined outcomes. Present two or three concrete paths, each with clear implications on scope, time, cost, risk, and reversibility. You are not deciding for them; you are enabling them to decide responsibly.

When decisions circulate endlessly for alignment, recognize the pattern and interrupt it. Ask directly: What information is still missing to decide? Who needs to be comfortable? By when will this be closed? If answers are vague, force specificity. Alignment without closure is wasted motion.

Escalate without emotion. Escalation is not complaint; it is responsibility. When escalating, always carry context, impact, and options. An escalation without options signals helplessness. An escalation with options signals leadership. Stakeholders are far more willing to decide when they feel supported rather than cornered.

Follow up relentlessly. One follow-up is politeness. Multiple follow-ups are seriousness. Do not apologize for reminding people of pending decisions. Your persistence is not harassment; it is the mechanism that keeps the project alive. Bureaucracy, hierarchy, ego, and inertia are obstacles to be worked around, not excuses to stop.

Make pending and upcoming decisions highly visible in project updates. Balance reports between past progress, present risks, and future decisions. Explicitly list what decisions are needed, from whom, and by when. However, never rely on reports alone. If a decision matters, pursue it in person or directly, not through documents.

Build human relationships deliberately. People decide faster for people they trust. Invest time in understanding stakeholder pressures, constraints, and personal contexts. This is not manipulation; it is realism. Projects are human systems, not mechanical ones. Strong relationships convert pursuit into cooperation.

Finally, accept this truth: pursuing decisions will sometimes make you unpopular. That is the price of leadership. Projects do not fail because decisions were pushed too hard; they fail because they were not pushed at all. If you consistently pursue decisions with clarity, respect, and persistence, the project will move. Without that, everything else is noise.

Decisions create motion. Motion creates progress. Progress creates confidence. Pursue decisions.