taste-driven-core
The Taste-Driven Core Model
Overview
A product development philosophy that removes metrics/KPIs from core product teams, relying instead on founder intuition ("Taste"), long-term vision, and technical quality.
Core principle: Make the best product first, make money second. Never reverse them.
The Hierarchy
┌─────────────────────────────────────────────────────────────────┐
│ 100-YEAR VISION │
│ (The North Star) │
├─────────────────────────────────────────────────────────────────┤
│ TASTE & INTUITION │
│ (The "Okay-to" Review Process) │
│ Every release reviewed by leadership via video │
├─────────────────────────────────────────────────────────────────┤
│ TECHNICAL ARCHITECTURE │
│ (The "How" Enables Optionality) │
│ Spend time debating architecture, not just shipping │
└─────────────────────────────────────────────────────────────────┘
Key Principles
| Principle | Description |
|---|---|
| No KPIs for core | Metrics are banned for brand-defining work |
| Taste over data | Founder intuition drives decisions |
| "Okay-to" reviews | Leadership approves via video demos |
| Aim heavy | Build 100-year solution, not A/B test winner |
When to Apply
- Core product defining brand identity
- Long-term architectural decisions
- Work requiring deep technical integrity
Common Mistakes
- Demanding KPIs for every feature
- Letting A/B tests decide product direction
- Compromising architecture to ship faster
Source: Archie Abrams (Shopify VP Product & Growth) via Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
13