Study these problems related to founding or starting something to have a taxonomy of types of peoples and how to solve them.
## Clipboard
## The landscape
Founders face recurring structural problems that show up across industries, missions, and organization types. These problems are structural in the sense that they're properties of the situation, not the founder — which means naming them helps you diagnose what you're actually up against and reach for the right playbook. Below is a reasonably comprehensive taxonomy, organized by the phase they tend to bite in.
## Problems about getting started
Cold-start problem. The value of your thing depends on users/participants/contributors that don't exist yet. Marketplaces, social networks, community currencies, dating apps, multi-sided platforms. Classic fix: subsidize one side, hand-pick early supply, or start in a niche where the network can be tiny and still useful (the "hard side first" and "come for the tool, stay for the network" playbooks).
Chicken-and-egg problem. A special case of cold-start where two things need each other simultaneously — merchants won't accept the currency without customers, customers won't hold it without merchants. Often resolved by a single anchor participant (a big employer, a big merchant) who commits first and pulls the other side.
Blank-page problem. Nobody is asking for this; no template exists; you're not sure what you're even building. Discovery-mode founders face this acutely. Fix is process, not insight: cheap experiments, rapid cycles, time-boxed exploration, writing to think.
Credentialing / legitimacy problem. Nobody takes you seriously because you're unknown, young, or operating outside established institutions. Matters most in fields where trust is load-bearing (health, finance, policy, research). Fix: borrow legitimacy via advisors, affiliations, publications, or accomplishments that cash out as proof-of-seriousness.
## Problems about demand
Substitution problem. Users can trivially switch to an alternative, so your thing has to dominate on every dimension or it gets abandoned. Decaying currencies hit this (swap to dollars). So do most crypto tokens, most new social networks, most productivity tools. Fix: either remove the substitute (regulatory moat, network lock-in), or bundle something the substitute can't match, or start in a closed domain where substitution isn't available.
Painkiller-vs-vitamin problem. Is your thing solving an acute pain people already feel, or a diffuse improvement nobody's demanding? Vitamins are much harder to sell. Most "improve society" projects are vitamins; the founder has to either reframe the problem as acute or accept a much longer and weirder sales cycle.
Demand-hallucination problem. You convinced yourself there's demand based on polite feedback, surveys, "I'd totally use that" comments, or your own intuition. The only real signal is behavior — payments, commitments, repeat usage. Fix: design experiments that force people to reveal preferences, not report them.
Jobs-to-be-done problem. Users aren't buying features; they're hiring your product to do a job. If you misidentify the job, you'll build the wrong thing even if the demand is real. Fix: interview for the underlying job, not the stated preference.
## Problems about the market and competition
Incumbent problem. A big player could crush you if they noticed. Usually less acute than founders fear (incumbents are slow, distracted, have internal politics) but real in narrow sectors. Fix: be too small to matter until you're too big to stop, pick fights incumbents can't fight (structural constraints like regulatory, business-model, or cannibalization), or just avoid.
Commodity problem. The thing you're building has no durable differentiation; competitors will arrive and drive margins to zero. Common in software without network effects, in physical goods without brand, in services without proprietary insight. Fix: find or build a moat (network effects, switching costs, brand, proprietary data, regulatory capture, scale economies).
Timing problem. The idea is right but the world isn't ready — the enabling technology is too expensive, the regulatory environment too hostile, the user behavior too unfamiliar. Or the opposite: the window already closed. "Right but early" and "right but late" both kill companies. Fix: Pay attention to enabling conditions more than to the idea itself. Ask what has to be true for this to work, and whether those things are true now.
Crowded-space problem. Fifty people are working on this. The market is real but differentiation is brutal and capital efficiency collapses. Usually worth avoiding unless you have a genuinely distinct angle.
## Problems about the organization itself
Founding team problem. Wrong co-founder composition — missing skills, mismatched values, unclear decision rights, incompatible work styles. The highest-base-rate killer of early-stage organizations. Fix: pick co-founders the way you'd pick a spouse, with explicit conversations about vision, equity, exit conditions, and failure modes.
Solo-founder problem. No co-founder means no sparring partner, no emotional support infrastructure, no skill complementarity, no one who notices when you're wrong. Survivable but strictly harder. Fix: build a pseudo-team via advisors, a co-founder-in-spirit relationship, or a structured accountability partner.
Mission drift problem. The organization gradually optimizes for something other than its stated purpose — usually survival, prestige, or donor/investor preferences. Fix: explicit mechanisms (mission lock-ins, board composition, charter constraints) plus cultural vigilance. More acute in nonprofits, mission-driven orgs, and anywhere the paying customer isn't the ultimate beneficiary.
Principal-agent problem. Once you hire, employees' incentives aren't automatically aligned with the org's. At scale this becomes most of what management is. Fix: compensation design, selection, culture, measurement. No clean solution.
Founder-bottleneck problem. Everything routes through the founder, so the organization can't grow faster than the founder's personal bandwidth. Fix: systematize, document, delegate, and accept that some quality will degrade in exchange for scale.
## Problems about money
Funding-model problem. The natural revenue or funding source for the thing you want to build doesn't exist, doesn't want to fund your version, or distorts what you build. Nonprofits face this with grant-chasing; startups face it with VC incentives that force growth over viability. Fix: pick the funding model first and work backward; or structure to be fundable by more than one kind of capital.
Runway problem. You don't have enough money to reach the next milestone, and you're burning faster than you're learning. Most common failure mode of early-stage orgs. Fix: brutal prioritization, cheaper experiments, earlier revenue, or raising more.
Unit-economics problem. You're growing but losing money on each unit, and no realistic scale closes the gap. Fix: find the leverage point (cost structure, pricing, retention, expansion revenue) that makes the math work, or accept the business doesn't.
Premature-scaling problem. You raised or grew before product-market fit, so you now have a large organization optimizing for the wrong thing and can't course-correct quickly. Fix: don't. Stay small until the core loop works.
## Problems about distribution
Distribution problem. You built the thing and nobody knows. The painful surprise for most technical founders: distribution is usually harder than building. Fix: distribution-first thinking — pick problems where you have unfair channels, or spend half your time on how people will find and adopt the thing.
Adoption-friction problem. Switching costs, learning curves, or integration pain are too high relative to perceived benefit. Users rationally don't bother. Fix: radically reduce the first-use cost ("time to first value"), integrate into existing workflows, or change the framing so the benefit feels larger.
Trust problem. Even motivated users won't adopt because they don't trust you with their money, data, health, or reputation. Fix: credibility signals, conservative early scoping, starting with trust-proxy customers, regulatory compliance as a feature.
## Problems about the problem
Well-posed-problem problem. The thing you're trying to solve isn't a well-defined problem — it's a cluster of related frustrations with no natural unit of progress. "Improve epistemics" is like this. So is "help people live better lives." Fix: force a well-posed subproblem, accept you're making the problem up somewhat, and be honest that you're picking a specific bet.
Neglectedness problem. If the problem is real and tractable, why isn't someone already solving it? Usually there's a reason (regulation, incentives, coordination, capital intensity, taste), and understanding the reason tells you what you're actually up against. Conversely, if the problem is genuinely neglected, that's often an important clue about why it's hard.
Measurement problem. You can't tell if you're making progress, so you can't iterate, can't attract resources, and can't tell if you should stop. Common in research, policy, long-feedback-loop work, and anything touching "impact." Fix: invent proxies, accept their imperfection, and triangulate across multiple noisy signals.
Counterfactual-impact problem. Even if the problem is real, your specific contribution might be small because the work would happen without you (replacement effect, parallel efforts, natural progress). Fix: pick problems where you're genuinely scarce, where your particular angle is unusual, or where being earlier or better materially changes the outcome.
Theory-of-change problem. You have activities but no articulated causal chain from activities to the outcomes you care about. So you can't tell which activities matter and you drift. Fix: write the chain down, identify the weakest link, and work backward from the outcome.
## Problems about systems and coordination
Coordination problem. Your thing only works if many independent actors move together — adopting a standard, switching platforms, changing norms. Each actor waits for others. Fix: tip the system via a focal point, a large anchor commitment, a subsidy, or a forcing function.
Collective-action problem. Everyone is individually better off free-riding, even though everyone would collectively be better off contributing. Unions, climate action, public goods, some forms of information commons. Fix: usually requires institutional design (enforcement, selective incentives, small-group dynamics) rather than just persuasion.
Unilateralist's-curse problem. In a group of people deciding whether to take an action with big potential downside, the most optimistic person will take it — which means decisions skew toward recklessness. Relevant for anyone building powerful technology or making public interventions. Fix: explicit deference to cautious members, deliberate consultation before action, and cultural norms that slow things down.
Feedback-loop problem. The consequences of your decisions take years to materialize, so you can't learn fast. Strategy in general has this; so does deep research, policy, and mission-driven work. Fix: proxies, red-teaming, and deliberate humility about claims you can't yet verify.
## Problems about the founder
Conviction problem. You don't believe in the thing enough to push through the hard parts, or you believe too much and can't update when you're wrong. Both failure modes are common; the right level of conviction is one of the harder meta-problems in founder psychology. Fix: precommit to update on specific signals so you can't confuse conviction with identity.
Attention problem. You're working on three things because each seems important, and you're making linear progress on none of them instead of exponential progress on one. Fix: pick; accept the opportunity cost; revisit on a calendar, not whenever doubt spikes.
Burnout problem. Founder morale is a depleting resource, and most projects take longer than the founder's initial emotional runway. Fix: sustainable pace, real rest, social infrastructure outside the project, and a theory of recovery not just work.
Identity-entanglement problem. The project and your self-worth fuse, which makes you unable to kill the project when you should, and makes every setback feel existential. Fix: deliberate separation — "I am not my project" as a practice, not a slogan.
## How to use the taxonomy
Most real projects have several of these simultaneously, and the ones that kill you are usually not the ones you're thinking about. The practical move is to take whatever you're building and walk the list, flagging which apply with what severity. That gives you a risk register, which is what most founders don't have and what usually separates the ones who survive from the ones who don't.
Worth naming: these aren't independent — cold-start often co-occurs with trust problems and distribution problems; mission drift often co-occurs with funding-model problems and measurement problems. Mapping the correlations is part of the diagnostic.