# Metric types

DoubleLoop's tool for mapping your strategy was inspired by Amplitude's [North Star Playbook](https://amplitude.com/north-star) by John Cutler and Jason Scherschligt. The framework provides a model for how work and metrics relate to each other:

![Adapted from Amplitude's North Star Playbook](/files/y8j8Utteihzwz8dgI2RD)

There are three types of metrics in DoubleLoop that live on a spectrum from leading to lagging indicators:

* **Input metrics**. Input metrics are *leading indicators* that can be influenced by work, like the percent of users that perform a certain action during a session. By themselves, they don’t equate business success.
* **North Star metric**. Your North Star metric is how you measure the value you're delivering customers. If you grow the metric, you'll make your users and happy and grow your business. It's the bridge between your leading and lagging indicators. A rule of thumb is that you should have one North Star metric per product at your company.
* **Business KPIs**. Business KPIs are lagging indicators that matter for your business; things like revenue and customer retention. Because they are lagging and subject to external forces, they often can't be impacted directly by work.

For background on how the top companies think about their metrics, see our post, [*Metrics-driven product development is hard*](https://blog.doubleloop.app/metrics-driven-product-development-is-hard/).


---

# 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.doubleloop.app/measure/strategy-map-concepts.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.