Why Your Requirements Keep Changing (It Is Not Your Work. It Is the Clock.)

Picture this.

You finish a task in two days. You send it. Your manager looks at it for thirty seconds and says “looks good, just change the button color.”

Now picture the same task. You take five days. You send the exact same work. Suddenly there are three new stakeholders on the review call. Someone questions the entire approach. A business person you have never met in your life has “concerns.” A designer who was not part of the brief has feelings about the spacing. And the button color is now the least of your problems.

The work is identical. You are the same person. The output did not change.

But five days somehow created seventeen new opinions.

This is not a you problem. This is not even a manager problem. This is Parkinson’s Law showing up to your standup uninvited and eating all the snacks.

---

First, What Is Parkinson’s Law

In 1955, a British historian named C. Northcote Parkinson wrote a now-famous essay. His opening line was this:

“Work expands so as to fill the time available for its completion.”

He was writing about bureaucracy and being funny about it. But seventy years later, every person who has ever worked in a team, a startup, a corporation, or a group project in college knows he was also being terrifyingly accurate.

When you give people five days to review something, they will use five days to review it. They will think of new things. They will forward it to other people. Those other people will think of new things. By day four, someone who has never attended a single planning meeting will have three strong opinions about your work.

This is not malicious. This is just what human brains do when given idle time and something to look at.

---

The Numbers That Should Make Everyone Uncomfortable

This is where it stops being a funny observation and starts being a documented business disaster.

$2 trillion is lost globally every year due to failed or reworked projects. Not million. Trillion. With a T.

Source: Project Management Institute, 2023

40 to 50 percent of total project time is spent on rework on average. Not building. Not improving. Redoing things that were already done once.

Source: Keil et al., IEEE Software

70 percent of projects that fail cite poor or changing requirements as the primary reason for failure.

Source: Standish Group CHAOS Report

80 percent of rework is caused by missing or misunderstood requirements at the start. Not bad execution. Not lazy work. Missing clarity before the work even began.

Source: American Society for Quality

Let that last one sit for a second. Four out of five revision cycles happen because the brief was incomplete at the start. Not because the work was poor. Not because the team was slow.

The problem walked in on day one and nobody noticed.

---

The Five Types of People Who Will Change Your Work (A Love Letter)

After watching requirements evolve in real time across enough projects, you start to recognize the cast of characters. They appear in every company, every industry, every Slack workspace.

The Shower Thinker enters on day three with “I was thinking about this and I feel like we need to rethink the whole approach.” Genuinely smart person. Genuinely terrible for project timelines. Means well every single time.

The Forwarded Email was never in the original brief. They received a screenshot from someone else and now have seven questions about decisions that were finalized six weeks ago. Nobody knows how they got into the review call.

The Business Concern shows up only when the work is almost done. Has never attended a planning session. Has very strong feelings about the font choice and the overall vibe.

The Scope Creeper says “can we just add one small thing” eleven times across three different meetings. Each thing is not small. They are always very enthusiastic about it.

The Silent Approver said nothing during three full review rounds. Gave a thumbs up at the end. Then sent a message at 11pm asking why the previous version was better and whether we could go back.

You have worked with all five of these people. You have probably been one of them at some point. No judgment at all.

---

So Is It a Planning Problem or a People Problem

Source: Project Management Institute, 2022 Pulse of the Profession

Here is the honest answer that nobody wants to say out loud.

It is almost always a planning problem that looks and feels like a people problem.

When requirements are vague at the start, every single person involved fills in the gaps with their own assumptions. When the actual finished work arrives, all those different assumptions collide at once. The result looks like someone changing their mind. But really, they never had a clearly defined mind to begin with. Nobody did.

The five-day delivery window does not create more changes. It just creates more time for assumptions to turn into opinions.

---

The Positive Side That Nobody Talks About

Here is something worth saying clearly before this turns into a rant with a sad ending.

Not all feedback is scope creep. Not all revision is chaos. Some of the best work in history got better because someone pushed back on it.

The difference between painful rework and healthy iteration is one thing: clarity at the beginning.

Teams that invest 30 percent more time in requirements definition upfront reduce total project time by 40 percent.

Source: Software Engineering Institute, Carnegie Mellon University

Projects with clearly documented and agreed acceptance criteria are 3x more likely to be delivered on time and within budget.

Source: PMI Pulse of the Profession, 2022

Teams using agile with clear sprint goals report 60 percent less unplanned rework compared to teams without defined goals.

Source: McKinsey Digital, 2021

The goal is not to eliminate feedback. Feedback is how good work becomes great work. The goal is to separate genuine improvement from decisions that should have been made before the work ever started.

One is collaboration. The other is just delay wearing a productive costume.

---

What Good Actually Looks Like

The best project kickoffs in the world answer three questions before a single line of work begins.

What does done look like? Not in a vague feel-good way. Specifically. With examples. With something you can point at and say yes or no to.

Who has the final say? One person. Not a committee. Not a thread. Not whoever replies fastest. One human with a name and the authority to close the conversation.

What is out of scope? This one is uncomfortable and most people skip it. But knowing what you are not building is as valuable as knowing what you are building. Sometimes more.

When these three questions have real answers written down somewhere that everyone has actually read, the two-day vs five-day problem mostly disappears. Because by the time the work lands, everyone already agreed on what they were looking at.

No surprises. No shower thoughts on day four. No Forwarded Email with questions from 2024.

---

The Real Takeaway

Rework is expensive. Changing requirements mid-flight is expensive. But the people asking for changes are usually not villains. They are just humans operating in a system that never gave them a clear picture at the start.

The fix is boring and unglamorous. It is a better thirty-minute conversation at the beginning. It is writing down what done looks like before anyone starts. It is one brave person in every kickoff meeting willing to ask “before we move, what does approved actually mean here?”

That person is slightly annoying in the moment.

They are also the reason the project ships on time, everyone goes home at a reasonable hour, and the button color gets decided exactly once.

Be that person.