> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/behaviour/parkinsons-law.md).

# Parkinson's Law

Any task or project will expand to fill the time available for its completion.

Parkinson's Law is a principle that suggests work expands to fill the time available for its completion. 

If you have a task or project and you give yourself a certain amount of time to finish it, you'll probably end up taking that entire time, even if the task could have been completed more quickly. 

This law highlights how time management and deadlines can impact productivity and efficiency. So, if you want to be more efficient, consider setting shorter, realistic deadlines to avoid unnecessary delays.

#### Further Reading

{% embed url="<https://lawsofux.com/parkinsons-law/>" %}

{% embed url="<https://medium.com/weavedesign/this-is-why-you-cant-finish-early-683e6de03f42>" %}

{% embed url="<https://www.atlassian.com/blog/productivity/what-is-parkinsons-law>" %}

{% embed url="<https://blog.logrocket.com/product-management/parkinsons-law/>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=Li3xm4jeLL0>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/behaviour/parkinsons-law.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.