What is Parkinson's Law and how to use it to manage multiple jobs without procrastination

Parkinson's Law—coined by historian Cyril Northcote Parkinson in 1955—states that "work expands to fill the time available for its completion." In other words, if you allocate two hours to a task that could be done in 30 minutes, you’ll likely spend the full two hours on it. While this principle originated in bureaucracy, it’s a powerful tool for anyone juggling multiple jobs and struggling with procrastination or the feeling of always being behind. The key isn’t working harder; it’s constraining time to force your brain to prioritize and execute efficiently.

Why Parkinson's Law is your ally (not your enemy)

Parkinson observed that British civil servants deliberately stretched out simple processes to justify their workload. Today, we know this phenomenon isn’t limited to offices—it affects freelancers, entrepreneurs, and anyone managing multiple projects at once. The difference lies in how we interpret it. Instead of seeing it as a flaw, we can use it to our advantage with two complementary approaches:

• Time constraints: Assign tight (but realistic) deadlines to tasks to prevent them from expanding into unproductive hours.
• Outcome-focused work: Measure success by what you complete, not the time spent. If a 60-minute meeting can be resolved in 20, why not do it?
• Eliminating filler: Identify tasks that inflate out of habit (like checking email every 10 minutes) and limit them with clear boundaries.

Parkinson's Law isn’t a diagnosis of laziness—it’s a reminder that time is finite: if you don’t manage it, inertia will.

How to apply Parkinson's Law to manage multiple jobs without burning out

1. Diagnose your "inflatable tasks"

The first step is identifying which activities consume more time than necessary. For example, a freelance designer managing projects for three clients might notice they spend 2 hours daily on emails, when 30 minutes would suffice if they batch responses. To spot these tasks:

• Track your time for 3 days, noting what you do and how long it takes (use a notebook or a tool like time-blocking for unpredictable schedules).
• Mark tasks that repeat and seem to expand unnecessarily (e.g., "checking social media," "organizing files," "preparing reports").
• Ask: Does this task directly contribute to my goals? If not, it’s a candidate for elimination or time limits.

2. Assign artificial deadlines (and stick to them)

The artificial deadline technique involves deliberately shortening the time allocated to a task to force focus. For example, if a developer needs to review a GitHub pull request for one client and a Jira task for another, instead of leaving it "for when I have time," they can block 25 minutes in their calendar and commit to finishing it then. To make it work:

• Break into micro-deadlines: If a task takes 4 hours, split it into 50-minute blocks with 10-minute breaks (adapted Pomodoro).
• Use visible timers: Set a countdown on your desktop or phone to create psychological urgency.
• Commit publicly: If working in a team, announce you’ll send the draft by 11:00 AM. Social pressure reduces the temptation to procrastinate.

3. Prioritize with the Eisenhower Matrix (with a Parkinson twist)

The Eisenhower Matrix sorts tasks into four quadrants based on urgency and importance. To apply Parkinson’s Law to multiple jobs, add a layer: assign a maximum time limit to each quadrant. For example:

• Urgent and important (e.g., delivering a client project): Max 2 hours/day. If it doesn’t fit, delegate or negotiate deadlines.
• Important but not urgent (e.g., planning a new client’s strategy): 1 hour/day, in a fixed block (e.g., 9:00–10:00 AM).
• Urgent but not important (e.g., replying to a vendor email): 15 minutes/day, batched into one block.
• Neither urgent nor important (e.g., checking Slack notifications): 5 minutes/day, or eliminate it.

This approach prevents low-priority tasks from eating into time meant for strategic work. A common mistake is letting urgent (but unimportant) tasks dominate your day.

Real-world examples: How professionals use Parkinson's Law

Case 1: The freelancer with three clients and a tight deadline

Maria, a graphic designer, has three active projects: a brand redesign for Client A (due in 5 days), a presentation for Client B (due in 2 days), and updates for Client C (due in 1 week). Instead of working in parallel and stretching each task, she applies Parkinson’s Law like this:

• Assigns 90-minute blocks to each project, with 15-minute breaks in between.
• For Client B (shortest deadline), she reduces the block to 60 minutes and eliminates distractions (mutes notifications, uses airplane mode).
• At the end of each block, she sends a progress update to the client to create accountability and prevent work from expanding.

Case 2: The remote team with endless meetings

A development team using GitHub and Jira notices their daily sync meetings last 45 minutes, when 15 would suffice. To apply Parkinson’s Law:

• Sets a strict 15-minute limit and a fixed agenda: 1) blockers, 2) daily priorities, 3) task assignments.
• Uses a visible timer for everyone and cuts off off-topic discussions.
• Long discussions are postponed to dedicated meetings with defined time slots (e.g., "We’ll discuss this Thursday from 10:00–10:30 AM").

Result: They reclaim 2.5 hours per person per week, redirecting it to development tasks. If you want to unify tasks from tools like GitHub and Jira, check out this step-by-step guide.

Common mistakes when applying Parkinson's Law (and how to avoid them)

1. Deadlines that are too tight

Shrinking time doesn’t mean working under constant stress. If you assign 20 minutes to a task that needs an hour, you’ll only create frustration. The solution is to calibrate deadlines with real data. For example, if you track that code reviews take 45 minutes, assign 50 minutes (a 10% buffer for unexpected issues).

2. Ignoring external dependencies

Some tasks depend on others (e.g., waiting for client feedback). In these cases, Parkinson’s Law applies only to your part of the work. For example, if you need to send a draft and wait for review, assign 1 hour to prepare the draft and schedule a reminder to follow up 24 hours later.

3. Not leaving room for the unexpected