# DORA metrics in action

You've prepared your Cortex workspace to hit your DORA benchmarks — what can you do now to maintain standards and encourage continuous improvement?

Learn more below on how you can prioritize DORA-related tasks and gain insights to improve your practices.

## Review, prioritize, and complete tasks

<div align="left"><figure><img src="/files/XJ8qPNFducoW5WKAdLyG" alt="Review tasks on the homepage." width="413"><figcaption></figcaption></figure></div>

<details>

<summary>Prioritize and complete work from the homepage</summary>

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

Engineers use the [Engineering homepage](/streamline/homepage.md) as their personalized daily starting point. It provides a centralized view of upcoming tasks, including:&#x20;

* **Active work**: See your open PRs, PRs assigned for review, active Jira tickets, and action items from Scorecards and Initiatives, ensuring you act quickly on work that has a direct impact on DORA metrics.
* **On-call status**: See current and upcoming on-call shifts, helping you stay prepared for efficient incident response.
* **Scorecards and Initiatives**: In the Scorecard section, see real-time progress toward standards. Under "Initiatives due soon," see action items and their due dates.&#x20;

  <figure><img src="/files/wKmscwDsZIjjE3qENsVN" alt="Initiatives due soon are listed on the homepage."><figcaption></figcaption></figure>
* **Shortcuts**: Use direct links to quickly access your owned entities.&#x20;

</details>

<details>

<summary>Act on failing Scorecard rules</summary>

<div align="left"><figure><img src="/files/wTKV8oL0nZwFVgMd0CfL" alt="" width="533"><figcaption></figcaption></figure></div>

#### Review failing rules

When a Scorecard rule is failing, this information is surfaced to you in multiple ways:

* Scorecard rules that require your attention appear on the [Engineering homepage](/streamline/homepage.md).
* You can receive notifications via Slack, Microsoft Teams, or email when a Scorecard rule is failing.
  * Learn more in the [Notifications docs](/configure/settings/notifications.md).
* You can review a Scorecard's progress in [reports](/improve/reports.md) or by [viewing the Scorecard](/standardize/scorecards/evaluate.md) in Cortex.

#### Remediate failing rules&#x20;

When a service falls short of standards, there are different ways you can approach remediation:

* You can identify and troubleshoot trends in Scorecards, and consider scalable remediation efforts. Learn more in [Review and evaluate Scorecards](/standardize/scorecards/evaluate.md).
* You can set up an [Initiative](/improve/initiatives.md) to assign and track remediation tasks.
  * You can also automatically create issues in Jira, ClickUp, Azure DevOps, and GitHub based on Initiatives. After creating an issue config, Cortex will automatically create a parent issue for each entity with failing rules, and each failing rule will be created as a subtask. Learn more in [Creating issues based on Initiatives](/improve/initiatives/issue-config.md).

</details>

## Use Cortex MCP to reduce MTTR

For a faster incident response, use [Cortex MCP](/get-started/mcp.md) to gather information about affected entities and get suggested next steps. This more efficient process contributes directly to reducing your MTTR.

See an example incident response approach using Cortex MCP in [Incident Response in action](/solutions/incident-mgmt/in-action.md#incident-response-with-cortex-mcp).

## Analyze and act on trends in Eng Intelligence metrics

Eng Intelligence allows you to view organization-wide and historical data, making it easy for leaders to validate the impact of Scorecards and for teams to see their progress toward goals.

<div align="left"><figure><img src="/files/u5t0gB403DCo0cQUmQzQ" alt="Analyze trends in the DORA dashboard." width="563"><figcaption></figcaption></figure></div>

View the [DORA Dashboard](/improve/eng-intelligence/dashboards/dora-dashboard.md) to see how your teams are measuring against DORA standards, then take action to promote continuous improvement.

* **Measure**: Track cycle time, deployment frequency, change failure rate, and time to resolution in the DORA Dashboard.&#x20;
  * Look at these trends before launching Scorecards to better understand your baseline performance.
* **Investigate**: On the DORA Dashboard, filter the individual metrics by date range, group, owner, repo, and labels to spot trends, and switch aggregations for cycle time and MTTR to spot outliers. Use the [Metrics Explorer](/improve/eng-intelligence/metrics-explorer.md) to drill into underlying data from deploys, version control systems, Jira, and PagerDuty, and validate where bottlenecks occur.
* **Take action**: When you identify a bottleneck that affects your DORA benchmarks, take action.&#x20;
  * For example:
    * Create a targeted [Initiative](/improve/initiatives.md) to fix an issue. For instance, if your rules relating to MTTR are not passing, you might [create an Initiative directly from the Scorecard](/standardize/scorecards/create.md#create-initiative-from-scorecard) to target MTTR.
      * Initiatives send notifications to users asking them to complete tasks by the deadline you configured. Learn more in [Initiatives and Action items](/improve/initiatives.md).
    * To promote broader changes, launch a [Scorecard](/standardize/scorecards.md).
    * To improve efficiency in a process, ask users to start using [Cortex MCP](/get-started/mcp.md).
      * For an example demonstrating how you can use Cortex MCP to improve incident response time, see [Incident Response in action](/solutions/incident-mgmt/in-action.md#incident-response-with-cortex-mcp).
* **Validate impact**: After taking action, watch as metrics like MTTR, cycle time, or deployment frequency shift on your DORA Dashboard while your team works to meet goals.
  * For example:
    * After you launch a DORA Scorecard, you see deploy frequency increasing as the team adopts the new standards.
    * After you require users to configure and use Cortex MCP, you see MTTR decreasing as the team's incident response process becomes more efficient.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cortex.io/solutions/dora/in-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.