> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stage3.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating KPIs

> Step-by-step guide to creating Key Performance Indicators for your processes

## Before You Create a KPI

Creating good KPIs requires thoughtful planning. Before jumping in, ask yourself:

* **What does success look like** for this process?
* **What number would tell you** if the process is working?
* **Can you realistically measure** this metric?
* **Will tracking this help** you make better decisions?

<Info>
  The best KPIs directly connect to your process goals. If improving this number means the process is working better, it's probably a good KPI.
</Info>

## Choosing What to Measure

<AccordionGroup>
  <Accordion title="Start with Process Goals" icon="bullseye" defaultOpen>
    What is this process trying to accomplish?

    **Example:** Your customer onboarding process aims to get new customers successfully using your product.

    **Possible KPIs:**

    * Time to first login
    * % of customers who complete setup
    * Satisfaction score after first week
    * Support tickets during onboarding
  </Accordion>

  <Accordion title="Identify Success Factors" icon="star">
    What factors determine if this process succeeds or fails?

    **Example:** For a hiring process, success means hiring great people quickly.

    **Success factors:**

    * Speed (time to hire)
    * Quality (new hire performance ratings)
    * Efficiency (cost per hire)
    * Fit (retention rate in first year)
  </Accordion>

  <Accordion title="Focus on What You Control" icon="hand">
    Choose metrics you can actually influence through process improvements.

    **Good:** Time to respond to support tickets (you control this)
    **Bad:** Industry-wide customer satisfaction (you don't control this)
  </Accordion>

  <Accordion title="Balance Multiple Perspectives" icon="scale-balanced">
    Consider different dimensions:

    * **Speed:** How fast?
    * **Quality:** How well?
    * **Cost:** How efficiently?
    * **Satisfaction:** How happy are stakeholders?

    Don't focus on just one dimension.
  </Accordion>
</AccordionGroup>

## Creating Your First KPI

<Steps>
  <Step title="Navigate to the KPIs Tab">
    Open the core process where you want to add a KPI.

    Click on the **"KPIs"** tab in the main navigation bar (next to SOP, RACI, Visual, etc.).
  </Step>

  <Step title="Create New KPI">
    Click the **"+ New KPI"** or **"+ Create First KPI"** button. This will open the "Create New KPI" modal.
  </Step>

  <Step title="What are you measuring?">
    This is the name of your KPI. Choose a clear, descriptive name.

    **Example:** "Number of sales calls per week"
  </Step>

  <Step title="Who is responsible?">
    This is the **Owner** of the KPI. Select the team member responsible for tracking and reporting this metric from the dropdown.
  </Step>

  <Step title="How will you measure it?">
    This is the **Definition**. Describe the specific method for collecting the data.

    **Example:** "Count all outbound calls logged in CRM system"
  </Step>

  <Step title="What indicates success?">
    This is the **Measurement Type**. Select whether a higher or lower number is better.

    **Options:**

    * Higher is Better (e.g., sales revenue, satisfaction score)
    * Lower is Better (e.g., response time, costs)
  </Step>

  <Step title="Set Frequency, Goal Value, and Unit">
    Fill in the final fields:

    * **Frequency:** How often you will measure this (e.g., Daily, Weekly, Monthly).
    * **Goal Value:** The target number you are aiming for.
    * **Unit (optional):** The unit of measurement (e.g., calls, %, hours).
  </Step>

  <Step title="Save Your KPI">
    Click **"Create KPI"** to add the KPI to your process dashboard.

    You can now start recording values.
  </Step>
</Steps>

## KPI Properties Explained

<AccordionGroup>
  <Accordion title="What are you measuring?" icon="heading" defaultOpen>
    **Required:** Yes

    The clear, descriptive name for the metric.

    **Tips:**

    * Use consistent naming.
    * "Number of sales calls per week" is better than "Sales calls".
  </Accordion>

  <Accordion title="Who is responsible?" icon="user">
    **Required:** Yes

    The team member accountable for tracking this metric.

    **Responsibilities:**

    * Record actual values.
    * Report on trends.
    * Take action when falling short of the goal.
  </Accordion>

  <Accordion title="How will you measure it?" icon="book">
    **Required:** No (but highly recommended)

    The detailed definition of what you're measuring and how it's calculated.

    **Should include:**

    * What is being measured
    * How it's calculated
    * Data sources
  </Accordion>

  <Accordion title="What indicates success?" icon="chart-line">
    **Required:** Yes

    How the KPI is measured:

    * **Higher is better** (e.g., satisfaction score)
    * **Lower is better** (e.g., response time)
  </Accordion>

  <Accordion title="Goal Value" icon="bullseye">
    **Required:** Yes

    The target number you're trying to achieve.

    **Tips:**

    * Base it on data, not wishful thinking.
    * Make it challenging but achievable.
  </Accordion>

  <Accordion title="Frequency" icon="calendar">
    **Required:** Yes

    How often you measure and report (e.g., Daily, Weekly, Monthly).
  </Accordion>

  <Accordion title="Unit (optional)" icon="beaker">
    **Required:** No

    The unit of measurement (e.g., calls, %, hours, days).
  </Accordion>
</AccordionGroup>

## Examples by Process Type

<Tabs>
  <Tab title="Sales Process">
    **Process:** B2B Enterprise Sales

    **KPI 1: Lead Conversion Rate**

    * **What are you measuring:** Lead Conversion Rate
    * **How will you measure it:** Percentage of qualified leads that become paying customers, measured monthly
    * **Who is responsible:** Sales Director
    * **Success:** Higher is Better
    * **Frequency:** Monthly
    * **Goal Value:** 25
    * **Unit:** %

    **KPI 2: Average Sales Cycle**

    * **What are you measuring:** Average Sales Cycle
    * **How will you measure it:** Average days from first contact to closed-won, calculated monthly
    * **Who is responsible:** Sales Operations Manager
    * **Success:** Lower is Better
    * **Frequency:** Monthly
    * **Goal Value:** 60
    * **Unit:** days
  </Tab>

  <Tab title="Support Process">
    **Process:** Customer Support Ticket Resolution

    **KPI 1: First Response Time**

    * **What are you measuring:** First Response Time
    * **How will you measure it:** Average hours from ticket creation to first agent response, calculated daily
    * **Who is responsible:** Support Manager
    * **Success:** Lower is Better
    * **Frequency:** Daily
    * **Goal Value:** 2
    * **Unit:** hours

    **KPI 2: Customer Satisfaction**

    * **What are you measuring:** Customer Satisfaction (CSAT)
    * **How will you measure it:** Average CSAT score from post-resolution surveys (1-5 scale), calculated weekly
    * **Who is responsible:** Support Manager
    * **Success:** Higher is Better
    * **Frequency:** Weekly
    * **Goal Value:** 4.5
    * **Unit:** (none)
  </Tab>

  <Tab title="HR Process">
    **Process:** New Employee Onboarding

    **KPI 1: Time to Productivity**

    * **What are you measuring:** Time to Productivity
    * **How will you measure it:** Days from start date until new hire meets 100% of productivity goals, averaged monthly
    * **Who is responsible:** HR Director
    * **Success:** Lower is Better
    * **Frequency:** Monthly
    * **Goal Value:** 60
    * **Unit:** days

    **KPI 2: New Hire Satisfaction**

    * **What are you measuring:** New Hire Satisfaction
    * **How will you measure it:** Average score from 30-day onboarding survey (1-5 scale)
    * **Who is responsible:** HR Manager
    * **Success:** Higher is Better
    * **Frequency:** Monthly
    * **Goal Value:** 4.3
    * **Unit:** (none)
  </Tab>
</Tabs>

## Setting Realistic Targets

<Steps>
  <Step title="Measure Current Performance">
    Before setting a goal, know where you are now. This is your baseline.

    Track the metric for at least 2-4 weeks to get a true average.
  </Step>

  <Step title="Research Benchmarks">
    Look at:

    * Industry standards
    * Competitor performance (if available)
    * Best-in-class examples
    * Your own historical data

    This gives context for what's achievable.
  </Step>

  <Step title="Consider Resources">
    Can you realistically hit the target with:

    * Current staff levels
    * Existing tools and systems
    * Available budget
    * Time constraints

    Don't set goals that require resources you don't have.
  </Step>

  <Step title="Set Stretch Goals">
    Targets (Goal Values) should be challenging but achievable.

    **Too easy:** Current performance is 4 hours, goal is 3.9 hours (no real improvement)
    **Too hard:** Current performance is 4 hours, goal is 30 minutes (impossible)
    **Just right:** Current performance is 4 hours, goal is 2 hours (significant improvement, achievable with effort)
  </Step>

  <Step title="Phase Improvements">
    For major improvements, set intermediate milestones.

    **Example:**

    * Current: 4 hours
    * Q1 goal: 3 hours
    * Q2 goal: 2.5 hours
    * Q3 goal: 2 hours (final goal)
  </Step>
</Steps>

<Tip>
  **Use the 80/20 rule:** Initial improvements are usually easier than later ones. Getting from 4 hours to 3 hours might be easy; getting from 2.5 hours to 2 hours requires more effort.
</Tip>

## Common KPI Mistakes

<Warning>
  **Measuring Too Much**

  Don't create a KPI for everything. Focus on the vital few metrics that truly indicate success.

  **Fix:** Limit to 2-5 KPIs per process. More than that becomes unmanageable.
</Warning>

<Warning>
  **Vanity Metrics**

  Don't track metrics that look impressive but don't drive real improvement.

  **Example:** Total website visitors (vanity) vs. conversion rate (actionable)

  **Fix:** Ask "If this number improves, does our process actually get better?"
</Warning>

<Warning>
  **Unmeasurable KPIs**

  Don't create KPIs you can't actually track consistently.

  **Example:** "Customer happiness" (vague) vs. "Customer satisfaction score from surveys" (measurable)

  **Fix:** Ensure you have a reliable way to collect the data in the "How will you measure it?" field.
</Warning>

<Warning>
  **Gaming the System**

  Be careful of KPIs that incentivize bad behavior.

  **Example:** Measuring only "tickets closed" might cause agents to close tickets prematurely without solving problems.

  **Fix:** Balance multiple metrics. Add "resolution quality" or "customer satisfaction" alongside "tickets closed."
</Warning>

## KPI Best Practices

<CardGroup cols={2}>
  <Card title="SMART Framework" icon="target">
    Make KPIs **S**pecific, **M**easurable, **A**chievable, **R**elevant, and **T**ime-bound
  </Card>

  <Card title="Automate When Possible" icon="robot">
    Use system reports and dashboards to auto-calculate KPIs instead of manual tracking
  </Card>

  <Card title="Review Regularly" icon="calendar-check">
    Revisit goal values quarterly. Business conditions change; targets should too.
  </Card>

  <Card title="Share Broadly" icon="share-nodes">
    Make KPI status visible to the team. Transparency drives improvement.
  </Card>
</CardGroup>

## After Creating Your KPI

Once you've created a KPI:

<Steps>
  <Step title="Start Tracking">
    Begin recording actual values according to your defined frequency.

    Learn more: [Recording KPI Values](/processes/recording-kpi-values)
  </Step>

  <Step title="Share with Team">
    Make sure everyone involved in the process knows about the KPI and what the goal is.
  </Step>

  <Step title="Monitor Trends">
    Watch how the KPI changes over time. Look for patterns, improvements, or deterioration.
  </Step>

  <Step title="Take Action">
    When KPIs are falling short of the goal, investigate why and take corrective action.
  </Step>

  <Step title="Celebrate Success">
    When you hit goals, acknowledge the team's efforts. Positive reinforcement matters.
  </Step>
</Steps>

## KPI Creation Checklist

Before finalizing your KPI:

* Name clearly describes what's being measured
* "How will you measure it?" explains the calculation
* "What indicates success?" is set correctly
* "Goal Value" is challenging but achievable
* "Frequency" makes sense for the metric
* "Responsible" person is assigned
* Data source is identified and accessible
* Team understands why this metric matters

## Next Steps

<CardGroup cols={2}>
  <Card title="Recording KPI Values" icon="pen-to-square" href="/processes/recording-kpi-values">
    Learn how to track your KPI data over time
  </Card>

  <Card title="What Are KPIs?" icon="circle-question" href="/processes/what-are-kpis">
    Review KPI fundamentals
  </Card>
</CardGroup>