> For the complete documentation index, see [llms.txt](https://docs.aude.ai/aude-product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aude.ai/aude-product-documentation/goals/performance-categories.md).

# Performance Categories

<figure><img src="/files/FJjZIP1gwCjn3O7eNSCx" alt=""><figcaption></figcaption></figure>

## Define Your Organization's Leadership Principles

Performance categories are the foundation of Aude's evaluation of engineering performance. Each category represents a key leadership principle or value defining your organization's excellence.&#x20;

You can see these as templates:

{% content-ref url="/pages/sNysNEhriAYS34irSmW6" %}
[Microsoft's Growth Mindset Principles](/aude-product-documentation/goals/performance-categories/microsofts-growth-mindset-principles.md)
{% endcontent-ref %}

{% content-ref url="/pages/B7x7mvL0oXZ7wtJvCMpL" %}
[Google's Ten things we know to be true](/aude-product-documentation/goals/performance-categories/googles-ten-things-we-know-to-be-true.md)
{% endcontent-ref %}

{% content-ref url="/pages/o0VAx2fiPfI7LNwHGkpP" %}
[Amazon's Leadership Principles](/aude-product-documentation/goals/performance-categories/amazons-leadership-principles.md)
{% endcontent-ref %}

{% content-ref url="/pages/IDiC6rsP1vR1yS5Ueu62" %}
[Engineering Excellence](/aude-product-documentation/goals/performance-categories/engineering-excellence.md)
{% endcontent-ref %}

### Requirements

* Managing Performance Categories requires the Organization Administrator role
* Each category needs a clear title and measurable criteria
* Categories are visible organization-wide
* Changes affect all current and future evaluations

### Understanding Evaluation Criteria

Evaluation criteria are measurable behaviors and outcomes demonstrating excellence in a performance category. Aude uses these criteria to:

* Automatically detect positive signals from integrated tools
* Create a consistent scoring baseline across teams
* Generate objective evidence for performance reviews
* Track improvement over time

Each signal contributes to a performance score, helping identify:

* Areas of strength and excellence
* Opportunities for growth
* Progress on development goals
* Overall performance trends

## Creating a New Category

### **Performance Category Title**

* Choose a clear, memorable name (e.g., "Technical Excellence", "Customer Focus")
* Use consistent naming conventions
* Keep titles concise but descriptive

### **Evaluation Criteria**&#x20;

Each criterion should follow the formula:&#x20;

`[WHO] demonstrates [WHAT] by [HOW], measured through [SIGNALS]`&#x20;

Example criteria for "Technical Excellence":

* "Engineers demonstrate code quality by maintaining >90% test coverage, measured through CI metrics"
* "Engineers demonstrate technical leadership by providing thorough code reviews within 24 hours, measured through GitHub activity"

## Best Practices

* Create 5-7 core categories
* Include 3-5 evaluation criteria per category
* Ensure criteria are measurable through integrated tools
* Focus on observable behaviors and outcomes
* Consider your existing company values

## Managing Categories

* Categories can be edited, but changes affect all future evaluations. Prior evaluations will remain unchanged.
* Review categories quarterly to ensure alignment with organizational goals