2. 1. The Quaestio Disputata: Structured Disagreement
The scholastic method centers on the quaestio disputata — the disputed question. A question is posed. Objections are listed (the strongest possible arguments against your position). Then the response. Then replies to each objection. The structure forces you to understand the opposing view better than its proponents do before you argue against it. This is the most underrated decision-making framework in existence.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Quaestio Disputata | The formal structure of scholastic inquiry: (1) State the question. (2) List objections (arguments against). (3) Present the sed contra (an authoritative argument for). (4) Give the respondeo (your answer with reasoning). (5) Reply to each objection individually. Every article in Aquinas’s Summa follows this structure. | Before making any major decision, formally steelman the opposing view. Don’t ask “why should we do this?” Ask “what are the strongest arguments that we should not do this?” Then address each one. The quaestio forces intellectual honesty because you must articulate the best case against yourself. | Amazon’s 6-page memo process is a secularized quaestio: state the proposal, present the data, address the counterarguments. The memo must anticipate objections and answer them before the meeting. Bezos reinvented the scholastic method for corporate strategy. |
| Objections (Videtur Quod) | “It seems that...” The objections come first, before the response. This is deliberate: you must understand the opposing position in its strongest form before you respond. Aquinas’s objections are often more eloquent and persuasive than those of the people he’s arguing against. | The pre-mortem. Before launching the product, write down the 5 strongest reasons it will fail. Make them as persuasive as possible. If you can’t articulate why your strategy might be wrong, you don’t understand your strategy. The objections are not obstacles to your thesis — they’re the map of its weaknesses. | The founder who pitches investors without being able to answer “why will this fail?” convincingly is doing bad scholastics. The founder who says “here are the three strongest reasons this won’t work, and here’s why I disagree with each” is doing Aquinas. Investors fund the second founder. |
| Sed Contra | “On the contrary...” A single, authoritative counterpoint to the objections, usually citing Scripture or Aristotle. The sed contra doesn’t prove the thesis — it establishes that a credible authority supports the opposite of the objections, creating the space for the full argument. | The reference customer, the precedent, the case study. Before arguing your full thesis, establish that someone credible agrees with the direction. “On the contrary, Stripe built a $95B company by doing exactly this.” The sed contra isn’t proof — it’s permission to take the argument seriously. | In a board meeting: “The objections to entering enterprise are valid. On the contrary, Figma, Notion, and Slack all started bottom-up and successfully went enterprise. Here’s why our case is analogous...” The sed contra earns the right to make the full argument. |
| Respondeo (I Respond That) | The main argument. It comes after the objections and the sed contra, meaning the reader already knows the counterarguments. The respondeo doesn’t ignore the objections — it incorporates them. The answer is richer because it has passed through the fire of opposition. | The strategy that has survived stress-testing. The product vision that has absorbed and addressed every major concern. The fundraising pitch that doesn’t avoid hard questions but incorporates them into the narrative. A respondeo that hasn’t been tested by real objections is not a strategy — it’s a wish. | The difference between a first-time founder’s pitch (enthusiasm without objection-handling) and a serial founder’s pitch (every concern already addressed within the narrative). The serial founder has internalized the quaestio: their respondeo pre-answers the questions the room will ask. |
3. 2. Distinctions: The Scalpel of Thought
The scholastics were obsessed with distinctions — precise differentiations between concepts that look similar but are fundamentally different. Essence vs. existence. Act vs. potency. Substance vs. accident. These distinctions aren’t pedantry. They’re precision instruments for cutting through confused thinking. Most startup arguments are actually failures of distinction.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Essence vs. Existence | Aquinas’s fundamental distinction: what something is (essence) is different from that it is (existence). You can understand what a unicorn is without it existing. Essence defines the thing; existence makes it real. In God alone are essence and existence identical. | The idea vs. the company. You can perfectly define what your product would be (essence) without it existing as a real business (existence). Most pitch decks describe essences. Investors fund existences. The gap between “this is what it would be” and “this exists and people pay for it” is the gap between essence and existence. | The beautifully designed Figma prototype that no one has built yet: pure essence, no existence. The ugly MVP with 10 paying customers: existence, however imperfect. Aquinas would tell you to ship the ugly MVP. Existence beats essence every time, because essence without existence is literally nothing. |
| Act vs. Potency | Aristotle via Aquinas. Act (actus) is what a thing currently is. Potency (potentia) is what it could become. A block of marble is potentially a statue. The sculptor brings it from potency to act. Change is the movement from potency to act. | Your product as it is (act) vs. your product as it could be (potency). Your market as it is (act) vs. your market as it could be (potency). The founder’s job is to actualize potential — to take the product from what it could be to what it is. But you must correctly assess the potency: not everything potential is actualizable. | The “TAM” slide in every pitch deck is a potency claim: the market could be $50B. The actual revenue is $50K. The gap between potency and act is the founder’s entire job. The danger: confusing what something could be with what it will be. Potency is possibility, not destiny. |
| Substance vs. Accident | Substance is what a thing essentially is. Accidents are properties that can change without changing what the thing is. A chair is substantially a seat; its color is an accident. You can change the color without changing the chair. But remove the seat and it’s no longer a chair. | What is your product substantially? What is its core, without which it’s not your product? Everything else is accidental — changeable without loss of identity. The UI is an accident. The pricing is an accident. The name is an accident. The core value proposition is the substance. Change the substance and you’ve pivoted. Change the accidents and you’ve iterated. | Slack’s substance: instant team communication with channels. Its accidents: the purple color, the loading messages, the specific emoji set. You could change every accident and it’s still Slack. If you removed channels and real-time messaging, it wouldn’t be Slack anymore. Know your substance; hold it sacred. Everything else is negotiable. |
| Per Se vs. Per Accidens | Something happens per se (by itself, essentially) or per accidens (accidentally, coincidentally). Fire heats per se. A musician being tall is per accidens. Confusing the two leads to false causal claims. | Did the growth happen because of your strategy (per se) or despite it (per accidens)? Did the feature drive retention, or did retention happen to coincide with the feature launch? Most startup success attribution is per accidens reasoning dressed up as per se analysis. | The startup that launched a new feature the same week a competitor went down, saw a surge in signups, and credited the feature. The growth was per accidens (competitor outage), not per se (feature launch). Misattributing per accidens causation as per se leads to repeating actions that didn’t actually cause the result. |
| Formal vs. Material Distinction | Scotus’s innovation: a distinction that exists in reality (not just in our minds) between aspects of the same thing. The intellect and the will are formally distinct in the soul even though they’re materially one. Some things are genuinely different aspects of a unity. | Product and distribution are formally distinct (they require different skills, different thinking) but materially one (a product without distribution is nothing; distribution without a product is empty). Engineering and design are formally distinct but materially one. The best founders hold both sides of formal distinctions simultaneously. | The classic startup debate: “are we a product company or a sales company?” Scotus would say: these are formally distinct (different activities) but materially one (the same company). The question is malformed. You’re both, simultaneously, and the formal distinction helps you organize without the material unity being lost. |
4. 3. The Four Causes: Why Things Exist
Aristotle’s Four Causes, systematized by the scholastics, remain the most complete framework for understanding why anything exists or happens. Modern thinking has collapsed “cause” into “efficient cause” (what made it happen), but the scholastics maintained all four — and the other three are where the strategic insight lives.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Material Cause | What is it made of? The bronze of a statue. The wood of a table. The material constrains what the thing can be — you cannot make a sword from cotton. | What is your product made of? What technology stack, what data, what infrastructure? The material cause constrains your product’s possibilities. A product built on a relational database has different potencies than one built on a graph database. The material shapes what’s possible. | Twitter’s original Ruby on Rails architecture (material cause) constrained its scaling potential. The “fail whale” was a material cause problem. The rewrite to JVM/Scala changed the material cause, which changed what the product could become. Your tech stack is not neutral — it’s a material cause that shapes everything downstream. |
| Formal Cause | What is its form or pattern? The blueprint of a house. The design of a chair. The formal cause is the organizing principle — the structure that makes the material into this thing rather than something else. Same material, different form, different thing. | Your product’s architecture, design system, information architecture, UX patterns. The formal cause is why Notion (blocks) feels fundamentally different from Google Docs (documents) even though both are “made of” the same material (text, databases, web technologies). The form is the competitive advantage. | Linear and Jira are made of the same material (issue tracking data, web tech). Their formal cause is completely different: Linear’s form is opinionated speed; Jira’s form is configurable comprehensiveness. Same material cause, different formal cause, different products, different markets. |
| Efficient Cause | What made it? Who or what brought it into existence? The sculptor is the efficient cause of the statue. The carpenter is the efficient cause of the table. This is what moderns usually mean by “cause.” | The founding team. The engineers. The designers. The people and processes that actually build the product. The efficient cause is your team’s capability. A brilliant formal cause (design) with a weak efficient cause (bad engineering) produces a beautiful prototype that doesn’t work. | Theranos had a compelling formal cause (blood tests from a finger prick) and a strong final cause (democratize diagnostics). The efficient cause (the actual engineering team and technology) couldn’t actualize the form. The formal cause was visionary; the efficient cause was inadequate. You need all four causes aligned. |
| Final Cause (Telos) | What is it for? The purpose, the end, the telos. The final cause of a knife is to cut. The final cause of an eye is to see. For Aquinas, the final cause is the “cause of causes” — the most important, because it determines everything else. You choose the material, form, and maker based on the purpose. | Why does your product exist? Not what it does — why it exists. The final cause determines every other decision: the tech stack (material), the design (formal), the team (efficient). Most startups can answer “what do we do?” Few can answer “why do we exist?” The ones that can have strategic clarity that the others lack. | Stripe’s final cause: increase the GDP of the internet. Not “process payments” (that’s the formal cause). The final cause explains why they build Atlas, Climate, Treasury, Issuing — products that make sense only if the telos is “make internet business easier,” not “process payments.” The final cause generates the roadmap. |
5. 4. Ockham’s Razor & Parsimony: Simplicity as Method
William of Ockham (c. 1287–1347) is the scholastic most people have heard of, thanks to his razor: “entities should not be multiplied beyond necessity.” But Ockham’s broader contribution was a radical commitment to parsimony — the idea that the simplest explanation sufficient to account for the phenomena is the best one. This principle is devastatingly useful for product thinking, architecture, and organizational design.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Ockham’s Razor | Entia non sunt multiplicanda praeter necessitatem. Do not posit more entities than necessary to explain the phenomena. If a simpler explanation works, prefer it. The razor cuts away unnecessary complexity. | Do not add features, abstractions, processes, or roles beyond what is necessary. If a startup can function with 5 people, don’t hire 10. If a product can solve the problem with 3 features, don’t build 10. If a process works without a meeting, don’t add the meeting. The razor applies to everything. | Craigslist: the simplest possible product for classified ads. No design, no features, no innovation for 25 years. It works. Billions in revenue. Ockham would be proud. Every feature Craigslist didn’t add is an entity that wasn’t multiplied beyond necessity. |
| Parsimony of Explanation | When multiple explanations fit the data, prefer the one with fewer assumptions. Not because the simpler one is definitely true, but because fewer assumptions means fewer potential points of failure. Parsimony is epistemically safer. | When diagnosing why growth slowed, prefer the simplest explanation. “The market is saturated” (one assumption) is more likely than “a competitor is running a secret campaign targeting our users through a network of influencers we can’t identify” (five assumptions). Check the simple explanation first. | The startup that explains declining growth with elaborate competitor theories when the real cause is that the onboarding flow is broken. Parsimony: check the simple stuff first. Is the signup form working? Is the email being delivered? Is the product loading? Most problems have simple causes. |
| Nominalism | Ockham’s radical position: universals don’t exist independently. Only individual things exist. “Redness” doesn’t exist — only red things. Categories are mental labels we impose on reality, not features of reality itself. This was philosophically revolutionary. | Market categories are not real things — they’re labels humans impose. “CRM” is not a thing that exists in reality. Salesforce, HubSpot, and Pipedrive exist. The category is a convenience, not a constraint. You don’t have to fit an existing category. Categories are nominalist fictions. | Notion doesn’t fit neatly into any category: is it a doc tool? A wiki? A database? A project manager? Nominalist answer: it doesn’t matter. Categories are labels, not essences. Notion is Notion. The customers don’t care which box analysts put it in — they care whether it solves their problem. |
| Plurality Should Not Be Posited Without Necessity | The positive formulation of the razor: you may posit plurality when necessary. Ockham’s razor doesn’t say “always choose the simplest.” It says “don’t add complexity unless you must.” Sometimes the complex explanation is correct. The razor tells you to justify every added complexity. | Microservices are warranted for a 500-person engineering org. They are not warranted for a 3-person startup. The complexity must be justified by necessity, not by fashion. Every architectural decision, every new tool, every new process must pass the test: “is this complexity necessary, or just comfortable?” | The 5-person startup with Kubernetes, a service mesh, 3 databases, a message queue, and a CI/CD pipeline more complex than their product. Ockham would ask: which of these entities are necessary? A monolith on a single server might serve the same purpose. Plurality posited without necessity. |
6. 5. The Problem of Universals: Categories & Abstractions
The great scholastic debate: do universals (like “redness,” “humanity,” “justice”) exist independently, or only in particular instances? This sounds abstract, but it’s the most practically important question in product strategy: is your category real, or are you building for a category that doesn’t actually exist?
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Realism (Universals Exist) | The realist position (Aquinas, Scotus): universals exist in things. “Humanity” really exists in every human. Categories are real features of reality, not just labels. There’s something genuinely shared by all members of a kind. | Market categories are real. “CRM” names a real pattern of need that exists across companies. If you’re a realist about your category, you believe the category pre-exists your product and you’re filling a real slot. This makes positioning easier but limits innovation: you’re constrained by the category’s existing definition. | HubSpot positioning itself as a “CRM”: a realist bet that the CRM category is real, that companies genuinely need this thing, and that HubSpot can provide a better version of it. The realist approach: the category exists; we’re the best instance of it. |
| Nominalism (Only Particulars Exist) | Ockham’s position: only particular things exist. “Humanity” is just a name for the collection of individual humans. There’s no shared essence — just a label we find convenient. Categories are human impositions, not discoveries. | Your market category doesn’t exist until you create it. There is no pre-existing slot for your product. You’re not filling a category — you’re creating one. The nominalist approach to positioning: name the thing, define the thing, own the thing. Category creation is a nominalist act. | Drift creating “conversational marketing”: a category that didn’t exist before they named it. Nominalist positioning: the category is a label Drift imposed on reality, and it stuck. The market didn’t have a “conversational marketing”-shaped hole. Drift carved the hole and put itself in it. |
| Conceptualism (The Middle Way) | Abelard’s compromise: universals exist in the mind as concepts abstracted from particular things. They’re not independent entities (contra realism) and not mere labels (contra nominalism). They’re genuine abstractions grounded in reality. | Categories are useful abstractions grounded in real patterns. “Project management tool” isn’t a metaphysical entity, but it’s more than an arbitrary label — it names a real cluster of needs. Use categories as thinking tools, not as prisons. They’re lenses, not laws. | The conceptualist approach to competitive analysis: your competitive set isn’t defined by which category Gartner puts you in (realism), and it isn’t meaningless (nominalism). It’s defined by which products your actual customers consider as alternatives. The category is a concept grounded in customer behavior. |
| The Porphyrian Tree | Porphyry’s tree of categories: a hierarchical classification from the most general (substance) down through genus and species to the individual. It’s the original taxonomy — the idea that everything can be placed in a nested hierarchy of increasingly specific categories. | Your market map. The hierarchy from broad category (software) to specific niche (AI-powered code review for Rust). Understanding where you sit in the Porphyrian tree of your market determines your positioning, your competitors, and your expansion path. You can move up the tree (generalize) or down (specialize). | Vercel in the Porphyrian tree: Infrastructure > Cloud > Frontend Cloud > Next.js hosting. Each level down narrows the market but deepens the value proposition. The strategic question: are you moving up the tree (becoming a general cloud platform) or down (becoming the best Next.js host)? Both are valid; they lead to different companies. |
7. 6. Natural Law & First Principles: Foundations That Hold
The scholastics believed that certain principles are self-evidently true and require no proof — they are the foundation on which all other knowledge rests. The natural law tradition (Aquinas) extended this into ethics: some things are right or wrong by their nature, knowable through reason alone. In startup terms: there are first principles that hold regardless of market conditions.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| First Principles (Per Se Nota) | Propositions that are self-evidently true and cannot be derived from anything more basic. “The whole is greater than the part.” “A thing cannot be and not be at the same time.” These are the bedrock of all reasoning. You don’t prove them — you reason from them. | Every business has first principles: value must exceed price. Acquisition cost must be less than lifetime value. People buy solutions to problems they have. You can debate strategy, features, and positioning endlessly, but these first principles are non-negotiable. Violate them and no amount of cleverness saves you. | The startup with negative unit economics that plans to “make it up in volume.” This violates a first principle: you cannot profitably sell something for less than it costs, regardless of quantity. First principles are not optional. They are the bedrock on which everything else stands or falls. |
| Natural Law | Aquinas: there are moral truths accessible through reason alone, without revelation. “Do good and avoid evil” is the first precept. These truths are universal, binding on all rational beings, and discoverable through the exercise of practical reason. | There are business practices that are universally right (transparency with customers, delivering promised value) and universally wrong (fraud, deception, knowingly shipping dangerous products), regardless of what the market rewards. Natural law in business: some things are wrong even if they’re profitable. | Dark patterns: they work (increase signups, reduce cancellations). They violate natural law (they deceive users). The scholastic position: the fact that something works does not make it right. The fact that it’s legal does not make it right. Some business practices are wrong by nature, and the organization that practices them corrodes from within. |
| Synderesis | The innate habit of the practical intellect that grasps the first principles of moral reasoning. Not a decision but a disposition — the pre-rational inclination toward good that makes moral reasoning possible. Everyone has it; not everyone listens to it. | Founder intuition. The gut feeling that something is wrong with the business model, the partnership, the hire. Not a logical argument — a pre-rational disposition toward the right answer. The best founders trust synderesis (their gut) while verifying it with data. The worst founders either ignore it (override intuition with spreadsheets) or worship it (never verify). | The founder who “just knew” the enterprise deal was wrong despite the revenue. The engineer who sensed the architecture wouldn’t scale before they could articulate why. Synderesis is the first signal. It should trigger investigation, not decision — but ignoring it is dangerous. |
| Practical Reason (Prudentia) | The intellectual virtue of knowing how to act well in particular circumstances. Not theoretical knowledge (knowing the truth) but practical knowledge (knowing what to do). Prudence is the “charioteer of the virtues” — it directs all other capacities toward the right action at the right time. | Strategic judgment. Knowing what to do next given the specific circumstances of your company, market, and team. This cannot be learned from books or frameworks alone — it’s developed through practice and reflection. Prudence is why experienced founders outperform first-timers: not more knowledge, but better practical judgment. | The decision to raise or bootstrap, to pivot or persist, to hire or wait — these are prudential judgments. No framework gives the answer. The founder must weigh the specific circumstances (prudence), apply first principles (synderesis), and make the call. Prudence is the meta-skill that makes all other skills useful. |
8. 7. Analogy of Being: Reasoning Across Domains
How do you apply knowledge from one domain to another? The scholastics developed a precise framework: analogy. Not metaphor (which is literary), not identity (which is logical), but analogy — a structured claim that two things share a proportional relationship without being identical. This is how the best founders transfer knowledge across domains.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Analogy of Proportionality | Two things are analogous when they share a proportional relationship, not an identical property. “Healthy” applies to a body and to food, but differently: a body has health; food causes health. The word is the same; the mode of application is proportionally different. | “Product-market fit” applies to a SaaS company and to a marketplace, but differently. In SaaS, PMF means users retain and pay. In a marketplace, PMF means both sides of the market show up repeatedly. The concept is analogous, not identical. Founders who treat PMF as univocal (meaning the same thing in every context) misapply it. | “Scaling” is analogous across domains. Scaling engineering (hire more engineers) is not the same as scaling sales (hire more salespeople) is not the same as scaling community (enable more user-to-user interaction). Same word, proportionally different meaning. The founder who “scales” community by hiring community managers is making a univocal error. |
| Analogy of Attribution | Multiple things are called by the same name because they all relate to one primary instance. “Healthy” applies primarily to the body, and secondarily to medicine (it causes health), urine (it indicates health), and climate (it preserves health). One primary meaning, multiple derivative meanings. | “Customer” means different things at different stages: the early adopter (primary: they define what customer means for you), the growth customer (derivative: they resemble the early adopter), the enterprise customer (further derivative: they share some needs but differ structurally). Understanding which meaning of “customer” you’re using prevents category confusion. | The startup that builds for “developers” without distinguishing: solo developers (primary instance), startup teams (attributed by resemblance), enterprise engineering orgs (attributed by partial overlap). “Developer” is not univocal. The solo developer and the enterprise architect share a name but not a buying behavior. |
| Equivocity (Same Word, Different Meaning) | When the same word is used for completely different things. “Bank” (financial institution) and “bank” (river bank) are equivocal — the shared word creates an illusion of shared meaning. Reasoning from equivocal terms is a fallacy. | Beware words that mean different things to different people in your organization. “Scale” to engineering means handle more load. “Scale” to sales means close more deals. “Scale” to the CEO means grow revenue. The word is equivocal. Meetings where people use the same word with different meanings produce agreement without alignment. | “We need to focus on growth.” Growth of what? Users? Revenue? Engagement? Market share? If the team leaves the meeting with 4 different interpretations of “growth,” you have an equivocity problem. The scholastic remedy: define your terms. Every meeting should start with shared definitions. |
| Univocity (Same Word, Same Meaning) | When a word means exactly the same thing in every application. “Triangle” means the same thing whether it’s made of wood or drawn on paper. Univocal terms enable precise reasoning because there’s no ambiguity. | Create univocal terms for your company’s key concepts. Define “active user” precisely. Define “churn” precisely. Define “lead” precisely. If these terms are univocal (same meaning for everyone), decisions become clearer. If they’re equivocal (different meanings for different teams), every conversation is confused. | Stripe’s internal glossary: precise, univocal definitions of business terms that everyone uses. When a Stripe employee says “GPV” (gross payment volume), everyone knows exactly what it means. This univocity of key terms eliminates an entire class of miscommunication that plagues less precise companies. |
9. 8. Virtue Ethics & Habitus: Character as Strategy
The scholastic approach to ethics is not rule-based (“follow these commandments”) but character-based (“become the kind of person who naturally does the right thing”). Virtues are habits — stable dispositions acquired through practice. This applies directly to organizational culture: culture is not a document. It’s a set of collective habits.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Habitus | A stable disposition that inclines a person to act in a certain way. Not a single action but a readiness for action. The courageous person doesn’t decide to be brave each time — they’ve developed a habitus of courage that makes brave action natural. Habitus is acquired through repeated practice. | Company culture is a habitus — a collective disposition to act in certain ways. You don’t build culture by writing a values document. You build it through repeated practice. If the team ships quickly, they develop the habitus of shipping. If the team debates endlessly, they develop the habitus of debating. Culture is what you repeatedly do. | Amazon’s “bias for action”: not a poster on the wall but a habitus developed through years of rewarding speed over perfection. New employees absorb the habitus by osmosis. The culture document describes the habitus; the habitus is built through daily practice. |
| The Cardinal Virtues | Aquinas’s four cardinal virtues: prudence (knowing what to do), justice (giving each their due), fortitude (courage in adversity), temperance (moderation in success). All other virtues are aspects of these four. | The four virtues of a founding team: Prudence (strategic judgment). Justice (fair dealings with co-founders, employees, and customers). Fortitude (persistence through the trough of sorrow). Temperance (not over-hiring when things go well, not panicking when they don’t). | The startup that succeeds long-term demonstrates all four: prudent strategic decisions, just treatment of stakeholders, fortitude through crises, and temperance in growth. The startup that fails usually lacks at least one: imprudent pivots, unjust cap tables, cowardice at the first downturn, or intemperate hiring. |
| The Mean Between Extremes | Aristotle via Aquinas: virtue is the mean between two vices. Courage is the mean between cowardice and recklessness. Generosity is the mean between stinginess and profligacy. The virtuous person finds the appropriate middle, which is not always the arithmetic center. | Every startup decision is a mean between extremes. Ship too fast: bugs and user distrust. Ship too slow: irrelevance. Raise too much: dilution and misaligned incentives. Raise too little: death by starvation. The founder’s job is to find the mean — and the mean shifts with context. | Hiring speed: the mean between “hire too fast and dilute culture” and “hire too slow and miss the market.” The mean for a pre-PMF startup is different from the mean for a post-PMF startup. The virtue is context-dependent, not a fixed rule. |
| Vice as Deficiency of Virtue | Vice is not the opposite of virtue but its deficiency or excess. The coward doesn’t lack bravery entirely — they have a deficiency of fortitude. The reckless person has an excess. Both are failures of the same virtue. Identifying the specific deficiency or excess is the first step to correction. | Organizational dysfunctions are deficiencies or excesses of good things. Too much process (excess of order) or too little process (deficiency of order). Too much consensus (excess of democracy) or too little input (deficiency of democracy). Diagnosing whether the problem is excess or deficiency changes the remedy entirely. | The startup that “moves fast and breaks things” to the point of shipping broken products has an excess of speed (recklessness). The cure is not to stop shipping (the other extreme) but to find the mean: ship fast with adequate quality. The diagnosis (excess, not wrong direction) determines the fix (moderate, not reverse). |
10. 9. Double Effect & Moral Reasoning: Navigating Trade-offs
The Principle of Double Effect (Aquinas, Summa Theologiae II-II, Q.64, A.7) is one of the most practically useful moral frameworks ever developed. It addresses the hard cases: when an action has both good and bad effects. Not every trade-off is a dilemma. The scholastics developed precise criteria for when a bad side effect is permissible — and when it isn’t.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Principle of Double Effect | An action with both good and bad effects is permissible when: (1) the action itself is not intrinsically wrong, (2) the good effect is intended, not the bad, (3) the bad effect is not the means to the good effect, (4) the good effect is proportionate to the bad. All four conditions must be met. | Every major business decision has side effects. Layoffs (good: company survives; bad: people lose jobs). Price increases (good: sustainable business; bad: some customers leave). The double effect framework: is the decision itself ethical? Is the good effect the intent? Is the harm a side effect, not the mechanism? Is the good proportionate to the harm? | Laying off 20% of the company to avoid bankruptcy: (1) layoffs are not intrinsically wrong, (2) the intent is company survival not hurting people, (3) the savings come from reduced payroll not from the suffering of those laid off, (4) company survival is proportionate to the harm. Permissible under double effect. Laying off 20% to boost stock price for a bonus: fails condition (2) — the intent is personal gain. |
| Intrinsic vs. Extrinsic Evil | Some actions are intrinsically wrong regardless of consequences (the scholastic position). Others are wrong because of their circumstances or consequences (extrinsically wrong). The distinction matters: you cannot do an intrinsically evil act even for a good result. | Some business practices are wrong regardless of outcome: fraud, deception, knowingly shipping dangerous products. Others are contextually wrong: aggressive pricing that harms a specific customer, features that have unintended negative effects. The first category is non-negotiable. The second requires judgment. | Theranos lying about test results: intrinsically wrong (deception about medical data) regardless of the intention (democratize healthcare). No good outcome justifies the means. Contrast: a startup choosing not to support legacy browsers, causing some users inconvenience. Contextually unfortunate, not intrinsically wrong. The scholastic distinction prevents false equivalence. |
| Proportionality | The good achieved must be proportionate to the harm tolerated. You cannot cause massive harm for trivial benefit. The proportion is not just about magnitude but about kind: some harms (to human life, dignity) outweigh almost any benefit. | Is the business value proportionate to the cost? Crunching the team for a week to hit a launch date might be proportionate. Crunching for six months to add a nice-to-have feature is disproportionate. The proportionality test: would a reasonable person say the benefit justifies this specific cost? | The social media company that optimizes engagement knowing it harms teenage mental health: the business benefit (ad revenue) is not proportionate to the harm (psychological damage to minors). A scholastic analysis would say: the bad effect is disproportionate to the good. The algorithm must be changed. |
| Cooperation in Evil (Material vs. Formal) | Formal cooperation: you share the evil intent. Material cooperation: you provide a tool or resource that someone else uses for evil, without sharing their intent. Formal cooperation is always wrong. Material cooperation requires proportionality analysis. | Your platform is used for spam (material cooperation: you didn’t intend it). Your growth hack deliberately uses dark patterns (formal cooperation: you intend the deception). The distinction matters: platform misuse is a problem to solve; intentional dark patterns are a choice to stop making. | AWS hosting a company that turns out to be fraudulent: material cooperation (AWS didn’t intend or facilitate the fraud). AWS actively helping a company it knows is fraudulent: formal cooperation. The remedy for material cooperation is vigilance and moderation. The remedy for formal cooperation is cessation. |
11. 10. Faith & Reason: Conviction Under Uncertainty
The central scholastic project was harmonizing faith and reason — showing that belief and logic are not enemies but complements. The startup parallel is exact: every founder operates on a mix of conviction (faith in the vision) and evidence (data from the market). The scholastics spent centuries working out how to hold both without either collapsing into the other.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Fides Quaerens Intellectum | “Faith seeking understanding.” Anselm’s motto. You begin with belief (the vision), then seek rational understanding of why it’s true. Faith is not the absence of reason — it’s the starting point from which reason proceeds. You believe first, then understand. | The founder’s conviction comes before the data. You believe the market exists, then seek evidence. You believe the product will work, then build and test. Conviction under uncertainty is the starting point, not the conclusion. The data comes later to confirm, refine, or disprove — but without the initial conviction, you never start. | Brian Chesky believed strangers would sleep in other strangers’ homes. Zero data supported this. The conviction preceded the evidence. The evidence (user behavior on Airbnb) eventually confirmed the faith. But without the initial, data-free conviction, the experiment never happens. Faith seeking understanding. |
| The Preambles of Faith (Praeambula Fidei) | Aquinas: certain truths are accessible through reason alone, and these serve as preambles to faith. God’s existence can be known through reason; the Trinity requires revelation. The preambles are the rational foundation on which faith builds. | Certain things about your market are knowable through research (preambles): market size, competitor landscape, technology trends. Others require conviction (faith): that your specific approach will win, that the timing is right, that your team can execute. Good founders distinguish between what they can know and what they must believe. | The preambles of the Airbnb pitch: people travel (knowable), hotels are expensive (knowable), people have spare rooms (knowable). The faith: strangers will trust each other enough to share living space (not knowable in advance, required conviction). The preambles justified the experiment; the faith justified starting it. |
| Negative Theology (Via Negativa) | The idea that we can know God better by saying what God is not than by saying what God is. God is not finite, not material, not changeable. This “way of negation” is epistemically more reliable than positive claims, because our concepts are too limited for the subject. | Define your product by what it is not. Especially useful for novel products that don’t fit existing categories. “We are not a CRM. We are not a project management tool. We are not a database.” Each negation eliminates a misconception and narrows the listener toward understanding. | Notion’s early positioning was essentially via negativa: “not quite a wiki, not quite a doc tool, not quite a database, not quite a project manager.” The negative definitions were clearer than any positive one, because the product was genuinely novel. Sometimes the via negativa is the only honest approach. |
| Credo Ut Intelligam | “I believe in order that I may understand.” Understanding follows from commitment. You cannot understand from the outside. The act of believing (committing, investing) changes your epistemic position — it gives you access to knowledge that observation alone cannot provide. | You understand the market only after you’re in it. Reading reports is observation. Shipping a product is commitment. The founder who ships learns things about the market that the analyst who observes never can. Understanding follows from commitment. You must believe (ship, sell, invest) before you can understand. | The difference between a market analysis and a launched product: the analysis says “this market exists.” The launched product says “here is what this market actually buys, how they buy it, what they pay, and what they complain about.” The second kind of knowledge is only available through commitment. Credo ut intelligam. |
12. 11. The Summa Method: Systematic Knowledge Architecture
Aquinas’s Summa Theologiae is not just a work of theology — it’s a masterclass in knowledge architecture. It takes the entirety of Christian theology and organizes it into a navigable, hierarchical, cross-referenced system. The method itself — how to organize complex knowledge into a usable structure — is the final scholastic gift to founders.
| Concept | Scholastic Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| The Summa Structure | Hierarchical organization: Parts > Questions > Articles. Each article follows the quaestio form. The entire work is navigable from any entry point. You can read the whole or jump to any specific question. The architecture serves both comprehensive study and targeted reference. | Your documentation, knowledge base, and internal wiki should follow the Summa pattern: hierarchical, navigable from any entry point, and structured so each unit is self-contained but connected to the whole. The best internal docs are small Summae: organized knowledge that can be read linearly or accessed randomly. | Stripe’s documentation is the closest thing to a software Summa: hierarchical (concepts > products > APIs), each article is self-contained, navigable from any point, and cross-referenced. It serves both learning (read the whole section) and reference (jump to the specific method). Aquinas would recognize the architecture. |
| The Commentary Tradition | Scholastics spent centuries writing commentaries on Aristotle, Lombard’s Sentences, and each other. The commentary tradition meant that knowledge accumulated: each generation built on the previous. The format was standardized, so ideas could be compared, critiqued, and synthesized across centuries. | Internal RFCs, ADRs (Architecture Decision Records), post-mortems as a commentary tradition. Each document builds on previous ones, references them, and adds new knowledge. Over time, the accumulation of commentaries becomes the company’s institutional intelligence. Without a commentary tradition, each team starts from zero. | Google’s design docs tradition: each doc follows a standard format, references previous decisions, and becomes part of the permanent record. New engineers read the commentary tradition (old design docs) to understand why the system is the way it is. This is exactly how scholastic students read the commentaries: to understand the accumulated reasoning. |
| Sic et Non (Yes and No) | Abelard’s method: collect contradictory statements from authorities on the same question. Don’t resolve them — present them side by side. Let the contradiction itself be instructive. The tension between authorities generates deeper understanding than either authority alone. | Collect contradictory advice. “Move fast and break things” vs. “go slow and get it right.” “Focus on one thing” vs. “diversify your bets.” Both are true in context. The Sic et Non approach: present the contradiction, understand the conditions under which each is true, and develop judgment about which applies to your situation. | Paul Graham says “do things that don’t scale.” Reid Hoffman says “blitzscale.” Both are right. The Sic et Non: these are true under different conditions (pre-PMF vs. post-PMF). The contradiction isn’t a problem to resolve but a tension to navigate. Wisdom is knowing when each applies. |
| Quod Nihil Scitur (That Nothing Is Known) | Francisco Sanches’s late-scholastic work arguing for radical skepticism about the limits of human knowledge. Not nihilism — a sober assessment that our knowledge is always partial, always provisional, always subject to revision. Intellectual humility as a methodological principle. | You know less than you think. Your market research is incomplete. Your user interviews are biased. Your metrics are proxies, not truth. The scholastic reminder: all knowledge is partial. Hold your convictions firmly (fides) while acknowledging their provisionality (quod nihil scitur). Certainty is not available to founders. Informed conviction is. | The founder who says “I believe this is the right direction, and here’s what would convince me I’m wrong” has absorbed the scholastic lesson. They hold conviction and humility simultaneously. They have faith seeking understanding, tempered by the awareness that nothing is known with certainty. |
13. Synthesis: The Scholastic Founder’s Toolkit
The scholastic mental models cluster into three meta-skills:
1. Clarity of Thought
- Make distinctions — essence vs. existence, substance vs. accident, per se vs. per accidens. Most startup confusion is a failure of distinction.
- Define terms univocally — if your team uses the same words with different meanings, you have equivocity. Define before you debate.
- Use the Four Causes — for any product or decision, ask: what is it made of (material)? What form does it take (formal)? Who builds it (efficient)? Why does it exist (final)?
- Apply the razor — don’t add complexity beyond necessity. Every feature, process, and hire must justify its existence.
2. Rigor of Argument
- Use the quaestio — for every major decision, list the strongest objections first. Address each one. If you can’t answer the objections, you haven’t earned the decision.
- Reason by analogy, not metaphor — when transferring knowledge across domains, be precise about what is proportional and what is not.
- Collect contradictions (Sic et Non) — when experts disagree, the disagreement itself is the most valuable data.
3. Wisdom in Action
- Develop prudence — the meta-virtue of knowing what to do in particular circumstances. This comes only from practice.
- Hold conviction and humility together — believe firmly (fides), seek understanding (intellectum), and acknowledge the limits of your knowledge (quod nihil scitur).
- Navigate trade-offs with double effect — when an action has both good and bad consequences, apply the four conditions. Not every trade-off is a dilemma; most have a right answer.
- Build habitus, not rules — culture is not a document. It’s the set of habits your team practices daily. Build the habits and the culture follows.
The scholastics spent five centuries doing nothing but thinking clearly about hard problems. Their methods — distinctions, quaestiones, analogies, the via negativa, the Four Causes, the razor — are the most battle-tested intellectual tools available. They were designed for questions where the stakes were infinite (the soul). Applied to questions where the stakes are merely financial (the startup), they provide an unfair advantage: the ability to think more clearly than your competitors about the same information.