> 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-9-employee-types.md).

# 9 Employee Types

In December 2015 Sean Graber one of the co-founders of Virtuali, wrote and article for Harvard Business Review called "[The Two Sides of Employee Engagement](https://hbr.org/2015/12/the-two-sides-of-employee-engagement)" in which he identified "9 Employee Engagement Archetypes" which categorised employees based on their perceptions of their jobs and their behaviours at work. 

The model provides a valuable framework for organisations to understand their employees' engagement levels and tailor their strategies accordingly.

1. **All-Star**\
   Highly engaged, positive, and high-performing
2. **Workhorse**\
   Dedicated, hardworking, but potentially feeling undervalued or burned out.
3. **Brat**\
   Disengaged, negative, and resistant to change.
4. **Martyr**\
   Highly engaged, but suffering in silence due to heavy workload or lack of recognition.
5. **Saboteur**\
   Disengaged, destructive, and intentionally harming the company.
6. **Cynic**\
   Disengaged, negative, but not actively harming the company.
7. **Delinquent**\
   Disengaged, indifferent, and performing poorly.
8. **Drifter**\
   Disengaged, indifferent, and not actively harming or helping the company.
9. **Underachiever**\
   Disengaged, negative, but not actively harming the company.

#### Further Reading

{% embed url="<https://hbr.org/2015/12/the-two-sides-of-employee-engagement>" %}

{% embed url="<https://medium.com/why-curiosity/the-9-types-of-employees-you-didnt-know-existed-who-to-hire-who-to-avoid-and-how-to-manage-them-c0a84d652171>" %}

{% embed url="<https://tedbauer.medium.com/nine-types-of-employees-e08722777a0e>" %}


---

# 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-9-employee-types.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.