> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/heart/efficiency.md).
# Efficiency
What the Efficiency dimension measures, how it scores task completion speed and user proficiency, and when it activates.
Efficiency is the HEART[^1] dimension that measures how well users perform tasks[^2] when they complete them. It tracks whether completions happen at a consistent pace and whether the user base becomes more proficient over time.
## What Efficiency measures
Efficiency answers three questions about an application:
* Are users completing tasks at a consistent and reasonable pace?
* Is the user base getting more proficient over time?
* Which tasks or audiences show the lowest efficiency?
Efficiency measures the speed and consistency of completions. Task Success measures whether tasks complete. Adoption measures who uses the application. The three are related but score different things.
The Efficiency dimension detail in the HEART scorecard.
{% hint style="warning" %}
Both Efficiency metrics depend on Tasks. If no Tasks are configured for the application, Efficiency does not activate and does not contribute to HEART.
{% endhint %}
## How the score is calculated
The Efficiency score combines two metrics, task completion efficiency and user proficiency, each on a scale of 0 to 100. If one metric lacks enough data, the score reflects the other alone.
When Efficiency is inactive, for example because no Tasks are configured or there is not enough data yet, HEART handles it as described in [How the score is calculated](/intelligence/heart.md#how-the-score-is-calculated).
## What feeds the score
{% columns %}
{% column %}
### Task completion efficiency
The share of tasks completed within a reasonable time for that specific task, based on how long it normally takes.
Each task is measured against its own baseline, not one threshold for all tasks. A task that usually takes two minutes is held to a different standard than one that usually takes thirty seconds. The measure reflects consistency within your own user base.
{% endcolumn %}
{% column %}
### User proficiency
The share of users who have become proficient in their regular tasks.
A user is proficient when their recent completions of regular tasks consistently fall close to the typical completion time for those tasks in your organization. Users without enough task history are left out of the calculation. Each user is measured on their own tasks, not against other users.
{% endcolumn %}
{% endcolumns %}
### Activation
Efficiency activates once the application has collected enough task completions over a sufficient period. Tasks must be configured first.
## Relevant articles
{% content-ref url="/pages/TBF4QYHDMWQghy26u8xI" %}
[HEART](/intelligence/heart.md)
{% endcontent-ref %}
{% content-ref url="/pages/nJSkeXwSmCTopscQ7Fmx" %}
[Tasks](/intelligence/tasks.md)
{% endcontent-ref %}
{% content-ref url="/pages/iSW1aAIFYuiVThZ8DMfM" %}
[Create a task in the Editor](/intelligence/tasks/create-a-task-in-the-editor.md)
{% endcontent-ref %}
{% content-ref url="/pages/v7SOlgVUQT5Cd3NHaTih" %}
[Task Success](/intelligence/heart/task-success.md)
{% endcontent-ref %}
## FAQ
What happens if no Tasks are configured?
Efficiency does not activate, and HEART is calculated from the remaining active dimensions. [Create a task](/intelligence/tasks/create-a-task-in-the-editor.md) to start scoring Efficiency.
What is the difference between Efficiency and Task Success?
Task Success measures whether tasks complete at all. Efficiency measures the speed and consistency of those completions.
[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100.
[^2]: A task in Userlane is a defined multi-step process that Userlane tracks automatically, measuring every attempt against the definition.
---
# 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://docs.userlane.com/intelligence/heart/efficiency.md?ask=&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.
