Skip to content
The Latent Daily
The Latent Daily

Sections

News & Industry
Knowledge & Learning
Research & Science
Tools, Software & Models
Developers & Builders
Hardware & Infrastructure
Society, Policy & Ethics
AI in Industries
People & Community
Special Formats

Tag

#Metrics

Metrics on The Latent Daily: 2 prompts. News, explainers and guides on Metrics, each linked to its sources.

2 items

Prompts tagged #Metrics

Data analysisintermediate

Investigate why a metric suddenly changed

You are a senior analyst investigating an unexpected change in a metric. Help me find the cause without jumping to conclusions. Metric: [NAME AND DEFINITION, e.g. "daily signups = new accounts created, all platforms"] What changed: [e.g. "fell 22% on Tuesday compared with the previous four Tuesdays"] When it started: [DATE AND TIME, TIME ZONE] Context I know about: [e.g. "app release 4.2 on Monday, paid campaign paused last week, public holiday in Germany"] Dimensions available: [e.g. "platform, country, traffic source, app version, browser"] Related metrics I can see: [e.g. "visits, signup form starts, error rate"] Work through this in order: 1. Rule out data problems first: tracking changes, pipeline delays, duplicated or missing events, time zone or definition changes, bot traffic. Say how to check each. 2. Put the change in context: is it outside normal variation (day-of-week, seasonality, previous similar dips)? 3. List 4-6 hypotheses ranked by likelihood given what I told you, with the evidence that would confirm or rule out each. 4. For each hypothesis, name the specific breakdown to run (e.g. "signups by app version, Monday vs Tuesday"). 5. Describe what to do if the drop is concentrated in one segment versus spread evenly. 6. Give a short incident-style summary template: what happened, impact, cause, confidence, next steps. Do not state a cause as fact. Label each conclusion with your confidence and what it is based on.

Works with: ChatGPT, Claude, Gemini

Data analysisintermediate

Define dashboard KPIs so everyone calculates them the same way

You are an analytics lead building a metrics dictionary for a dashboard. Business and team: [e.g. "B2B SaaS, customer success team"] Decisions this dashboard should support: [e.g. "which accounts need attention this week", "quarterly churn review"] KPIs we want (names as people use them today): [e.g. "active users, churn, NRR, time to first value"] Data sources available: [e.g. "product events in BigQuery, Stripe subscriptions, HubSpot CRM"] Known disagreements: [e.g. "sales and finance report different churn numbers"] For each KPI, produce a dictionary entry with: - Name and one-sentence business meaning - Exact formula (numerator, denominator, time window, unit) - Inclusions and exclusions (test accounts, free plans, refunds, internal users) - Data source and table/field names, or "to confirm" if you do not know them - Grain and refresh frequency (daily, weekly; by account, by user) - Owner role (who decides if the definition changes) - Target or healthy range, if one can be justified, otherwise "to set" - Caveats and common misreadings Then: 1. Flag KPIs that overlap or could be confused, and suggest which to keep. 2. Suggest 1-2 leading indicators for each lagging KPI. 3. List questions the team must answer before the definitions are final. Do not invent company-specific numbers or field names; mark assumptions clearly.

Works with: ChatGPT, Claude, Gemini, Any LLM