Time Pressure in Projects: On Schedules and Leadership
Where things usually go well
Good project teams generally know exactly how to put together a schedule. They build in buffers, identify dependencies, and document risks. That’s usually not where the problem lies. It only arises when the first deviations become apparent and there’s no explicit determination of what that means for the plan as a whole. And that’s precisely where the pressure builds up that becomes palpable later in the project.
The first signs
In every project, things don’t always go as planned. A supplier delivers later than expected, a decision takes longer, or a dependency turns out to be less critical than previously assumed. That in itself isn’t a problem. What makes it problematic is that these signals rarely lead to a fundamental question: Is our schedule still accurate? Instead, people look for ways to catch up, thereby implicitly maintaining the original schedule, even though reality has already changed.
Why we keep going
That reflex is understandable. In projects, pressing ahead feels like the quickest option, while reassessing feels like a delay. No one wants to be the one holding up the process, especially when there’s pressure to make progress and meet deadlines. As a result, doubts are downplayed, assumptions aren’t re-evaluated, and risks are identified but not acted upon. The result is that the content and the decision-making gradually drift apart, without a clear moment when this is corrected.
What that means in practice
When a schedule isn’t actively recalibrated, it quietly shifts from a steering tool to a reference point. Teams continue to adhere to it, while at the same time having to compensate more and more for what is no longer accurate. This leads to additional coordination, corrective work, and inefficient decisions. It feels like acceleration, but in reality, it actually causes delays because problems must be resolved later and under greater pressure. As long as a schedule isn’t adjusted to reflect reality, there is no acceleration—only delay.
The tipping point in projects
The real difference lies in the moment when someone decides that the plan needs to be revisited—not because the project is going off track, but because the underlying assumptions are no longer valid. That moment is often missed because no one is explicitly responsible for it. Signs are there, but the ownership needed to turn them into decisions is missing. And precisely because of that, a project continues longer in a direction that is actually already under pressure.
This is where leadership begins
What’s at play here isn’t a lack of knowledge or structure, but a matter of leadership. Not in the sense of hierarchy, but in taking responsibility for what’s visible. It requires someone to initiate a conversation when things get rocky, to challenge assumptions, and to have the courage to point out that a plan is no longer viable. Not to slow things down, but to prevent a project from having to catch up later on issues that weren’t resolved earlier.
Who will take ownership?
In many projects, it is assumed that this responsibility naturally falls to the project manager. In practice, however, this is precisely where a gray area arises. The project manager focuses on progress, specialists identify the substantive risks, and management looks at the bigger picture. Everyone sees a part of the picture, but no one explicitly takes responsibility for re-evaluating the plan. As long as that ownership isn’t clear, warning signs linger in the project, and course corrections only happen once the pressure has already mounted.
How organizations can use this
If leadership in projects revolves around continuously testing reality against the facts, then this also has implications for how an organization structures its projects. Not only in terms of structure, but especially in terms of what is explicitly defined. It helps when it is clear who is responsible for monitoring the feasibility of a schedule, separate from day-to-day progress. In addition, it requires moments when reassessment is routine, not just when delays have already occurred. In organizations where this is well-structured, risks and deviations actually influence decisions, and a schedule is actively updated when assumptions change. As a result, projects remain more manageable, and acceleration occurs not by working harder, but by preventing waste in a timely manner.
Where Ditio connects
Precisely because this sense of ownership isn’t explicitly established in many projects, Ditio is often brought in to restore that focus. Not only by setting up schedules and introducing structure, but above all by ensuring that these remain aligned with what is happening in practice. Ditio professionals highlight where assumptions are under pressure and immediately translate that into what it means for the schedule and the decisions that need to be made. As a result, a project does not get bogged down in making adjustments after the fact, but action is taken in a timely manner, thereby preventing delays and remedial work.
Early intervention pays off
In many projects, the problem isn’t how planning is done, but what happens once reality starts to deviate from the plan. Those who continue working at that point without making adjustments create unnecessary corrective work and pressure later in the project. Those who intervene earlier keep the project manageable and prevent delays from piling up.
So take a critical look at how your project handles these kinds of situations and who actually takes responsibility for them.
There is often more to be gained from that than from tightening up the schedule itself.