> 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/universal/managing-people/the-peter-principle.md).

# Peter Principle

<figure><img src="https://1194756820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7GrawCzldiDSsP1yfNLi%2Fuploads%2Fgit-blob-a94357197f88ab4a557c968f98a02a9cd03a98d1%2Fpeter-principle.png?alt=media" alt=""><figcaption><p>Image by <a href="https://sketchplanations.com/the-peter-principle">Sketchplanations</a></p></figcaption></figure>

The Peter Principle is a theory that states that employees in a hierarchical organisation tend to be promoted to their level of incompetence. In other words, individuals are promoted based on their performance in their current role, but once they reach a position where their skills are no longer sufficient, they are no longer promoted.

This principle is often used to explain why some organisations seem to have a large number of incompetent managers. It suggests that these managers were promoted to their positions because they were good at their previous jobs, but once they were in a role that required different skills, they were no longer able to perform effectively.

The Peter Principle raises some important questions about promotion policies and organisational structures. It suggests that organisations should be careful about promoting employees based solely on their performance in their current role, and that they should consider other factors, such as their potential for growth and development.

#### Further Reading

{% embed url="<https://en.wikipedia.org/wiki/Peter_principle>" %}

{% embed url="<https://medium.com/@ronmci/are-you-aware-of-the-peter-principle-and-business-2237f98c5847>" %}

{% embed url="<https://uxdesign.cc/the-peter-principle-how-lazy-leadership-can-stifle-your-design-career-74bd6fc747e>" %}

{% embed url="<https://medium.com/@1kg/why-good-employees-often-fail-after-promotions-the-peter-principle-39ca4ff2f3ee>" %}


---

# 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/universal/managing-people/the-peter-principle.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.