Mishneh Torah, Sabbath 26

Hook: The "Fixed" Mindset Trap

As a founder, you constantly battle "feature creep" and "process bloat." You have tools—software, workflows, team structures—that were meant to be assets but have become immovable anchors. You treat them like furniture that can’t be moved because you’ve forgotten they’re just tools. The Rambam’s laws of Muktzeh (set-aside objects) on the Sabbath offer a brutal diagnostic for your operational efficiency.

Text Snapshot

"An exception is made regarding the upper weaver's beam and the lower weaver's beam. They may not be carried, because they are [usually] fixed [within the loom]... Similarly, the pillars [of the loom] may not be moved, lest one fill the hole [in the earth created when they are removed]." Mishneh Torah, Sabbath 26:1

Analysis: 3 Decision Rules

1. Utility vs. Permanence: If an asset is "fixed" (like the weaver’s beam), it ceases to be a tool and becomes part of your "infrastructure." You can’t pivot if your tools are bolted to the floor. If you can’t move it, it owns you.
2. The Risk of Optimization: The text warns against moving pillars "lest one fill the hole." Sometimes, fixing a "small" inefficiency (filling a hole) leads to a larger, forbidden labor (rebuilding the floor). Don't break your core architecture to fix a minor bug.
3. Intent Defines Reality: A brick is a building material until you designate it for sitting; then it becomes furniture Mishneh Torah, Sabbath 26:1. Your team’s output is defined by how you categorize it. Stop letting "legacy" projects clog your capacity; categorize them clearly as "junk" or "utility" and act accordingly.

Policy Move

The "Unbolt" Audit: Once a quarter, identify one "fixed" process—a meeting, a reporting structure, or a legacy stack component—that you treat as non-negotiable. Force yourself to "unbolt" it for a week. If operations don't collapse, decommission it.

Board-Level Question

"Are we holding onto this resource because it’s still the best way to achieve our objective, or because it’s 'fixed' into our current workflow and we’re afraid of the friction required to move it?"

Takeaway

In the month of Tamuz, a time of transition, remember: If you can't move it, you can't optimize it. Stop managing your "pillars" and start managing your "tools." If it’s not serving the mission, it’s just clutter.