Stop Giving Yourself Less Time to Get Better Work
Parkinson’s Law explains why generous timelines often produce bloated work. The fix is not pressure for its own sake, but tighter constraints that force clarity, focus, and faster decisions.
Most teams assume missed speed comes from complexity.
Often, it comes from excess time.
That is the core idea behind Parkinson’s Law: work expands to fill the time available for it. Give a task a quarter, and it will somehow become quarter-sized. Give it a week, and the same task is suddenly forced to reveal what actually matters.
Used well, this idea is not about rushing people. It is about removing the empty space where overthinking, unnecessary scope, and cosmetic polishing tend to grow.
Why longer timelines create worse work
When time is abundant, teams rarely stay still. They add edge cases, revisit decisions that were already good enough, and keep refining details that do not change the outcome.
The result looks busy, but the value curve flattens early.
There is usually a point where a piece of work is strong, useful, and ready to ship. Past that point, additional effort often produces very little. In some cases it makes the result worse: heavier plans, slower delivery, more coordination, and more opportunities to lose the original intent.
The challenge is finding the point where the work is complete enough to matter, but not so overworked that the team burns time protecting polish instead of delivering value.
Constraints sharpen judgment
A tight deadline does something useful: it forces prioritization.
When there is no room for everything, teams have to answer the right questions:
- What is essential?
- What can wait?
- What creates real value for the user or the business?
- What are we only doing because we had time available?
This is why work done under thoughtful constraint can feel cleaner. The team is pushed toward substance. The extras do not disappear because they are impossible. They disappear because they were never that important.
A better way to challenge estimates
Managers often run into this when discussing project timelines.
A team says something will take six months. Sometimes that estimate reflects real complexity. Sometimes it reflects risk padding, uncertainty, prior bad experiences, or the natural tendency to protect breathing room.
The wrong move is to dismiss the estimate immediately.
The better move is to treat it as a starting point and then use constraints to surface the core version of the work.
A practical sequence looks like this:
- Start by validating the estimate. Show that you believe the team is describing the work honestly.
- Cut the time window. Ask what would need to change if the delivery window were half as long.
- Look closely at what falls out. Features, dependencies, and polish items that get removed first are often the least essential.
- Protect the core value. Keep narrowing until what remains is the smallest version that still matters.
- Rebuild intentionally. Only add scope back if it clearly improves the outcome.
This approach does more than shorten plans. It exposes what the project is really for.
Speed is not the goal. Focus is.
Parkinson’s Law gets misused when leaders turn it into blanket pressure. Shorter timelines do not magically fix weak priorities, poor staffing, or unclear ownership.
The point is not to squeeze harder.
The point is to create enough constraint that the team cannot hide behind optional work. That kind of pressure can be healthy when the goals are clear, the tradeoffs are explicit, and the team is allowed to simplify.
Without those conditions, compressed timelines just create stress.
With them, they create focus.
How to put this into practice
If you want to use Parkinson’s Law productively, start small.
1. Cut the first estimate
Take an initial timeline and reduce it. Not to create panic, but to force a conversation about what is truly necessary.
2. Define the smallest valuable outcome
Before discussing polish, identify the version that solves the actual problem.
3. Treat nice-to-haves as separate decisions
Do not let optional enhancements quietly become part of the baseline.
4. Ship earlier and learn sooner
Shorter cycles create feedback faster. That matters more than elegant plans that sit untested.
5. Watch for over-polishing
When the work is already effective, more effort may only be serving internal comfort rather than customer value.
The takeaway
More time does not automatically produce better outcomes.
Very often, it produces bigger, slower, and less disciplined work.
Good constraints do the opposite. They strip the effort down to what matters, improve decision quality, and help teams deliver before momentum gets buried under avoidable complexity.
If a project feels heavier every week, the problem may not be the work itself.
It may be the time you gave it.
Keep reading
More field notes on applying AI, leading teams, and building durable companies.
The Cost of Context Switching
Engineering output drops fast when focus gets fragmented. Protect deep work, batch communication, and design your team around fewer interruptions.
The Overlooked Leverage Inside Software Companies
Internal tools rarely feel urgent, but they often deliver the fastest return in a growing software business.
The Unwritten Rules Running Your Life
Many of the limits people accept are inherited defaults, not real constraints. Progress starts by choosing rules that match reality instead of repeating someone else’s script.