Data-driven decision making sounds straightforward: look at the data, make decisions. In practice, it’s harder. Data can mislead, overwhelm, or paralyze. Startups often have too little data, unreliable data, or conflicting data. Understanding how to collect, analyze, and act on data—while maintaining the judgment and speed that startups need—is essential.
Data-Driven vs. Data-Informed
Data-driven: Data determines decisions
Data-informed: Data informs judgment
Startups should be data-informed, not blindly data-driven.
Why the Distinction Matters
Pure data-driven has problems:
•
Data doesn’t capture everything
•
Optimization can be myopic
•
Novel situations lack data
Judgment + data beats data alone.
•
Acquisition: How customers arrive
•
Activation: First value experience
•
Retention: Do they come back?
•
Referral: Do they tell others?
The AARRR framework remains useful.
Leading indicators: Predict future outcomes
Lagging indicators: Show past results
Track both; lead with leading indicators.
Vanity metrics: Look good, don’t help
•
Total users (without context)
Actionable metrics: Drive decisions
Building Data Infrastructure
•
Basic analytics (Mixpanel, Amplitude, PostHog)
Sophistication comes later.
Quality matters more than quantity:
Bad data leads to bad decisions.
•
Analytics tools → Data warehouse → BI tools
•
Manual analysis → Automated dashboards
•
More sophisticated analysis
Build what you need, when you need it.
Compare groups over time:
•
Acquisition cohorts (when they joined)
•
Feature cohorts (what they use)
Essential for understanding retention and growth.
Track progression through steps:
•
Where do people drop off?
•
What’s the conversion rate?
Funnels reveal optimization opportunities.
Averages hide important differences.
Making Decisions with Data
Data informs, doesn’t decide.
Sometimes data is obvious:
Act quickly on clear data.
Apply judgment. Make a call. Monitor.
Sometimes you don’t have data:
Use proxies, analogies, and judgment. Don’t wait for perfect data.
Waiting for perfect data:
•
Never have complete information
•
Speed matters in startups
•
Good enough > perfect too late
Fix: Set decision deadlines. Act on imperfect data.
Measuring the Wrong Things
Tracking what’s easy, not what matters:
•
What you can measure, not what you should
Fix: Start with decisions needed, work back to data required.
Data without context misleads:
Fix: Understand the story behind numbers.
Optimizing metrics at expense of goals:
•
Missing the forest for trees
Fix: Keep sight of real objectives. Metrics serve goals.
Finding what you want to find:
•
Ignoring contradicting data
Fix: Actively seek disconfirming evidence. Question assumptions.
•
Ask for data in discussions
•
Reference data in decisions
•
Admit when data changes your mind
•
Show how data informs judgment
•
Data literacy development
Record how decisions were made:
•
What judgment was applied
•
What would you do differently?
Learn from past decisions.
•
Mixpanel, Amplitude (product analytics)
•
PostHog (open source alternative)
•
Google Analytics (web traffic)
•
Segment (data collection)
•
Metabase, Looker, Tableau
•
Snowflake, BigQuery, Redshift
•
Add sophistication when needed
•
Focus on using data, not collecting it
Startup Speed Requirements
Data should accelerate, not slow down.
•
Quick analysis capability
Startups accept more uncertainty:
•
80% confidence often enough
•
Directional data valuable
•
Speed of learning matters
Don’t wait for statistical significance on every decision.
•
Be data-informed, not blindly data-driven; judgment + data beats data alone
•
Track AARRR: acquisition, activation, retention, revenue, referral
•
Focus on actionable metrics over vanity metrics
•
Start simple with analytics; build sophistication as needed
•
Data quality matters more than quantity; bad data leads to bad decisions
•
Cohort analysis, funnel analysis, and segmentation reveal what averages hide
•
When data is unclear or absent, apply judgment and monitor results
•
Common mistakes: analysis paralysis, measuring wrong things, ignoring context, over-optimizing
•
Build data culture: model data use, enable access, document decisions
•
Data should accelerate decisions, not slow them down; 80% confidence is often enough