Founder's Operating System
Why source-backed matters
What’s inside
Napoleon Hill — Definite Chief Aim
Hill's first and most important principle: define a Definite Chief Aim — a single, written, dated, measurable major purpose. Without one, energy scatters across competing priorities and nothing compounds. The Chief Aim must be specific (not 'be successful' but 'ship product X by date Y, reaching N users at Z revenue'). Read it twice daily, morning and night, until belief is absorbed at the subconscious level. Every decision the founder makes — what to build, who to hire, what to refuse — is filtered through whether it advances the Chief Aim. Hill argues that the moment you commit a goal to writing with this specificity, the subconscious begins routing opportunities, people, and resources toward it. The corollary: any goal that cannot survive being written down with date and metric is not a real goal — it's a wish. The Chief Aim sits upstream of all other decision frameworks; OOC/EMR, prioritization matrices, and OKRs are tools for ladder-ing tactical work to it.
Warren Buffett — Owner's Manual
Buffett's operating principles for capital allocation, distilled: (1) Think in decades, not quarters — the discount rate on long-term compounding overwhelms short-term optimization. (2) Stay inside your circle of competence; the size of the circle matters far less than knowing where its edge is. (3) Price is what you pay, value is what you get — a great business at a fair price beats a fair business at a great price. (4) The market is a manic-depressive: serve you, don't be guided by you. (5) Reputation takes 20 years to build and 5 minutes to destroy — if you think about that, you'll do things differently. (6) When you find a true conviction position, concentrate; diversification is protection against ignorance. For founders: this maps to product decisions (decade-long bets), market choice (circle of competence), and capital allocation (concentrate on what's working — kill what isn't).
Charlie Munger — Mental Models Worth Memorizing
Munger's lattice of mental models — a toolkit for thinking from multiple disciplines simultaneously. Core ones every founder should internalize: (1) Inversion — instead of 'how do I succeed?', ask 'how do I guarantee failure?' and avoid those things. (2) Incentives drive behavior — never ask why someone is acting against their interest; you've misunderstood the incentive. (3) Lollapalooza effects — when multiple psychological biases stack in the same direction, outcomes go nonlinear (bubbles, panics, cult products). (4) The Iron Law of opportunity cost — every yes is a no to everything else. (5) Avoid the social-proof trap — most people lose money in markets because they're doing what everyone else is doing. (6) Be radically honest about what you don't know. Munger: 'Acknowledging what you don't know is the dawning of wisdom.' For founders, inversion is the most underused: instead of asking how to win, list every way the company could die and design to prevent each.
Paul Graham — Do Things That Don't Scale
Graham's anti-pattern correction for early-stage founders: the biggest mistake new startups make is waiting for users to discover them. Instead, do unscalable things in the first 100 users. Recruit them manually, one at a time. Deliver insanely better service than would ever scale. Reply to every email personally. Hand-hold every onboarding. The objection — 'that won't scale' — misses the point: you're not trying to scale yet, you're trying to learn what makes users love the product and figure out what to scale later. Airbnb founders flew to NYC and personally photographed listings. Stripe co-founders installed their own product on customers' servers. The transition from 'doing things that don't scale' to 'building things that do' happens organically when you've learned what to automate. The hidden benefit: this period produces the customer-research density that informs every product decision for the next five years.
Tony Robbins — OOC/EMR Decision Protocol
OOC/EMR is Robbins' six-step protocol for any non-trivial decision: Outcomes — Options — Consequences — Evaluate — Mitigate — Resolve. Start with Outcomes: name the OUTCOME you actually want (not the tactical question). Rank your top 3 outcomes; this surfaces hidden priorities. Options: generate at least 5 paths to the top outcome, including absurd ones (creativity unlocks). Consequences: for each option, write 1st-, 2nd-, and 3rd-order effects (most bad decisions are made by ignoring 2nd-order effects). Evaluate: score each option against the ranked outcomes. Mitigate: for the top option, list every downside and design a mitigation plan. Resolve: commit, write the decision down with date, set review milestones. The discipline isn't in the steps individually — it's in slowing down enough to do all six BEFORE committing. Founders who skip steps 4-5 reliably underestimate consequences. The protocol pairs perfectly with a Chief Aim: every Outcomes step ladders back to the singular major purpose.
How installing a Knowledge Pack works
Sources & further reading
Related packs & reading
Your AI shouldn’t start from zero.
Install this pack and your MIND begins smart — then every answer is grounded in your own knowledge graph.
Try MIND free →