The Parallax of Progress: How Hierarchy Warps Project Timelines

In project management, timelines often create misunderstandings across different levels of management. Teams on the ground, working on the project, see every task’s minute details, while senior leaders perceive the project’s start and end as closer together. Why the disconnect? It’s a matter of perspective.

To understand it better, hold your finger an inch from your nose and look at it with one eye, then the other. The finger’s apparent jump is called parallax. It’s how an object’s position shifts based on your viewpoint. For individual contributors (ICs) and first-level managers, the project feels long, and every task requires time and energy. But for leaders, two or more steps removed from the details, the timeline looks shorter. It’s like looking at an airplane high above: it seems to barely move but is extremely fast.

Inner workings

Picture two people looking at a car. The first person is standing right next to it, the second one is looking at it from the top of a skyscraper. Distance changes perception. For the latter, the car looks like a toy.

Now imagine a project from start to finish, with an estimated length of $l$ days. The farther an observer is, the more compressed the timeline seems. A first-level manager, at distance $d$ , has a perception of the project duration similar to the person standing next to the car.

Parallax is the angle. Specifically, the apparent shift in an object’s position when viewed from two perspectives. Here, it’s about the estimated start and end dates of a project. We can calculate the shift with:

$\theta = \arctan \left( {\cfrac{l}{2d}} \right)$

Figure 1. Parallax of an observer near an object.

Another manager, farther away at $d'$ , perceives the project as shorter, similar to the observer atop the skyscraper. The project length remains the same, only the perception changes. The parallax for this manager is calculated the same way:

$\alpha = \arctan \left( {\cfrac{l}{2d'}} \right)$

Figure 2. Parallax of an observer far from an object.

As we can see from the images, $d' > d$ and $\alpha < \theta$ . The higher the manager, the smaller the parallax, the shorter the project appears.

Bridging the gap

This misalignment creates challenges, especially for project managers. Leaders, impressed by a demo, may push to ship sooner, thinking the finish line is in sight. Meanwhile, ICs, focused on the remaining tasks, may overestimate the work needed. Are all those steps essential? Sometimes, a product can launch when good enough, like a Minimum Viable Product (MVP) to test the market. And yes, it’s tricky to balance speed, features, and quality.

Aligning those views requires clear communication. But rather than a technical report that will drown readers in details, likely unread, focus on sharing the essentials, so everyone understands the project clearly:

Key milestones to map progress
Effort needed for each step
Short-term challenges or blockers

Note: Bringing minute details of the project to your manager may come across as if you’re unable to do your job and are offloading responsibility onto them.

The understanding gap is closed when the information you share brings clarity, enabling better conditions for good decision-making.