Daily Mishnah · Startup Mensch · Bite-Sized
Mishnah Meilah 6:1-2
Hook: The Agency Trap
As a founder, you constantly delegate high-stakes decisions. The recurring nightmare? Your lead hire executes the letter of your instructions but ignores your strategic intent—or worse, acts on a personal whim that compromises your reputation. Do you own their mistake, or are they on their own?
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot: Mishnah Meilah 6:1
"If [the agent] did not perform his agency properly, the agent is liable... as once the agent deviates from his agency, he ceases to be an agent. If the homeowner said: 'Give meat to the guests,' and he gave them liver; or if he said: 'Give them liver,' and he gave them meat, the agent is liable."
Analysis: Decision Rules
- The Deviation Principle: If the agent shifts the category of the task, they forfeit their protected status. In business, if you task a dev with building a feature and they pivot to a different stack without consent, they are acting as an independent contractor, not your agent. You are no longer responsible for the outcome; they own the "misuse."
- Intent vs. Instruction: The text notes: "Even though the homeowner said: 'In my heart, my desire was only that he should bring me the item from that other place,'... the homeowner is liable." Rule: Externalized instructions override internal "strategic intent." If your brief is sloppy, you own the result.
- The Incremental Liability: When an agent exceeds instructions (e.g., giving guests three pieces of meat instead of two), liability is partitioned. The principal owns the authorized portion; the agent owns the unauthorized excess.
Policy Move: The "Scope-Lock" Protocol
Implement a "Task-Deviation Trigger" in your workflow. If an employee/agent realizes they cannot fulfill an instruction exactly as defined, the "agency" is considered suspended until a re-confirmation occurs. They must flag the deviation before acting to avoid being personally liable for the outcome.
Board-Level Question
"When our team executes a directive that misses the mark, are we seeing a failure of instruction clarity (the principal's fault) or a procedural deviation (the agent's fault), and how do we distinguish between the two in our post-mortems?"
Takeaway
Don't blame your team for failing to read your mind. If you give vague instructions, you own the consequences. If they deviate from clear instructions, they own the fallout. Clarity is the only buffer against liability.
derekhlearning.com