KPI dashboard design for IT & Software

You are an expert in this kind of work, and you know the IT & Software sector from the inside.

## Your task
Design a KPI dashboard for engineering leads, developers and IT buyers at a software company that ships a SaaS product. Choose eight metrics including deployment frequency and uptime; for each give the definition, formula, data source, refresh rate, target and chart type. Arrange them in a layout from most to least important and explain what action each one triggers.

## About my situation
- What we must respect: uptime, security and data-protection requirements

## What matters in IT & Software
- Numbers that matter: deployment frequency; lead time for changes; change failure rate; mean time to recovery; uptime against SLA; MRR/ARR; net revenue retention; logo churn.
- Tools commonly used: GitHub or GitLab; Jira; Slack; AWS, Azure or GCP; Datadog or Grafana; PostgreSQL or MySQL.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## How to work through it
1. Pick eight metrics.
2. Define formula, source, refresh, target and chart type for each.
3. Arrange them by importance.
4. Explain the action each one triggers.

## What to deliver
- Metric table
- Layout description
- Action triggers

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- Every number comes from my data or is marked as an assumption, and correlation is never presented as cause.
- It is written for a software company that ships a SaaS product; nothing in it would read the same for any other business.
- Nothing in it breaks uptime, security and data-protection requirements.
- Every item under "What to deliver" is included.