Sukkot: Building to Be Broken
We waste countless hours trying to engineer "bulletproof" strategies, rigid quarterly plans, and flawless long-term roadmaps. But when market conditions shift overnight, those heavy, permanent systems crack under pressure. This week, as we head into Sukkot, the holiday's ultimate symbol, a temporary hut open to the elements, offers a counterintuitive lesson in organizational agility: true stability comes from flexibility, not permanence.
Parsha in a Nutshell
The Torah reading for Sukkot (Leviticus 23:33–44) commands the nation to step out of their permanent homes and live in temporary huts (Sukkot) for seven days.
The structure itself has strict design specs: it must be built with temporary walls, and its roof (Schach) must be made from unattached organic material like bamboo or palm fronds. Crucially, the roof cannot be solid, it must be open enough so that the stars remain visible and rain can trickle through. The ritual commemorates the temporary dwellings the Israelites lived in during their 40-year journey through the wilderness (Leviticus 23:43).
Diving Deeper:
Most leaders fall into the trap of over-engineering. They build "concrete houses", rigid project plans, inflexible team structures, thinking concrete plans equal security. Then, the first unexpected roadblock hits, and the entire framework collapses.
The Sukkah is a masterclass in building for adaptability. It isn't designed to withstand a hurricane by force; it's designed to be lightweight, modular, and easily rebuilt.
The rule requiring a open roof (Schach) carries a direct leadership mandate: never build a process so sealed off that you lose sight of reality. The gaps in the roof force you to stay aware of external elements: market shifts, team feedback, and sudden industry disruptions.
When you build a product, design a workflow, or launch an initiative, build "Sukkah-style" frameworks: light, iterative structures that get the job done today, but remain flexible enough to pivot when conditions change tomorrow. Resilience is building something you can adjust on the fly without panicking.
Weekly Leadership Challenge
Audit a Rigid Plan: Identify one roadmap or project plan that feels over-engineered. Where can you strip away rigid assumptions and replace them with lighter, more flexible milestones?
Practice Iterative Building: Don't wait until a project is 100% polished to share it. Send a lightweight "V1 prototype" or draft outline to your manager or team early to test its strength before building permanent walls around it.
