Mishneh Torah, Testimony 2-4

Hook

You’re a founder. You live in a fog of war. Every day, you’re bombarded with conflicting reports: sales forecasts from your team that don't quite align with market intelligence, customer feedback that pulls in opposite directions, engineering estimates that feel… optimistic. You need to make snap decisions, often with incomplete, messy, or even contradictory data. The pressure is immense. Do you halt progress to pursue perfect clarity, risking market opportunity? Or do you push forward with what you have, risking a costly misstep? This isn’t just about speed; it's about integrity. It’s about building a company that values truth, but understands that "truth" has different thresholds depending on the stakes. This ancient text from Mishneh Torah offers a surprisingly sharp, ROI-minded framework for navigating this exact dilemma: how to assess the reliability of information when the stakes range from a minor miscalculation to a catastrophic failure. It teaches us not just what to look for, but how much to demand, and when pragmatism must trump exhaustive interrogation.

Text Snapshot

Mishneh Torah, Testimony 2-4, meticulously details the laws of witness testimony. It distinguishes between chakirot (core interrogations: "where and when exactly"), derishot (fundamental questions clarifying the act), and bedikot (additional, non-essential questions like "clothing color"). The text dictates that minor discrepancies in chakirot or derishot invalidate testimony, while "I don't know" for bedikot is acceptable. Crucially, it sets different standards for capital cases (requiring extreme precision) versus monetary cases (allowing more flexibility to "prevent loans from being given"). It also addresses reasonable human error, the combining of testimonies, and the non-retractability of statements.

Analysis

Insight 1: The Hierarchy of Data: Core vs. Peripheral

Founders often drown in data, treating all information with equal weight. This text demands a sharper approach. It differentiates between chakirot and derishot (core facts — the "who, what, when, where, how" of an event) and bedikot (peripheral details). The rule is clear: "With regard to the chakirot and the derishot, if one witness gave specific testimony and the second said: 'I do not know,' their testimony is of no consequence." If your core data points – your market size, your CAC, your burn rate – are not corroborated or are met with "I don't know" from a key source, that information is, as the text states, "of no consequence." It cannot form the basis of a decision.

However, for bedikot, the standard is different: "With regard to the bedikot, by contrast, even if both of them say: 'I don't know,' their testimony is allowed to stand." This is gold. It means you don't need absolute clarity on every single detail to move forward. If you're launching a new feature, and your team can't agree on the exact shade of blue for a button (a bedika), but they agree on the core functionality and user need (chakirah), you proceed. The critical caveat, though, is that even for bedikot, outright contradiction is fatal: "If, however, they contradict each other, even with regard to the bedikot, their testimony is nullified." This means if one designer says the button is blue and another says it’s red, the whole testimony (the feature launch) is compromised until that contradiction is resolved. The lesson: prioritize corroboration on core facts. Tolerate ambiguity on peripheral facts, but never tolerate contradiction on any fact.

Insight 2: Precision & Pragmatism: The Zone of Reasonable Error

In the startup world, "perfect" is the enemy of "good." The text implicitly recognizes this by defining a "zone of reasonable error" for certain types of information. It acknowledges human fallibility without sacrificing the pursuit of truth. For instance, "If one witness says: 'It took place during the second hour of the day,' and the other says: 'It took place during the third hour,' their testimony is allowed to stand. The rationale is that it is common for people to err with regard to one hour." This is a crucial admission of pragmatism. A one-hour discrepancy in timing is acceptable. But push that further, and the testimony is nullified: "If, however, one says: 'It took place during the third hour,' and the other says: 'It took place during the fifth hour,' their testimony is nullified."

What's the business translation? When analyzing market trends, sales projections, or project timelines, a minor variance (e.g., a one-day difference in a launch date, or a 5% difference in projected revenue) might be acceptable. It's "common for people to err" within a small margin. However, a significant deviation (e.g., a two-hour difference, or a 20% revenue gap) indicates a fundamental flaw in understanding, invalidating the data as a basis for decision-making.

The text also introduces a concept of "evident to all" facts, where even a small discrepancy is unacceptable: "If one witness says: 'It took place before sunrise,' and the other says: 'It took place at sunrise,' their testimony is nullified. Even though the discrepancy between them is less than one hour, the matter is evident to all." This means some facts are so fundamentally clear and verifiable that any deviation, no matter how small, signals a problem. For a founder, this applies to non-negotiable, universally understood facts: legal compliance dates, critical security vulnerabilities, or the market price of a commodity. For these, the bar for accuracy is absolute.

KPI Proxy: Variance Tolerance for Critical Metrics. For core metrics (e.g., customer acquisition cost, churn rate, feature adoption), define acceptable variance ranges. If data points from different sources fall within a 1-hour/1-day equivalent "zone of reasonable error," proceed. If they exceed it, or contradict a "matter evident to all," invalidate the input and re-investigate.

Insight 3: The Urgency Tax: Rigor vs. Velocity

