Web Analytics · Measurement Strategy

KPI & Goal Architecture

Each team's daily metric should trace, in one line, to the outcome the business is actually chasing.

A crowded dashboard is not a strategy. We connect the outcome to drivers teams can act on and add guardrails that reveal when one metric improves at another team's expense.

A KPI tree that lets each team trace its day-to-day metric back to the business outcome it is meant to support.

Plan KPI architectureAll Measurement Strategy & Analytics Governance tasks
A Zeo architect arranging KPI blocks into a pyramid with the north-star metric at the top

Some of the 500+ brands we've worked with

See all references
  • DenizBank
  • Yves Rocher
  • Zorlu PSM
  • Yemek.com
  • İstanbul Gedik Üniversitesi
  • Ruffles
  • GS Store

How we run it

Leadership names the outcome. The teams beneath decide how to reach it.

We organize metrics as a connected system of outcomes, drivers, diagnostics, and guardrails. Four stages turn strategic intent into a metric system with clear formulas, ownership, targets, and review points.

How we hold ourselves to it

  • Define the outcome metric — We work with leadership to agree on the one metric that best represents whether the strategy is working.
  • A tree of drivers teams can actually move — We break the outcome down into drivers that teams can actually move day to day, with a lever attached to each one.
  • Every metric gets a formula, a source, and an owner — Each metric gets a precise formula, data source, and owner, so two people calculating it independently get the same number.
  • What happens when someone games this number? — For every metric a team might be tempted to over-optimize, we define a counter-metric that catches the damage before it becomes a bigger problem.

  1. Clarify the strategy

    We interview leadership to define what the business is trying to achieve and the timeframe for that outcome.

    Strategy summary

    AI assist
    Summarizes leadership interviews into candidate outcomes.
    Human gate
    Leadership agrees on the one outcome that counts.
    Owners
    Analytics Lead, Leadership Sponsor
    Two illustrated figures talking across a row of microphones

  2. Build the metric tree

    We decompose the outcome into drivers, diagnostics, and guardrails, reviewing each proposed relationship with its owner.

    KPI tree

    AI assist
    Drafts candidate driver relationships from historical data.
    Human gate
    Metric owner confirms they can move the driver.
    Owners
    Analytics Lead, Metric Owner
    Illustrated figure sketching plans at a drafting table

  3. Write metric contracts

    We document the exact formula, source, and owner for every metric in the tree.

    Metric registry

    AI assist
    Checks formula consistency across the draft registry.
    Human gate
    Owner signs off on the formula and data source.
    Owners
    Analytics Lead, Metric Owner
    Illustrated figure holding up a signed agreement page

  4. Set targets and review cadence

    We use the available history to help set realistic targets and agree on how often the tree should be reviewed.

    Target and review plan

    AI assist
    Projects targets from historical trend data.
    Human gate
    Leadership approves the target and review cadence.
    Owners
    Analytics Lead, Leadership Sponsor
    Illustrated figure reading an oversized measurement dial

A metric without a guardrail is an invitation to be gamed.

Automation summarizes the leadership interviews into candidate outcomes, drafts driver relationships from historical data, checks formula consistency across the registry, and projects targets from trend. Ownership is the human part: leadership names the outcome, a metric owner confirms they can actually move a driver, and targets and cadence are approved rather than calculated.

What you get

Two people calculating the same metric should land on the same number.

You receive a governed metric system, not another list of numbers without context.

  • Architecture document

    KPI tree

    A visual document connecting the outcome metric to its drivers, diagnostics, and guardrails.

    Accepted when

    Every driver connects to the outcome by a path someone can read out loud.

    Cadence: Revisited each planning cycle

  • Reference document

    Metric registry

    The exact formula, source, and owner for each metric, enabling reproducible calculations.

    Accepted when

    Two people computing a metric from the registry land on the same number.

    Cadence: Amended whenever a definition moves

  • Operating guide

    Target and review plan

    Targets grounded in available history and a cadence for checking whether the tree still reflects reality.

    Accepted when

    Each target cites the history it was grounded in.

    Cadence: Reviewed on the cadence it names

We call it done when: every metric has an owner who agrees they can move it, two people compute it the same way from the registry, and each driver has a guardrail where gaming is possible.

Fit and readiness

Teams report plenty of metrics. Few can trace them back to strategy.

Too many metrics and no shared owner usually means the same argument keeps happening in different meetings.

A good fit when

  • Teams report many metrics but cannot explain which ones have a meaningful connection to strategy.
  • Departments calculate the same KPI from different formulas, so growth and conversion numbers start a fresh argument whenever teams compare them.
  • Targets lack clear baselines or owners, or no one has defined what to monitor when improving one metric harms another.

Better handled as other work when

  • You need to define which events to collect, not which metrics matter for strategy, that's Measurement Strategy & Tracking Plan.
  • You need dashboards built to display already-agreed KPIs, that's Looker Studio Dashboard Development.

If one of these is closer to your situation, start here instead: All Measurement Strategy & Analytics Governance tasks

We call it done when: leadership has agreed on the one outcome that counts, so the tree has a root instead of a committee.

People who build your measurement system

Zeo designs measurement systems that connect a business decision to governed collection and reporting you can check. The people shown here work on the part of that system this page covers.

Content we've produced on this topic

Videoby Ezgi Gülsen YaylıData Studio ile SEO KPI'larını Ölçümleme - Ezgi Gülsen YaylıVideoby Ezgi Gülsen YaylıSEO Kampanyalarında Performansın Doğru Ölçümlenmesi - Ezgi Gülsen Yaylı

Tools we use

Tools behind this work

  • Google Analytics

    checked while writing each contract, to confirm the metric is actually measurable as defined

  • Notion

    carries the metric tree and each metric's written contract, from first draft to the review cadence

Next step

Turn your metrics into something teams can act on

Bring your current dashboards and the strategy they are meant to support. We will build the metric tree that connects them with explicit assumptions and ownership.
Plan KPI architecture

Before we start

Questions teams ask before booking

Use only as many KPIs as needed to represent the outcome, its meaningful drivers, and the guardrails that matter. Diagnostic metrics may be numerous, but labeling all of them as KPIs removes the distinction.