Skip to content

Problem Taxonomy

Purpose

The problem taxonomy defines the founder problems the OS should recognize.

This is the bridge between survey answers, Compass answers, knowledge, partners, events, network, and advisor support.

Starting Problem Categories

Problem Category Clean Founder Language
Direction I need direction
Customers I need more customers
Marketing I need people to know I exist
Sales I need to manage leads and sales better
Funding I need money to grow
Finance I need financial control
Systems I need better systems
Exit I need to build value or prepare for exit
Legal I need legal structure or protection
Team I need people or leadership support
Networking I need the right relationships
Service Providers I need trusted help
Website I need to look professional online
Banking I need a business bank account
Payments I need to accept money

Problem Logic

Founders often describe symptoms before root problems.

The OS should support both.

flowchart LR
  A[Founder Symptom] --> B[Guided Diagnosis]
  B --> C[Problem Category]
  C --> D[Best OS Surface]

Phase 2 Task

Finalize the first 12 to 20 problem categories.

Each problem category should connect to:

  • founder language
  • stage fit
  • partner category
  • knowledge asset
  • event or network support
  • OS placement surface
  • country sensitivity