solve-before-scale
The Solve Before Scale Protocol
Overview
A phased approach to product development that prioritizes solving a core problem with qualitative signals before attempting to scale with quantitative metrics.
Core principle: Prototypes > PRDs. Build to think; use prototypes to discover what to build.
The Two Phases
┌─────────────────────────────────────────────────────────────────┐
│ PHASE 1: SOLVE │
├─────────────────────────────────────────────────────────────────┤
│ • Embrace chaos and "wide lurches" in direction │
│ • Ignore "grownup metrics" (CTR, retention) │
│ • Focus on qualitative "magic moments" │
│ • Build prototypes to discover what to build │
│ • Find the core utility that users love │
More from coowoolf/insighthunt-skills
gamification-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
46gardening-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
45minimum 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.
16three-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
15pre-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
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
13