This is where the text gets fiercely ROI-minded. The most profound distinction is between capital cases (life-or-death, requiring ultimate precision) and monetary cases (financial, where speed and utility often outweigh forensic rigor). The Sages explicitly prioritize economic function: "Nevertheless, our Sages ordained that witnesses in cases involving financial law not be questioned or interrogated, lest this prevent loans from being given." And further: "According to Rabbinic Law, however, we decide cases involving financial matters on the basis of testimony recorded in a legal document even if the witnesses are no longer alive. This measure was enacted lest the alternative prevent loans from being given."

Think about that for a second. The system deliberately lowers the bar for proof in financial matters to keep the economy moving. It chooses velocity and transaction flow over perfect, exhaustive due diligence. For a founder, this is a mandate: not every decision warrants the same level of scrutiny.

• Capital Decisions (High Stakes): An M&A deal, a major funding round, a critical legal battle, a decision that could tank the company or risk its core values. These require chakirot and derishot level precision. You scrutinize every detail, demand full corroboration, and nullify information with any fundamental contradiction.
• Monetary Decisions (Everyday Operations): Product iterations, minor sales strategy adjustments, hiring for a non-executive role, tactical marketing campaigns. For these, you can operate with less perfect information. Rely on written reports, even if the "witnesses" (original data sources or experts) are no longer directly accessible. Accept "I don't know" on peripheral points. The goal is to "prevent loans from being given" – to avoid paralysis by analysis, to enable transactions, to keep the business flowing.

The implication is clear: founders must consciously categorize their decisions by their "capital" or "monetary" impact. Applying capital-level rigor to monetary decisions will kill your velocity. Applying monetary-level laxity to capital decisions will kill your company.

Policy Move

Decision-Making Rigor Matrix

Implement a "Decision-Making Rigor Matrix" that explicitly categorizes all significant company decisions into two tiers, mirroring the text's "capital" and "monetary" distinctions. This will standardize the expected level of data precision and validation.

1. "Capital Decisions" (High-Stakes): Decisions with irreversible, company-altering impact, high legal/financial exposure, or fundamental shifts in core strategy (e.g., M&A, Series B+ funding terms, legal compliance for critical regulations, core product pivot, executive hiring/firing).

   • Data Standard: Requires chakirot and derishot level rigor. All core factual claims (e.g., market size, valuation, legal liabilities, core user metrics) must be corroborated by at least two independent, qualified sources. Any "I don't know" on a core fact renders the data unusable. Any contradiction, even on bedikot (peripheral details), requires immediate investigation and resolution before proceeding. Due diligence processes must be exhaustive, and primary source verification is paramount.
   • Process: Mandate a "Decision Brief" signed off by relevant department heads, outlining data sources, corroboration status, identified contradictions, and a clear path to resolution for any discrepancies. External counsel/auditors are typically involved.

2. "Monetary Decisions" (Operational/Growth-Oriented): Decisions for day-to-day operations, product iterations, tactical marketing, sales pipeline management, non-executive hiring, minor feature releases. These are critical for growth but generally reversible or have contained risks.

   • Data Standard: Allows for more flexibility, reflecting the "lest this prevent loans from being given" principle. Core facts still need strong support, but "I don't know" on bedikot (e.g., exact user preference for a non-critical UI element) is acceptable. Minor discrepancies within a defined "zone of reasonable error" (e.g., 1-day variance in project timelines, 5% difference in A/B test results) are tolerated. Reliance on written reports, even from unavailable "witnesses" (e.g., past market research, archived customer feedback), is permissible.
   • Process: Standardized templates for "Decision Memos" that capture key assumptions, data points, and identified risks. Focus on speed and agility. Encourage rapid iteration and A/B testing rather than exhaustive pre-decision data collection for every detail.

KPI Proxy: Track "High-Stakes Decision Reversal Rate" (aim for near 0) and "Operational Decision Velocity" (optimize for speed). This policy ensures that the right level of scrutiny is applied to maximize both accuracy where it counts and agility where it drives growth.

Board-Level Question

"Given the inherent tension between market agility and data integrity, how are we systematically auditing our decision-making processes to ensure our teams are consistently applying the appropriate level of data rigor for 'capital' versus 'monetary' decisions, as informed by the principle of 'lest this prevent loans from being given'? What mechanisms are in place to prevent both paralysis by analysis on high-velocity decisions and catastrophic errors on high-stakes ventures?"

This question forces leadership to acknowledge that "truth" is not a monolithic concept in business. It challenges them to ensure that the organizational culture and processes are designed to differentiate between information requirements. Are teams clear on when to demand forensic-level precision (as in capital cases, where "contradictions... even with regard to the bedikot, their testimony is nullified") and when to accept "good enough" data for the sake of speed (as in monetary cases, where rigor is relaxed "lest this prevent loans from being given")? Without this clarity and a robust auditing mechanism, the company risks either grinding to a halt from excessive caution or making reckless, unforced errors on critical strategic moves.

Takeaway

The Torah isn't just moral philosophy; it’s a fiercely pragmatic operating manual for navigating uncertainty. By distinguishing between core facts and peripheral details, defining acceptable error margins, and adjusting rigor based on impact, it provides a timeless framework for founders to make smarter, faster, and more responsible decisions in the relentless pursuit of building something great. Don't just seek truth; understand its necessary thresholds.